OIRP Release Notes

Oracle Insurance Rules Palette Release Notes

The Oracle Insurance Rules Palette is a standalone application that can be used in conjunction with Oracle Insurance applications. The Rules Palette allows users to create and configure business rules that support their business process model. Plans hold related policies that share a set of business rules, plan rules, requirements, transactions, segments, plan data and plan values. Copybook functionality enables transactions and business rules to be used across multiple plans, leveraging existing information and reducing configuration time.

These release notes contain the enhancements made to the Oracle Insurance Rules Palette as part of the Oracle Insurance Policy Administration GA release 11.3.0.0.

Customer Support

If you have any questions about the installation or use of our products, please visit the My Oracle Support website: https://support.oracle.com or call (800) 223-1711.

Oracle customers have access to electronic support through My Oracle Support. For information, visit:

http://www.oracle.com/us/corporate/accessibility/support/index.html#info or http://www.oracle.com/us/corporate/accessibility/support/index.html#trs if you are hearing impaired.

Enhancements in the Oracle Insurance Rules Palette

This section describes the enhancements made to the Oracle Insurance Rules Palette:

Funds and Valuation

ValuationFields BR

This rule is introduced to calculate values for funds and can store the values at Deposit, Fund, and Policy levels. The configured values are calculated during valuation processing (for example, calculate the fund’s yield). This functionality is available only when the fund is used by a Plan that utilizes Point In Time (PIT) valuation processing; if the Plan uses Inception Valuation, the Fund’s ValuationFields business rule is ignored. A user can configure the Fund’s calculated values to display on the Values screen or use in Math (with standard Valuation syntax example: Valuation:Fund:Yield ).

The ValuationFields business rule can perform aggregate functions on calculated values. The supported aggregate functions are: MIN, MAX, SUM, COUNT, AVERAGE, and functions, such as GMEAN, MEDIAN, MODE. The ValuationFields business rule is overridden at the Fund level.

For more information, refer ValuationFields

GrossFullWithdrawal and GrossFullWithdrawalWithAllocations Assignments

Previously, these assignments were used to reduce the policy value by taking the value either from fund deposits or directly from Funds. Now, the same continues if funds and deposit values are positive, but the opposite happens if the funds and deposit values are negative. A new attribute IGNORENEGATIVECASHVALUES is added with Yes/No values to allow negative fund values for Fixed Funds of Type (01).

  • If this attribute is configured with the value of Yes, funds with a negative cash value is dropped during the pro rata calculation and from the fund removal.
  • The default value is No, which allows funds with negative cash value to be included in the pro rata calculation. The absolute value of the funds are used in the pro rata formula.

For more information, refer:

GrossFullWithdrawal Assignment

GrossFullWithdrawalWithAllocations

ActivityResultsScreen

The ActivityResulltsScreen business rule can be configured for the ValuesScreen (tab) in it to display the positive and negative fund values. Now, the ActivityResultsScreen rule is enhanced to include the new elements <Valuation>, <NegativeCashValue>, and <PositiveCashValue>, which can be configured to display the sub-total Negative and Positive Cash Values.

The <Graphs> element of the ValueScreen allows a pie chart to represent the Policy's assets along with the positive and negative fund values. The chart displays a section for each fund represented in its size as a percentage of the fund's value compared to the policy's cash value.

For more information, refer ActivityResultsScreen

RemoveByFund Assignment

Now, the RemoveByFund Assignment is enhanced to provide the ability to withdraw money from a specific bucket of one or more indexed funds. RemoveByFund Assignment allows an activity to remove money from one or more funds without the use of an allocation. The activity can use its configured logic to determine which funds and the amount to remove from each fund. The removal can now target a specific indexed fund bucket.

  • In the existing functionality, the RemoveByFund assignment identifies the fund or funds from which to remove money. This is now enhanced by adding a new attribute called BUCKET, which indicates the bucket number from which the money to be removed.
  • In the existing functionality, the Removals from deposits, if tracking by deposit, continue in LIFO or FIFO order. This is now enhanced such that the cash value of the bucket must be sufficient to cover the removal amount.

For more information, refer RemoveByFund

WriteValuationElements BR

With the Re-design of Data Storage for PIT enhancement, the WriteValuationElements BR is modified as follows:

  • The NetGain element in this business rule is replaced by BeginNetGain and EndNetGain elements.
  • The following elements in this rule are removed.
    • SurrenderValue
    • FreeAmount
    • SurenderRate
    • SurrenderValue

For more information, refer WriteValuationElements

FundCategoryOrder

