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 that were made to the Oracle Insurance Rules Palette GA release 11.1.0.0, 2017.
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 visit 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 enhancements that were made to the Oracle Insurance Rules Palette GA release 11.1.0.0.
New Rules Added
PlanAgreementSearchScreen BR
This is a new rule added to support Plan Agreement Search in OIPA.
- The <Fixed Fields>will allow the CustomerName and ProductName fixed fields to be renamed.
- <Fields> will allow additional Fixed Fields to be added to criteria.
- By default the grid will display Plan Name, Plan Status, Plan Effective Date, Plan Expiration Date , but the fields in the grid can be changed using the configuration in <Results> to display AsPlan and AsPlanAgreement fields.
Enhanced Business Rules
ValidateExpressions
A new optional attribute WORKFLOWTASK is added to the <Expression> element of the ValidationExpressions rule.
- This attribute is used to identify the Task Name for creating a new workflow task and to persist the Workflow Task Data as a record.
- It allows only the tasks that are applicable to the Activity Entity Code whose Creation Method allows the workflow task to be created automatically.
Note: If the Workflow feature is "turned on" via the system property, then only the associated <Expression> element in this rule generates the error for the configured workflow task.
GeneratePendingRequirements
A new optional element <WorkflowTask> is added to the GeneratePendingRequirements rule.
- The element is used to identify the task to be generated by its task name (as configured).
- It allows only the tasks that are applicable to the Requirement Entity Code whose Creation Method allows the workflow task to be created automatically.
Transaction
A new optional element <WorkflowTask> is added to the <Transaction> element.
- The element is used to identify the task to be generated by its task name (as configured).
- It allows only the tasks that are applicable to the Activity Entity Code whose Creation Method allows the workflow task to be created automatically.
Note: When the workflow feature is "turned on" via the system property and any business error is generated by an expression in the Policy level activity's ValidateExpressions rule, the configured workflow task is created and persisted as a Workflow Task Data record.
RequirementDefinitions
A new element <WorkflowTask> is added to the <Requirement> element.
- The element is used to identify the task to be generated by its task name (as configured).
- It allows only the tasks that are applicable to the Requirement Entity Code whose Creation Method allows the workflow task to be created automatically.
Note: When the workflow feature is "turned on" via the system property and the Requirement is generated, the configured workflow task is created and persisted as a Workflow Task Data record.
GroupCustomerScreen Rule
- The GroupCustomerScreen rule is enhanced to allow the configuration of Client types other '20'. With this restriction removal, now the Type drop down of Group Customer screen in OIPA displays the Client types as configured in the screen rule.
- To provide the ability to identify a hierarchy of group customers a new <FixedField> Hierarchy Relationship for relationship type is added under Action/Event configuration in the GroupCustomerScreen rule.
Enhancements in Rules Palette
Workflow Role/Queue/Task Definition
Workflow Tasks can be defined by adding a new Workflow node under Admin Explorer > Administration in Rules Palette. Under the "Workflow" node, two child nodes, Workflow Queues and Workflow Definitions can be added.
Workflow Roles
A Workflow role may be defined and each Workflow role may be associated to multiple queues. These sets of associations allow a user access to multiple queues in OIPA. Each user or team can be defined with a unique set of responsibilities. Users will access Workflow tasks in OIPA based on their role association to the queues.
Workflow Queues
Specific Roles defined above can be assigned to each Queue. Examples of queues may be a Supervisor Review, Underwriter, Customer Service, Claims Supervisor Review, Claims, etc. These roles can be configured separately from the security level roles. The number of and names of the roles may also be configured by the customer based on their business needs.
Workflow Tasks
User can define and assign specific task types to each queue and is configurable based on the business need. A definition includes a unique task name, identification of a queue, creation method and entity. This information may be updated or deleted in Palette as needed.