Oracle® Rules Palette Release 9.1.0.0.0 E15811-01

# CopyBook Element

## Description

Transactions can point to the CopyBook business rules. This allows for plans/products to share common functionality. Maintenance is less complicated since the transaction’s XML is held in only one place. The CopyBook named will be resolved and the configuration contained in it will be replaced within the transaction.

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.

## CopyBook Element/Attribute Table

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.

## Example XML

<Transaction>

<CopyBook>CopyBook-InitialPremium</CopyBook>

</Transaction>

## Schema XML

<Transaction>

<CopyBook>CopyBookName</CopyBook>

</Transaction>