You are here: Business Rules > Attached Rules > CreatePolicy

Oracle® Insurance XML Configuration Guide Release 9.4.1.0 E23637_01

# CreatePolicy

## Description

The business rule is introduced to provide the ability to configure an activity-based creation of a new policy based on events occurring on an existing policy. One or more policies may be generated from a single source policy, although only one new policy per activity is supported. All policies are created in a pending status awaiting user review. The CreatePolicy business rule must be attached to a non-reversible activity and must be listed in the TransactionBusinessRulePacket.

CreatePolicy Element / Attribute Table
Attribute/Tag | Definition | Attributes | Element/Attribute Value and Description
--- | --- | --- | ---
<CreatePolicy> | The required opening and closing elements of this business rule. |  |
<Columns> | Optional Element; Opening tag for the Column section listing Policy columns. |  |
<Column> | Required Element; Defines the column description. |  | String: MathVariable. Name of any MathVariable defined in the transaction.
| NAME | Required Attribute; String: Column name. Column name from AsPolicy table except for PolicyGUID and UpdatedGMT(Column name should be exact name of the column in the AsPolicy table) .
| TYPE | Required Attribute; String: Decimal, Money, Percent, Integer, Date, and Text. Defines the Column data type that will hold the data type of the column in the AsPolicy table.
<Fields> | Optional Element; Opening tag for Dynamic Fields section. |  | Lists Policy fields that add a record to AsPolicyFields when a new policy is created.
<Field> | Required Element; Opening tag for field definition block. |  |
<FieldName> | Required Element; Defines the name of the field. |  | String: Field name from AsPolicyField
<FieldType> | Required Element; Defines data type of the field. |  | String: Decimal, Money, Percent, Integer, Date, and Text . Defines the Field data type.
<FieldValue> | Required Element; Defines value of the field. |  | String: MathVariable. Name of any MathVariable defined in the transaction.
<Policy> | Required: Start of the policy section. If the created policy uses the same plan as the source policy, then policy data on the target policy is defaulted to all values of the source policy. Any given policy or segment field value on the target policy can be substituted by a MathVariable or activity field. If the CreatedPolicy is for a different plan, then all policy data must be specified. |  |
| PLAN | Optional: Valid plan name or PlanGUID. By default, the policy is created using the same plan as the source policy. Identifies the plan for the new policy. The plan determines which fields are available for the new policy.
| COPYSOURCE | Optional Indicates whether or not to copy all source policy values to the new policy and only applies to AsPolicy and AsPolicyField (not AsSegment, etc.). By default, the value of the attribute is "No". Yes - Copy the source policy values to the new policy. The values will default to the source policy values unless overridden by values specified in this section. When the new policy has a different plan than the source policy, policy field names will be compared between the source policy and the new policy's field names. For all field names that match, the source policy data will be copied to the new policy. No: The structure of the new policy should be created from the specified Policy business rule. All field types and default values are pre-populated. Then, any fields that are defined in the following field's overwrite the defaults.
<Fields> | Required for different plans: Opening and closing elements for listing policy fields (fixed and dynamic). This section will override the field values that are defaulted or copied from the original policy and provide values for new fields. Note: This element is required when 'PLAN' and 'COPYSOURCE' attributes are not present inside the <Policy> element. At least PolicyName and IssueState fields must be configured. |  |
<Field> | Required, Repeatable: Opening tag for policy field definition block. |  |
<From> | Required: Defines a source for the value being applied to the field indicated by <To> and substituting for the source policy’s field value. |  | A MathVariable, activity field or literal. Reference to an activity field must have a prefix of “Activity:”.
<To> | Required: Indicates the target policy field for the value of the <From> element. |  | Any valid policy column or field name.
<Segments> | Optional: A section to contain all of the Segment information to pass along to the new policy. This may be required if Segments are necessary for a new valid policy. By default, no segments are created by the rule. |  |
<Segment> | Required, Repeatable: Provides a means to identify the segment to create and initialize for the new policy. This element is repeated for each segment that is to be created. |  |
| SEGMENTNAME | A literal value. Identifies the segment to create by its Segment Name.
| COPYSOURCE | Optional: Indicates if information from a segment of the same name on the original policy will be copied to the new segment. By default, the value of this attribute is "No". Yes - Specified segment will be copied from the original policy. No The structure of the new segment should be created from the Segment business rule. All field types and default values are pre-populated. Then, any fields that are defined in the following Field's section rule will overwrite the defaults.
| COPYALLROLES | Optional: Indicates whether or not to copy all the segment roles from the source policy segment to the new segment. If this attribute is not present, the default is 'No'. Cannot coexist with the COPY attribute on Role. By default, the value of this attribute is "No". Yes – Segment roles will be copied. No – Segment roles will not be copied from the source policy. Roles can be generated without being copied from the source.
<Fields> | Required: Opening and closing elements for listing segment fields. These values will apply to the specific segment being created. |  |
<Field> | Required, Repeatable: The opening and closing elements for a Segment field definition block. |  |
<From> | Required: Defines a source for the value being applied to the field indicated by <To> and substituting for the source segment’s field value. |  | A MathVariable, Activity field or literal. Reference to an Activity field must have a prefix of “Activity:”.
<To> | Required: Indicates the target segment field for the value of the <From> element. |  | Any valid segment field name defined by the SegmentName business rule.
<Roles> | Optional element; Begins policy role configuration. |  |
| COPYALL | Yes|No attribute values Cannot coexist with ROLECODE.
<Fields> | Required: Opening tag for fields configuration. |  |
<Field> | Repeatable |  |
<From> | Required: Defines a source for the value being applied to the field indicated by <To> and substituting for the source role's field value. |  |
<To> | Required: Indicates the target segment field for the value of the <From> element. |  |
<Role> | Required and Repeatable |  |
| ROLECODE | MathVariable to populate role code. Cannot coexist with COPYALL.
| COPYSOURCE | Optional Attribute: If this attribute is not present, the default is 'No'. COPYSOURCE cannot coexist with COPYALLROLES attribute on Segment. Yes - All Segment roles of this type will be copied from the source segment to the new segment. No - Segment roles will not be copied from the source segment. Creates a new role.
<Fields> | Required: Opening tag for fields configuration. |  |
<Field> | Repeatable |  |
<From> | Required: Defines a source for the value being applied to the field indicated by <To> and substituting for the source role's field value. |  |
<To> | Required: Indicates the target segment field for the value of the <From> element. |  |
<Allocations> | Optional Element; Defines Allocations to set for the new policy. This element initializes the field values and identifies the Allocations descriptions. It initializes the start of the section listing Allocation requirements. | FUNDMAP | Optional Attribute String: MathVariable. The name of the MathVariable containing the fund map. Name of the collection for the transaction that contains the mapping from the source policy fund to the new policy fund.
<Allocation> | Required Element; Defines the description of allocations to be copied from the source policy to the new policy. Repeated for each Allocation to be created for the target policy. | ALLOCATIONSOURCE | Optional Attribute String: Activity Allocation records will be copied from the allocations specified on the activity.
| FROMTYPE | Optional Attribute Code: Any valid allocation type code.
| TOTYPE | Optional Attribute Code: Any valid allocation type code.
<Fields> | Required: Opening tag for fields configuration. |  |
<Field> | Repeatable |  |
<From> | Required: Defines a source for the value being applied to the field indicated by <To> and substituting for the source role's field value. |  |
<To> | Required: Indicates the target segment field for the value of the <From> element. |  |
<Comments> | Optional: Defines comments to associate with the new policy. Data is populated from either the source policy or the activity itself. |  |
| COPYALL | Optional: Allows comments to be copied from the source policy. Yes: Comments are copied.
<Comment> | Optional Element; Defines the comment to be added to the new policy. |  | String: Comment |
<Activities> | Optional Element; Indicates the start of the section listing activities to be created on the new policy. |  |  |
<Activity> | Optional Element; Defines the name of the transaction to be created. | TRANSACTIONNAME | Required Attribute; String: Valid Transaction name for the plan. Any transaction name for the plan associated with the policy. |
<Fields> | Optional Element; Opening tag for listing Activity fields. |  |  |
<Field> | Optional Element; Opening tag for Field definition block. |  |  |
<From> | Required Element; Specifies a MathVariable from which to pull a value to be assigned to an activity field. |  | String: MathVariable/Literal/Field Name Name of any MathVariable defined in the transaction. |
<To> | Required Element; Specifies the AsActivity column or name of the activity field to assign the "From" value. |  | String: Field name Any field defined in the transaction XML of the transaction of which an instance is being created. |

