While there are multiple ways to enter data into a grid, they generally require user input. Calculated fields can now be used to enter data into grids, either as static values or copied from other fields or grids within the workflow. The functions can add rows, edit or replace existing rows, or clear the grid and start fresh.
The two new functions are SaveToGrid() and NewGrid(), and use the same parameters. The difference is that SaveToGrid() adds new rows after any existing rows, while NewGrid() deletes any existing rows and adds new rows to the empty grid.
The functions take parameters to define the target grid, target fields, and a source field for each target field, as well as optional parameters to update a specific row in a grid.
− For details on using the grid mapping functions, see the Functions to Enter Data Into Grids (Grid Mapping) section.
In order to provide greater control over advanced lookups for combo box fields, multiple Domain / Rate Tables can now be provided in parallel with settings for Effective Date and Culture.
The Layer and Layer Versions sections have been removed from the Product Model.
•The effective date field from layer versions has been moved to the domain rate table management page. When upgrading to this version, all of your domain / rate tables will have the effective date of the associated layer version.
One field has been added to the General Information Panel on the Domain Rate Table Management page in addition to the effective date field.
•A Culture can be specified to associate the Domain / Rate Table to a specific language, including region, which will affect the available options in the lookup.
•The Effective Date controls when a particular Domain / Rate Table is in effect. When using an advanced lookup, only Domain / Rate Tables that are in effect will be applicable.
•Both options can be used together and will both be evaluated to determine the correct Domain / Rate Table to be used. If no Domain / Rate Table matches, there will be no results.
When using multiple domain / rate tables with Culture settings, the Key Column selected in the Data Source Configuration must contain unique values and must be identical across all related domain / rate tables.
A new key has been added to the language file downloaded from the Custom Labels page,
Label_ DataSourceDisplayColumn_DataSourceConfigurationCode_ColumnCode. All display column headers within a combo box drop-down can be customized.
- For details on configuring Domain / Rate Tables, see the Domain / Rate Table section.
Custom labels and languages are now supported for premium types. The following changes have been made to support this feature.
•Some older premium types may not have a Code. As part of this release, those premium types will be updated with a unique code.
•A new key has been added to the language file downloaded from the Custom Labels page, Label_PremiumType_PremiumTypeCode. All premium types are included in the file, and can be customized.
− For details on managing language configurations, see the Custom Labels section.
As part of the Automatic Cancellation Initiation feature, introduced in version 2.4.78, three system fields from the Billing module were made available to triggers in the Policy module.
These integration fields can now be mapped to workflow fields (dynamic fields), creating a read-only link that makes this system data available in the workflow. These dynamic fields can then be used in generated documents, e-mails, and calculated fields.
Note that the (BILLING) Term Total Payment Amount field previously introduced for triggers has been renamed to (BILLING) Term Total Collected Amount.
To map the fields, enter the associated code of the integration field into the External Code field in the Field Management page.
− For details on managing dynamic fields, see the Managing Fields section.
− For a list of available integration fields, see the Billing Integration Fields section.
In order to provide greater flexibility when taking policy numbers from dynamic fields, some enhancements and modifications have been made to the Master Cover - Policy Numbering page.
•The Manual option for the Source field has been renamed to From a Field. This is more consistent with the other settings on the page.
•When From a Field is selected, the Sequence panel and Next Sequence Number field are now displayed. The remaining fields in the Sequence panel remain hidden, as they do not apply to this Source type.
•When From a Field is selected, the Next Sequence Number value is now incremented for each new policy that is bound. This number is maintained between both Source types, and can still be changed manually.
Unlike Automatic configurations, From a Field configurations cannot be set to increment this number on renewals. This must be handled in the dynamic field.
•A new function has been added. The NextPolicySequenceNumber() function returns the next number as it appears in the Policy Numbering page. This can be used in calculated fields to define the policy number through means such as calculations or table lookups.
The existing functionality for Automatic configurations has not changed.
− For details on configuring policy numbering, see the Policy Numbering section.
When the Event Tracking report was introduced in version 2.4.78, the calculations payload was available as an XML file. This XML file has been replaced with a branching interface similar to the Calculation Trace View panel recently introduced in the Quote Report page.
On clicking the Payload link in the Event Tracking page, the Calculation Trace View window opens in a new tab or window, depending on your browser settings. This window provides a branching list of fields, calculations, functions, and triggers used in evaluating that specific operation during the event. Each entry includes an icon to identify the type of calculation component, and hovering the mouse pointer over an entry displays additional information in a tooltip.
Note that the branching view is only available for events that have occurred since this version was deployed. Payloads for older events will still display as XML files.
When accessing the Event Tracking report from with a transaction, only events related to that transaction are included. A full version of the report can now be accessed from the Reference menu, using the Event Tracking option. This version of the report includes all events, across all transactions.
− For details, see the Event Tracking Report section.
While working within the system, a variety of errors and other notification messages may occur, and are logged in the system. These can result from internal issues, problems with communications, configuration errors, or other causes.
The new Application Logs Viewer provides a structured view of these logs, with details on errors and messages recorded by the system. This can be used to troubleshoot problems, particularly when descriptive errors have been suppressed by the system configuration.
The Application Logs option is available under the Reference menu.
Access to this feature is controlled by the ViewEventHistory security right.
− For details, see the Application Logs Viewer section.
An audit trail feature is now available for the Billing system. This tracks changes to a range of data and settings, and makes the details available in a report.
The Audit Trail option has been added to the Billing menu. This opens the Audit Trail page with a list of tracked resources. Clicking on a resource opens the Audit Trail Details window which lists the changes to that resource, with new and old values, the user who made the changes, and the date and time of the change.
Note: Not all features and data are being tracked at this time. Additional sections are expected to be added in future releases. Also, changes will only be tracked once this feature is available, so older changes will not be available.
Access to this feature is controlled by the new ViewBillingAuditTrail security right, which has not be added to any security roles.
− For details, see the Reviewing Billing Changes in the Audit Trail section.
The Adjuster Auto-Assignment rules have been enhanced to support custom Workflow Events. One or more events can be selected in the Adjuster Auto-Assignment Management window, and the rule will only be applicable when at least one of those events occur when processing a claim.
This serves as an additional condition, so the rule must still be active and the trigger must still evaluate as true for the rule to apply.
If no events are selected, the rule will be evaluated during the default events, such as submitting a claim or using the Assign Adjuster button.
− For information on managing auto-assignment rules, see the Adjuster Auto-Assignment section.
In preparation for a new feature to send out scheduled e-mails with summaries of claim payments, some new options have been added to the system.
The E-mail Configurations section has a new option, the Scheduled E-mail checkbox. This option makes the configuration available for selection in the scheduling section. Note that Scheduled E-mail configurations cannot also be set to Manual E-mail or Automatic E-mail. In addition, a Claim Payment Payee option has been added to the Recipient Parties field.
A new page has been added to the General Settings section, Scheduled E-mails. This new page includes settings to enable the e-mails, schedule the time of day, select an e-mail configuration, and define which payment types and categories should produce e-mails.
These new options can be configured, but no e-mails will be sent. The full functionality will be enabled in a future release, and a Part 2 will be included in the release notes.
− For information on managing e-mail configurations, see the Configuring Claims E-mails section.
− For information on managing general settings for e-mail scheduling, see the General Settings – Scheduled E-mails section.