2.5.100 Core Enhancements

 

Logarithm Functions Have Been Added

The following functions can now be used to calculate the logarithm and natural logarithm of a number.

 

Log(p0, p1)

Calculates the logarithm of a number in relation to a base value.

P0 (numeric): The number whose logarithm should be calculated.  This can be a placeholder, function, formula or literal value.

P1 (numeric, optional): The base value.  If no value is provided, the system will use a base value of 10.

Returns (numeric): Returns the logarithm of p0 in relation to the base value.

      Exceptions:  Any value of p0 or p1 that is less than or equal to 0 will cause the function to return a null value, which will be treated as 0 by the system.

eg.

Log(10) will return 1.

Log(10,2) will return 3.321928.

Log([[FieldA]]*[[FieldB]],2) where [[FieldA]] = 3 and [[FieldB]] = 2 will be evaluated as Log(3*2,2) and will return 2.584962.

5 + Log(0) will return 5.

 

Ln(p0)

Calculates the natural logarithm of a number.

P0 (numeric): The number whose natural logarithm should be calculated.  This can be a placeholder, function, formula or literal value.

Returns (numeric): Returns the natural logarithm of p0.

      Exceptions:  Any value of p0 that is less than or equal to 0 will return a null value, which will be treated as 0 by the system.

eg.

Ln(10) will return 2.302585.

Ln([[FieldA]]*[[FieldB]]) where [[FieldA]] = 3 and [[FieldB]] = 2 will be evaluated as Ln(3*2) and will return 1.791759.

5 + Ln(0) will return 5.

 

−    For details on functions and placeholders see the Full Function Reference List section.

 

 

 

 

Setting a New Licensee HQ Company

In order to customize the licensee company hierarchy, a new or existing licensee company can be set as the licensee HQ.

 

A new checkbox, Top Level, has been added to the Company panel of the Licensee Information screen.  Saving a company with this setting will make it the new HQ company, and the previous HQ company will become a subsidiary of the new HQ.

 

Access to this checkbox is controlled by the new ChangeOwnership security right.  This right has not been added to any security roles by default.

 

−    For details on creating licensee companies, see the Creating a New Licensee Office section.

 

 

 

 

Selecting or Creating Clients From a Custom Screen in the Workflow

The client for a submission can now be selected or created through custom fields in the workflow.  These can be used in place of the standard select/create client pages, or as an additional method of handling the client data.

 

To start, a new setting is now available in the master cover.  The Client Selection in New Submission Workflow field now has an option for Within the Workflow.  Selecting this option bypasses the select/create client pages, allowing client management to be handled through the workflow.

 

A set of resources have been created to support this new approach.  A built-in screen can be added to the workflow, or the component panels, fields, and lookups can be used in a custom screen.

 

−    For more information on these built-in resources, see the Built-In Client Management Components section.

 

The Assured Lookup web service has also been updated as part of this enhancement.  In order for it to work with any data source configuration, the following two hidden fields must be added to the workflow, and two Output to Fields configurations must be implemented.

 

    The AssuredUserId and InsuredCompanyId fields must be added to the screen containing the Assured Lookup

 

    Output to Field configurations must be created to save the Assured User Id to the AssuredUserId field and the Insured Company Id to the InsuredCompanyId field.

 

−    For more information on the Assured Lookup, see the Web Service List for Data Sources section.

 

 

 

 

New Cross-Policy Search Functions to Return Detailed Results

Two new versions of the $CrossPolicyExactMatch and $CrossPolicyFuzzyMatch functions have been created.  While the original functions just returned a boolean true/false value if a match was found, the new functions can return a customized list of values from the matching transactions.  The returned list of values can be used with the NewGrid or SaveToGrid functions to populate a grid with the search results.

 

The two new functions are the $CrossPolicyExactMatchList function and the $CrossPolicyFuzzyMatchList function.  The parameters are similar to the existing functions, with some changes to define the returned values.

 

−    For details and examples, see the Searching Across Polices section.

 

 

 

 

Enhancements and New Functions for Copying Data to Grids

The NewGrid and SaveToGrid functions have been enhanced with a new optional parameter that allows each row to be duplicated as many times as needed.

 

The copies parameter and associated p5 parameter (to specify the number of copies) can be included at the end of each function.

 

NewGrid(p0, p1_SequenceNo, p2, p3, p4, p3, p4, , copies, p5)

SaveToGrid(p0, p1_SequenceNo, p2, p3, p4, p3, p4, , copies, p5)

 

These are optional parameters.  If they are not included, the functions will process normally and produce one instance of each row according to the configuration of the function.  If the parameters are included, each row will process normally according to the configuration of the function, but will be added to the target grid multiple times.  If the p5 parameter is 1, then one duplicate of each row is created, resulting in two identical rows.  A parameter of 3 will produce four identical rows.

 

A new function, NewList, has been added.  This function takes a comma-separated list and returns a list of the values, formatted to be used in other functions such as NewGrid and SaveToGrid.

 

NewList(p0,)

P0 (text): List of all values, separated by commas.  These can be placeholders, functions, formulas, or literal values.

Returns (): A list of all provided values, formatted for use in other functions.

 

Another new function, BreakText, has been added.  This function takes a large string value and splits it into smaller string values with a specified maximum length.  This produces a list of strings, formatted to be used in other functions such as NewGrid and SaveToGrid.

 

BreakText(p0,p1)

P0 (text):  This identifies the text to be split.  This can be a placeholder, function, formula, or literal value.

P1(integer):  The maximum number of characters in the sub-strings.  If the character number falls in the middle of a word, the system will move back to the nearest whitespace, such as a space, tab, or line break character.  If a single word exceeds the maximum number of characters, the word will be split at the character limit.

Returns (text): Returns the resulting sub-strings as a list of strings, formatted for use in other functions.

 

−    For details, see the Full Function Reference List section.