A new Business Rule, FundCategoryOrder can be configured to define the order in which the fund categories are displayed in OIPA. The applicable configured categories are displayed on the Values Screen’s Fund Detail and Policy and Asset Graph Sections and the processed activity’s Valuation tab display the fund categories in the configured order. If the Rule is not present or configured to "Off", the funds display as they currently do, with no mention of a category name.

A new code name, AsCodePlanFundCategory, is used to define the applicable fund categories. After the categories are entered in the AsCode table, they can be associated to the fund in the Rules Palette. A new column, Category, has been added to the AsPlanFund and AsProductFund tables to store this new value.

For more information, refer FundCategoryOrder

ScreenMath Element

This enhancement enables configuration of valuation in ScreenMath to calculate the updated values as of valuation date by supporting the MathValuation MathFunction in ScreenMath. Previously, this functionality was only available in Math. Now, the Valuation can be run for OnLoad, OnChange, and OnSubmit events and if necessary, calculate and view the values before running the activity. The ScreenMath section of Screen Rules can be configured with this enhancement. Valuations run in ScreenMath are not stored in the database.

For more information, refer screenmath

PlanFund

A new field, TrailingCalculationDuration, is introduced on the PlanFund in the Rules Palette Admin Explorer. The configuror needs to enter the number of days the fund should appear on the Values screens even when the balance is zero.

This enhancement supports the display on Values screen, processed Activity screen, and Inquiry screen and supports dynamic calculations of funds in Math Valuation even when the balance of the funds is zero. It supports tracking by fund and by deposit and is only applicable to Point In Time (PIT) valuation.

The following database tables for Fund have been modified:

  • AsPlanFund table is added with a new column VALUERESETDURATION to store the number of days after the value of the fund reaches 0. It should still be displayed on the valuation screen.
  • AsFundValue and AsDepositValue tables are added with a new column ZEROBALANCEDATE to capture the date on which the fund value reached zero the last time.

For more information, refer AllocationScreen

Deprecated Rules

PointInTimeValuation BR

With the Re-design of Data Storage for PIT Valuation enhancement, the rule is deprecated in this release. The default behavior for writing Policy, Fund, and Deposit valuation records are the same as before, as the value for WriteBegin is always set to Yes. The processed activity Valuation tab results now always displays the Begin and End values tabs.

Requirements Enhancements

AddRequirements BR

This enhancement adds flexibility to the AddRequirements business rule to retrieve the requirement name, initial status, and allowance for duplication from the activity's math variables or fields. This can replace complicated logic that determines the requirements to generate into the activity's math section. It allows the AddRequirements business rule configuration to be a boilerplate across multiple transaction configuration provided by activity math and fields. These factors are likely to reduce the scale of maintenance tasks associated to the rule's configuration.

For more information, refer

AddRequirements-Requirements

AddRequirements-Transactions

ClientRequirementScreen

This new screen rule can be used to configure client's requirement summary table, which can be accessed using the Requirements link from left navigation menu when the ClientScreen opens. If this rule is not configured, requirement summary is displayed using the default table.

For more information, refer ClientRequirementScreen

ClientScreen BR

ClientScreen BR is modified to include the new attribute ALLOWREQUIREMENTS. This attribute is added to the ClientScreen business rule to indicate whether Client Level Requirements are allowed. The default is No. If set to Yes, and if the appropriate security exists, the Requirement node is available on the Client screen’s left navigation pane.

For more information, refer ClientScreen

Add Support for CopyBook Use in Requirements

Previously, any CopyBook configuration present in the Requirement rules were ignored by the system. CopyBooks and Functions are now supported in all three Requirements sections, Source, Definitions and Results. In addition, all of the Requirements attached Rules support the CopyBooks.

  • RequirementDetail
  • RequirementDefinition
  • RequirementResults
  • AddRequirements
  • AddImpairments
  • CopyToRequirementResultFields
  • CopyToPolicyFields
  • CopyToClientFields
  • CopyToRequirementFields
  • CopyToImpairmentFields
  • MatchRequirementResult
  • ProcessActivities
  • SpawnActivities
  • StatusChange
  • UpdateImpairmentStatus

Workflow Enhancements

ValidateExpressions BR

In the existing functionality, ValidateExpressions BR generates a workflow task when there are any business errors during the execution of an activity. Now, the rule is enhanced to include a new attribute, CREATEONUSEREXECUTION in the <Expressions> element configuration. This optional attribute can be configured whether to generate a workflow task manually when a user executes the activity from the OIPA UI or automatically through cycle, DI and AsFile post processor executions.

For more information, refer ValidateExpressions

Transaction

In the existing functionality, a transaction configuration may include workflow task generation when any one of the transaction's business errors from ValidateExpressions is generated. Now, the rule is enhanced to include a new attribute, CREATEONUSEREXECUTION in the workflow configuration. This optional attribute can be configured whether to generate a workflow task manually when a user executes the activity from the OIPA UI or automatically through cycle, DI and AsFile post processor executions.

