Oracle® Insurance Rules Palette Release 9.3.1.0 E21044_01
Transactions and screens can point to the CopyBook business rules. This allows for plans/products to share common functionality. Maintenance is less complicated since the logic is held in only one place. The CopyBook named will be resolved by the system and the configuration contained in it will be added to the rule that implements it.
CopyBooks can be used under all elements of transactions. If the entire configuration of a transaction has been placed in a CopyBook, the transaction XML will be configured as shown in the XML example below.
| Element/Tag | Definition | Attribute | Element/Attribute Value and Description |
|---|---|---|---|
|
<CopyBook>
|
This is the start and end tag for the element. |
|
The value is the name of the CopyBook being called. The exact name of the CopyBook must exist in the business rule configuration. |
<Transaction>
<CopyBook>CopyBook-InitialPremium</CopyBook>
</Transaction>
<Transaction>
<CopyBook>CopyBookName</CopyBook>
</Transaction>
Copyright © 2009, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices