Requirement Processing Sample

Requirements can be added to transactions to control the situation that must be present in order for the transaction to process as an activity in OIPA. When the transaction is added as an activity, OIPA will check to make sure the requirement conditions are met before allowing the activity to process. If the requirements are not met, a requirement icon will appear next to the activity and it will not process. The activity will then go to Requirement Pending status rather than Active status.

Scenario

CSR selects the ContractSign activity and enters an Activity Effective Date of Feb 15, 2010. The CoSign Checkbox is left Unchecked. The requirements attached to this transaction require that the activity only process when the Co-sign checkbox is checked or the Effective Date is greater than March 1, 2010. A requirement icon appears next to the activity and it does not process.

Configuration Requirements

There are three AsCode tables created for requirements:

There are seven database tables used for requirements:

There are three business rules that need to be configured:

There is one optional business rule:

Requirement definitions should be created with specific requirement criteria to satisfy.

A transaction is needed to demonstrate requirements.

Prototype Samples

The following pieces of configuration were added to the Prototype Company to demonstrate requirements processing:

Requirement Processing transactions

Requirement Processing Prototype Transactions in Main Explorer

Requirements in Admin Explorer

Requirement Definitions in Admin Explorer

Requirement Business Rules

Requirement Business Rules in Global Rules Explorer

     
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. About Oracle Insurance | Contact Us