## XML Example

    <CreatePolicy>

    <Policy PLAN="Plan:PlanGUID" COPYSOURCE="Yes">

    <Fields>

    <Field>

    <From>ContractEffectiveDate</From>

    <To>PlanDate</To>

    </Field>

    <Field>

    <From>Policy:IssueStateCode</From>

    <To>IssueStateCode</To>

    </Field>

    <Field>

    <From>NewContractNumber</From>

    <To>PolicyNumber</To>

    </Field>

    <Field>

    <From>ContractStatusCode</From>

    <To>StatusCode</To>

    </Field>

    </Fields>

    </Policy>

    <Segments>

    <Segment SEGMENTNAME="Deferred Annuity" COPYSOURCE="Yes"></Segment>

    <Roles>

    <Role ROLECODE="37" COPY="Yes"></Role>

    <Role ROLECODE="01" CLIENTGUID="Activity:OwnerClientGuid">

    <Fields>

    <Field>

    <From>ContractEffectiveDate</From>

    <To>StartDate</To>

    </Field>

    </Fields>

    </Role>

    </Roles>

    </Segment>

    </Segments>

    <Roles COPYALL="Yes"></Roles>

    <Comments COPYALL="Yes"></Comments>

    </CreatePolicy>

## Schema Example

    <CreatePolicy>

    <Policy PLAN = "Plan:PlanGUID" COPYSOURCE = "Yes|No" >

    <Fields>

    <Field>

    <From></From>

    <To></To>

    </Field>

    </Fields>

    </Policy>

    <Segments>

    <Segment SEGMENTNAME = "" COPYSOURCE = "Yes|No" COPYALLROLES=”Yes|No”>

    <Roles>

    <Role ROLECODE = "MathVariable" CLIENTGIUD = "MathVariable" COPY=”Yes|No”>

    <Fields>

    <Field>

    <From></From>

    <To></To>

    </Field>

    <Field>

    <From></From>

    <To></To>

    </Field>

    </Fields>

    </Role>

    </Roles>

    </Segment>

    </Segments>

    <Roles COPYALL = "">

    <Role ROLECODE = "" COPYSOURCE = "Yes|No"> </Role>

    </Roles>

    <Comments COPYALL = "Yes|No">< /Comments>

    </CreatePolicy>

Copyright © 2009, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices

Open table of contents