The release of OIPA 10.2.2.0 includes the below enhanced features in the Rules Palette and OIPA application:
S.No |
Feature |
Description |
Business Rule Changes |
Database Changes |
||
New Business Rules Added |
Enhanced Business Rules |
New Tables Added |
Existing Tables Updated |
|||
1 |
Display of Allocations History Enhancement |
This enhancement provides OIPA the ability to capture and view the policy allocation changes (added or modified) performed by the user through its UI or activities (i.e. transaction processing) or integration points. The Policy Allocation history includes the data modification done on Policy Allocation Type and Funds. With this enhancement, now the user can view into how a simple single list of fund allocations has changed for the lifetime of the policy. The history is captured and displayed for Policy Allocations where the plan is defined to support model allocations. It provides a way for the user to delete an entire policy allocation in the OIPA UI or through OIPA activities. For example, The Delete operation does show up when an allocation record is deleted using the trash can as in modifying the allocation from 3 funds to 2 funds. |
None |
None |
None |
None |
2 |
Availability of DepositValueGUIDs for Assignment Using MVA Funds |
The Collections in Assignment Types feature is enhanced to retrieve and pass the correct array of GUIDs in FILLBY-DEPOSIT function. This can be used to build the collection, which will be passed on to RemoveByFund for receiving ValuationGUIDs and DepositValuationEffectGUIDs as identities of deposit from where the money will be removed. |
None |
None |
None |
None |
3 |
Support OnChange/OnLoad for Fixed Fields on Requirements |
Administration of the fixed fields of a Requirement (such as Status) is modified to support OnLoad or OnChange of that field value to affect other fields for screen validation purposes. When administering a Requirement through the Requirement, the following Requirement fixed fields are exposed to Actions and Events to effect a change in the fixed field or an action when the Fixed Field changes. ˇ StatusCode ˇ Comments |
None |
None |
None |
None |
4 |
Action/Events Enhancement in Plan Screen |
This enhancement adds Action Event processing to the Plan Screen to enable validations to be performed on the plan data. It eliminates the user from the possibility of configuring incorrect fields and values such as validations, messages, warnings. |
ˇ PlanScreen |
None |
None |
None |
5 |
Grabbing Interest Rates for Valuation Enhancement |
This enhancement provides the ability to grab interest rates for Valuation. It retrieves the interest rates available within the following and store the interest rates used for a valuation: ˇ Activity math with a valuation object ˇ Function math that performs a valuation ˇ PolicyValues business rule Valuation XML It provides an easy method to retrieve and display the data to the user with more transparency. |
ˇ StoreFundValuationInterestRates |
None |
|
ˇ AsValuationInterestRate |
6 |
Support for Field Level Security on Search Screens |
The object search based on security group functionality is extended which allow to perform search on, ˇ Multiple conditions. ˇ Data in the main object table to be used in the filter. ˇ Data from other data objects that can be used in that search rule to be used in the filter. |
None |
ˇ ClientSearchScreen ˇ PolicySearchScreen ˇ GroupCustomerSearchScreen ˇ SuspenseSearchScreen |
None |
None |
7 |
PlanOrder Rule Modified like ProductPlanOrder Rule |
The PlanOrder business rule is modified to accommodate the sort order of products for all the screens that have system-defined product drop-down lists. The rule is now referred as ProductPlanOrder. It defines the order of the plans as well as the products either being optional. |
None |
ˇ ProductPlanOrder |
None |
None |
8 |
Implement History on GroupCustomer and GroupCustomerAddress Screens |
This enhancement provides the ability to store and display the details of GroupCustomer and GroupCustomerAddress history on its screens. |
None |
None |
None |
None |
9 |
Support OptionText on Disbursement |
This enhancement provides the ability to view the OptionText in lieu of code values on the disbursement record when viewing the processed activity tab in OIPA. The Option Text will be populated automatically without requiring any additional configuration. Displaying the text in place of codes values eliminates the user to memorize the code values and correlate it to the actual text. |
None |
None |
None |
None |
10 |
Assignment Balancing Enhancement |
This enhancement provides the ability to remove/apply money in a way that is consistent among all the assignments. During assignment processing, removed and applied amounts are rounded in order to move full denominations of a currency. Rounding introduces the need for adjustments to remain in balance with the requested money movement. Adjustments are applied to the last fund of a sorted list. The sorted list may be ordered by FundGUID or Fund Name. |
ˇ AssignmentProcessing |
None |
None |
None |
11 |
Ability to use Collections in CreateSegment to attach Segment Roles |
This modification will allow linking of clients to a role by dynamically adding multiple clients to a segment role when using the Create Segment attached rule. This enhancement allows creation and running of the policies more quickly. |
None |
ˇ CreateSegments |
None |
None |
12 |
Retain Activity Validation Overrides during Reprocessing |
This enhancement provides a provision at the Company level to the users of OIPA to decide whether or not to retain the Activity Validation Override during reprocessing. |
None |
ˇ CompanyCosmetics |
None |
None |
13 |
IVSTrackNumber limit increased to more than 10 |
This enhancement provides the ability to employ more than 10 tracks of development within the Rules Palette development environment. |
None |
None |
None |
None |