For more information, refer Transaction_Element

GeneratePendingRequirements BR

In the existing functionality, any activity level Requirement that generates a workflow task is defined in GeneratePendingRequirements. Now, the rule is enhanced to include a new attribute, CREATEONUSEREXECUTION in the workflow configuration. This optional attribute can be configured whether to generate a workflow task manually when a user executes the activity from the OIPA UI or automatically through cycle, DI and AsFile post processor executions.

For more information, refer GeneratePendingRequirements

RequirementDefinition BR

In the existing functionality, any Policy and Policy Client level Requirement that generates a workflow task is defined in the XML Definition of the Requirement. Now, the rule is enhanced to include a new attribute, CREATEONUSEREXECUTION in the workflow configuration. This optional attribute can be configured whether to generate a workflow task manually when a user executes the activity from the OIPA UI or automatically through cycle, DI and AsFile post processor executions.

For more information, refer RequirementDefinition

Segments Enhancement

CreatePolicy

In the existing functionality, the configuration of CreatePolicy allows naming the segment as the source of data. Now, the rule is enhanced to allow the source policy data to include multiple segments with the same name, that is, multiple child coverages.

  • A new attribute SEGMENTGUIDS is added to the CreatePolicy rule, which identifies one or more Segments that may be copied to the new policy. Its value references an array math variable containing SegmentGUIDs. This attribute is applicable only when the existing attribute COPYSOURCE is equal to "Yes".

For more information, refer CreatePolicy

Client Enhancements

ClientActivityLinkScreen

Previously, when a user selects the Client DataType field in an Activity, the Client screen appears with FindClient and NewClient tabs (ClientSearchScreen and ClientScreen). Now, ClientActivityLinkScreen rule is introduced to control the presentation of the FindClient and NewClient screens, when a user selects an Activity field defined as Client DataType to add or modify an activity in the host screen. When this new rule is configured, the context of the initiating screen (host screen) is passed to the ClientScreen and ClientSearchScreen. With this enhancement:

  • The configuration can alter the data capture, perform the data validation, and add or search Client Types for different business scenarios.
  • When returned from the Client pop-up to the host screen, the ONCHANGE event can be triggered.

The rule can be overridden at the Primary Company level.

For more information, refer ClientActivityLinkScreen

ClientScreen and ClientSearchScreen Business Rules

The ClientScreen and ClientSearchScreen rules are modified to include the new elements and attributes to alter data or to perform some validation based on the context passed from the host screen (adding or modifying an activity).

Now, the user can configure <Events>, <Actions> and <ScreenMath> functionality under the root elements of <ClientSearchScreen> and <ClientScreen>) and outside the <Client> elements.

For more information, refer:

ClientScreen

ClientSearchScreen

Comments Enhancements

GenerateComments BR

This new attached business rule can be configured to generate comments from activities for any entity. The rule can be attached to Plan/Policy/Client level of activities. The rule allows defining an ObjectArray in a transaction math that contains the field data for a comment for the target entity. The activity uses a BigText field to create the comments and passes them into the comment object in Math. BigText data types are saved as CLOB in the database, limited up to 4000 characters.

For more information, refer GenerateComments

MaintainComments BR

The MaintainComments rule is introduced to allow copy-to functionality to update a comment on any entity that supports the Comments feature. When the target entity in which the comment needs to be updated is specified in the rule, OIPA creates a comment in an object array such that the entity is defined in the math when the comment object is initiated.

For more information, refer MaintainComments

UpdateCommentsStatus BR

The UpdateCommentsStatus attached rule is introduced to update the status of multiple comments of the entities.

For more information, refer UpdateCommentsStatus

Rates Enhancement

Add More Rate Criteria Columns to Rates

This feature provides the ability to increase the number of rate criteria columns from the default of 10 to the required number of columns based on the business needs. To utilize this feature, an optional system property rateCriteriaConfiguration.enabled is added to the PAS Properties to enable this functionality and provide validation of the database schema against the AsCode table on the newly added columns to ensure they are in sync.

The required number of rate criteria columns are defined in AsCode table of AsCodeRateCriteriaColumns CodeName. It means the AsCodes table defines the maximum number of RateCriteria columns that can exist in the system across all Primary Companies. The system reads this pre-defined CodeValue from the AsCodes table and generates the scripts to create the specified number of rate criteria columns dynamically in the AsRate and AsRateGroup tables when they are executed.

For more information, refer Rate_Groups

Note: Please Note, this script must be run immediately after the AsCode table is modified and the script is generated to ensure there are no mismatch issues, any delay in running the script may result in issues when trying to access Rates.

