What's New in 10.1.2.0

This enhancement invokes a defined business process for a group of specified policies from one screen (Batch Screen) and avoids the need to enter activities on each individual policy. This functionality can be used to invoke activities on other entities in addition to policies.

This enhancement provides the ability to track, apply, and remove premiums/payments based on age of premium. In addition to tracking premium/payment deposits, bonus or interest payments can be tracked. Tracking the money transactions in the life cycle of a policy can be used to calculate remaining premium, charges, age of deposit, etc.

The ability to attach and retrieve a file through the OIPA UI has been added to the Comments functionality. Files are now extensions of comments and at any place a comment can be inserted, so may a file without any additional configuration. All file types are supported and the system allows one file upload per comment but any number of comments may be added to an entity. Entities that support user comments are: Policy, Activity, Client, Requirement, Suspense, and Segment.

Market Value Adjustment (MVA) Funds Support

This enhancement implements support for MVA processing. MVA funds are defined by a fund type and interest calculation. This calculation is invoked during any valuation that includes MVA funds.

This enhancement provides the ability to link the Policy segment entity with Plan segment entity. In group insurance set up, this enables the policy segment to capture the plan segment data.

Client Search Screen Security by Client Type

A consistent Policy Summary presentation has been introduced for all the Policy related screens, except the Policy Screen. The Policy Summary section can be configured or a default display will be used. The Policy Screen itself retains the current fixed field and dynamic field presentations without the Summary. Also, the Policy Summary section has been added to the Policy Overview Screen to make it consistent with all other Policy related screens.

Ability to Transfer Indexed Funds from one Bucket to another Bucket

This enhancement expands the capability of executing valuation within a transaction’s resolved Math to the Math section of a User Defined Function.

The MathStatement activity function, GetFundPositions, has been modified that allows the exclusion of funds by Fund GUIDs or an array of Fund GUIDs. Previously, fund could only be excluded by Fund Type.

The ApplyByFund and RemoveByFund assignment types currently require explicitly configured fund GUIDs and amounts. This feature will allow these assignments to accept a dynamic collection of fund GUIDs and amounts thereby greatly enhancing the functionality of the assignment types.

Multifield in ScreenMath Action & Event

All screens that support MultiFields will allow an Action/Event configured in a Screen’s Business Rules ScreenMath to trigger the Action/Event configured in a MultiFields rule.

Configuration of this rule will allow a <Prohibit> element that works the opposite of <Allow>. This supports conditions that are easier to restrict rather than permit. Additionally, the <Allow> and <Prohibit> elements are repeatable to support a 'best match' scenario to find the first configured set of criteria that are all true.

A new attribute 'Total' is added to the output column in the InquiryScreen. This displays the sum of the results of specific numeric data columns at the bottom of the grid.

Multifield Enhancements to Capture and Update data via Transactions

This enhancement allows updates to Multifield data into an entity like Policy or Segment or Role, etc. through a transaction and allows copying data back to Multifields from transactions.

Suspense Accounting based on a Dynamic Suspense Field

This enhancement improves the user experience and eliminates confusion while entering 'Role' information, using the 'Find Client' functionality or performing an action using the right click menu.

Improvements have been made to correct formatting and eliminate confusion when entering/viewing Client Address information.

Updates to a Client’s Default Address will be reflected in History. The deletion of a Client’s address will be reflected the Address History summary table as a ‘Delete’ action versus an ‘Update’ action. Additional information has been added to the History summary table for easier identification of which entity/role has been modified.