You are here: Business Rules > Attached Rules > CreatePolicy

CreatePolicy

Description

The business rule is introduced to provide the ability to configure the 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 will be supported. All policies will be created in a pre-issue status pending user review. The CreatePolicy business rule will 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.
<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 math variable of activity field If the created policy is for a different plan, then all policy data must be specified.
		PLAN	Optional: Valid plan name or PlanGUID. 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.) 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 CreatePolicy > Policy > Fields should 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 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 math variable, activity field or literal. Reference to an activity field must have a prefix of “Activity:”.
<To>	Required: Indicates the policy field the value of the <From> element will be copied to.		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.
<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. 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 CreatePolicy>Segments > Segment > Fields rule should overwrite the defaults.
		COPYALLROLES	Optional: Indicates whether or not to copy all the segment roles from the source segment to the new segment. Yes – Segment roles will be copied.
<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 math variable, activity field or literal. Reference to an activity field must have a prefix of “Activity”.
<To>	Required: Indicates the segment field the value of the <From> element will be copied to.		Any valid segment field name defined by the SegmentName business rule.
<Roles>	Optional: Defines the Roles to create for the new policy. Role creation is supported by three options: copy all roles, copy specified roles by role code and add new roles.
<Roles>		COPYALL	Optional: Indicates whether the all Roles from the source policy are copied to the new policy. Yes – Roles will be copied.
<Role>	Required, Repeatable: The opening and closing elements that defines the roles to assign to the new policy. This section is repeated for each role to create.
		ROLECODE	Required: Identifies the role code to create. A code value from AsCodeRole.
		COPYSOURCE	Optional: All information from like Roles of the source policy is copied to new Roles on the target policy. Yes – Roles will be copied. No - A blank role is created from the business rule and the user has the option to overwrite the role columns from within the CreatePolicy rule.
<Comments>	Optional: Defines comments to associate with the new policy. Data is populated from either the source policy or the activity itself.
<Comments>		COPYALL	Optional: Allows comments to be copied from the source policy. Yes: – comments are copied.

CreatePolicy Database Tables
Table Name	Description
AsAddress	Stores client address information: physical address, e-mail, phone.
AsAddressField	Stores address information organized by guaranteed user identification.
AsAddressRole	Associates a client with an address. Clients may have several addresses of varying types and several clients may share the same address.
AsClient	Stores personal information about clients.
AsCode	Contains a list and description of all valid codes and their values.
AsRole	Contains role information.

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>

<Fields>

<Field>

<From>ContractEffectiveDate</From>

<To>StartDate</To>

</Field>

</Fields>

</Segments>

<Roles COPYALL="Yes">

<Role ROLECODE="01" COPYSOURCE="Yes"></Role>

<Role ROLECODE="27" COPYSOURCE="Yes"></Role>

<Role ROLECODE="07" COPYSOURCE="Yes"></Role>

<Role ROLECODE="40" COPYSOURCE="Yes"></Role>

</Roles>

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

</CreatePolicy>

Schema Example

<CreatePolicy>

<Policy PLAN="[plan name]" COPYSOURCE="[No|Yes]">

<Fields>

<Field>

<From>[math variable|activity field|literal]</From>

<To>[field name]</To>

</Field>

</Fields>

</Policy>

<Segments>

<Fields>

<Field>

<From>[math variable|activity field|literal]</From>

<To>[field name]</To>

</Field>

</Fields>

<Segment SEGMENTNAME="[segment name]" COPYSOURCE="[No|Yes]" COPYALLROLES="[No|Yes]">

<Fields>

<Field>

<From>[math variable|activity field|literal]</From>

<To>[field name]</To>

</Field>

</Fields>

</Segment>

</Segments>

<Roles COPYALL="[No|Yes]">

<Role ROLECODE="[Code]" COPY="[No|Yes]">

<Fields>

<Field>

<From>[math variable|activity field|literal]</From>

<To>[field name]</To>

</Field>

</Fields>

</Role>

</Roles>

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

</CreatePolicy>