Other Rules Enhancements

MultiField BR

Previously, instances of MultiFields were stored in the MultiValueField tables for all objects. When this data was queried from the database, there was no way to know how to group them unless screen rules were read, which was problematic when using APIs. To address this, a new column, GroupName, has been added to the MultiValueField tables. The GroupName column is populated with the Name configured in the MultiField rule. The Name element in the MultiField rule is now mandatory.

For more information, refer MULTIFIELD

DisbursementUpdate BR

This rule is enhanced to allow Policy Level activities to update the status of disbursement records. The rule is modified to include the new attributes namely, DISBURSEMENT and ACTIVITY, which can be configured if a single disbursement record needs to be updated for a policy. When DisbursmentUpdate rule is attached to a policy level activity and there are multiple disbursements available for a policy, then multiple DisbursmentGUID's are passed to <DisbursementArray> and the status is updated for multiple disbursement records.

For more information, refer DisbursementUpdate

ExternalLinks BR

This system rule is introduced to configure external application links that can be accessed from OIPA. The rule allows the configuror to configure links at the Primary Company level and at the context level such as Client, Case, Suspense, Policy and Group Customer.

For more information, refer ExternalLinks

Rules Palette Enhancements

Allow New Security Group to Access Plans Under a Group Customer

Previously, when creating a new security group, security could only be granted to the plans manually one at a time using the Rules Palette. A new option Grant Access to All Plans has been added to Rules Palette - Security Groups. Selecting this option grants authorization of all of the applicable Plans to the newly added Security Group.

For more information, refer Security at Product Level

Ability to Override a Requirement at the Product Level

In the existing functionality, Requirements could only be overridden at the Company, Plan or State levels. This enhancement adds the ability to override Requirements at the Product/Child Product level. The Rules Palette has been updated to allow override of Requirement at the product level and OIPA best match logic ensures that the appropriate override level is used.

For more information, refer Create_Requirements

Rules Palette Release Management Improvements

Release management improvements allow a user to manage the configuration and version history content for each entity that may contain multiple layers of data dependent on the entity's design in OIPA. The IVSCodeRuleType code table is used to encode all the entities that are captured in configuration packages and can be added to a Release Management package. Each encoded entity contains its own content and history syntax. This enhancement extends Release Management/Versioning to the following entities that were not included earlier:

  • ActivityFilters
  • AllocationModels
  • AssetClass
  • AssetClassFund
  • Comments
  • Fund
  • FundPlans
  • FundPlanStatuses
  • FundProducts
  • IntakeProfile
  • Masks
  • PlanBenefitFunds
  • PlanChildFunds
  • PlanStateApproval
  • ProductParentFunds
  • ServiceGroups
  • Workflow Definition
  • Workflow Queue/Role
  • Company
  • Enrollment Transaction
  • Product
  • Rate Group
  • Security Auth Company
  • Security Auth Company Page
  • Security Auth Company Web Services
  • Security Auth Inquiry Screen
  • Security Auth Plan
  • Security Auth Product
  • Security Auth Plan Page
  • Security Auth Transaction
  • System Date
  • Translations

For more information, refer:

Entities Captured by Release Management

Configuration and Version History Management of Entities

Release Management Utility

This enhancement implements a utility that deploys the OIPA Detached Migration Configuration Package to the target environment. You can run this utility from a command line or an automated script for continuous deployment. The deployment utility loads a Detached Migration Release Package (generated by the Rules Palette) into the target environment by parsing individual files of the package.

For more information, refer OIPA Detached Migration Deployment Guide.

Support from Rules Palette to Populate AsFileOutput Table

This enhancement allows the addition of records to ASFILEOUTPUT table by using the Rules Palette. A new node, FileOutput has been added under the Admin Explorer in Rules Palette. Similar to other Admin items, this new option has the Check In/Check Out ability, the ability to delete, and so on.

For more information, refer:

Configure_a_File Input

Configure_a_File Output

Enhanced AsMapGroup Functionality

The Rules Palette functionality has been enhanced to provide an efficient and user-friendly way to load Map Group, including multiple sets of Map Criteria and Map Values in a single session, using Excel spreadsheets with minimal setup in the Rules Palette. The spreadsheet import option is used to create only a new Map Group record. A user can update an existing Map Group record only through the Rules Palette user interface.

In addition, two new MathVariables, MAPGROUP and MATHGROUPARRAY have been introduced to efficiently retrieve information from AsMapGroup. They can be configured in transaction Math or ScreenMath. MAPGROUP returns a single value and MAPGROUPARRAY can return multiple values based on the parameters.

For more information, refer:

MAPGROUP

MAPGROUPARRAY