The Calculated Fields documentation has been expanded to include new developments for copying grid data, a new function for conditional formulas, and access to tracking data for managing grids.
The Grid Mapping features have a new function, ClearGrid(). This function clears a target grid and any associated child grids. This function should be used within a conditional structure to avoid unintentional loss of data.
ClearGrid(p0)
P0 (text): Code of the grid to be cleared. Child grids are cleared automatically, and do not need to be specified.
Returns (): N/A
− For details on using the ClearGrid() function, see the Functions to Enter Data Into Grids (Grid Mapping) section.
The Where() function can be used to apply conditional logic when processing grid data. This function is placed after any action such as a placeholder, function, or a parameter within another function. That action will only be processed if the Where() condition evaluates to True.
For example, when placed after a SaveToGrid() function that would copy all rows from a grid, each row will evaluate the condition and any row where the condition fails will not be copied.
Where(Value1 operator Value2)
Value1: This is the first value for comparison.
operator: Operator to determine how the values should be compared
Value2: This is the second value for comparison.
Returns (): N/A
− For details on using the Where() function, see the Conditional Selection of Grid Rows - the Where() function section.
In order to provide greater control of grids and tracking data within grids, new system placeholders have been added automatically for all dynamic grids. In each case, the gridcode should be replaced with the code of the appropriate grid.
|
[[gridcode_SequenceNo]] |
Used in grids, displays the row number for each row. |
|
[[gridcode_ChildSequenceNo]] |
Used in child grids, displays the row number for each child associated to a specific parent row. A separate sequence is tracked for each parent row. |
|
[[gridcode_HierarchyId]] |
Used in grids, displays the hierarchy position for the current row within a parent/child grid structure. For example, the second row of the top-level grid has four child entries, and the third row of those child entries has one child entry, the hierarchy will display "2.3.1". |
|
[[gridcode_Key]] |
Used in grids, displays the unique internal identifier value for the current row. |
|
[[gridcode_NextSequenceNo]] |
Used outside of grids, displays the next row number that will be used when adding a row to the selected grid. |
|
[[gridcode_NextChildSequenceNo]] |
Used in grids, displays the next row number that will be used when adding a row to the child grid associated to the current row. |
− For details on the new placeholders, see the Grid Information section.
Reports can now be created that summarize how existing transactions would be different if they were created using the latest published version of their master cover.
The reports include, but are not limited to:
•The change in total premium.
•The change in total tax.
•The change in total commission.
•A comparison of validations and referrals that were triggered.
These reports, known as Impact Assessments, can be created by navigating to the Product Design menu and then selecting Impact Assessment.
Two new security rights have been created:
•ViewImpactAssessment: Allows the user to access the Impact Assessment option in the Product Design menu.
•CreateImpactAssessment: Allows the user to create impact assessment requests.
− For details on creating impact assessments, see the Creating an Impact Assessment section.
A new master cover setting can be used to have the Create Client Company page open instead of the Select or Create Client list when a user is creating a new submission. This is useful for workflows where it is likely that a new client company will have to be created for the submission.
The setting can be controlled using the new Client Screen in New Submission Workflow field, which has been added to the Miscellaneous Settings panel on the Master Cover - Policy Settings page.
− For details on configuring miscellaneous settings for master covers, see the Policy Settings section.
A new Loss Cost Lookup web service can now be used with Data Source Configurations. The service is used to retrieve ISO Loss Cost data for controls within a workflow. The service is designed for use with two lines of business: General Liability and Automobile.
The web service can be selected for use in the Data Source field in the Attributes panel on the Data Source Configuration Management page.
− For details on Data Source Configurations, see the Creating a Data Source Configuration section.
When creating Reinstatement transactions, the premium can now be pulled directly from a dynamic field in the workflow instead of using the default refund reversal method.
This new setting can be configured using the new Reinstatement field which has been added to the Coverage Calculation Methods panel on the Master Cover - Policy Settings page. It contains the following two options:
•Reverse Cancellation: This is the default setting and maintains the existing functionality. The premium is set to reverse any refund calculated for the associated cancellation transaction.
•Rule Evaluation: This option uses Rate Rules to pull premium values from one or more dynamic fields in the workflow. The premium values can be produced by calculated fields, or brought in from external systems. Multiple rules can bring in values for multiple premium types, including adding together multiple values for each premium type. Taxes, fees, and commissions are then applied to each premium type using the existing settings.
Notes:
•Rate rules are not compatible with premium grids and should not be used with any workflow that contains one.
•This feature does not support all workflow features, and is specifically intended for use with integration configurations that use a Policy Decisions integration type.
− For details on Data Source Configurations, see the Creating a Data Source Configuration section.