CreatePolicy

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 Elements/Attributes
Element/Tag Attributes Definition 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 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.

<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>

 

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.

<MultiFields>   Optional, repeatable element: Defines the multifields to be updated/inserted  
  Note: The system will validate named "To" fields against the field name in the MultiField rule for the PolicyScreen rule.
  NAME Required: Specifies the named section of the related entity's Multifield rule. Literal name
  END Required: Specifies the total number of instances of multifields for the named section of the related entity's Multifield rule. If NAME is omitted or does not exist in the MultiField rule, all the fields in the MultiField rule will be repeated for "END" number of times. Literal Integer or Integer Math Variable
<Field>   Optional, repeatable element: Contains the instructions for the specified "To" field. This element (and sub elements) may be omitted if the default field values are desired.  
<FromIndexCollection>   Required: A collection of index/value pairs for the target fields. Indices must be unique integers Math variable collection of index/values.
<To>   Required: The target named field in the entity multifield rule Literal 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.

  PLANSEGMENTNAMEGUID Optional: Indicates if PLANSEGMENTNAMEGUID needs to be populated for the new segment. By default, it would not be populated. A MathVariable, Activity field .

<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.

<MultiFields>   Optional, repeatable element: Defines the multifields to be updated/inserted  
  Note: The system will validate named "To" fields against the field name in the MultiField rule for the SEGMENTNAME (AsSegmentName) specified.
  NAME Required: Specifies the named section of the related entity's Multifield rule. Literal name
  END Required: Specifies the total number of instances of multifields for the named section of the related entity's Multifield rule. If NAME is omitted or does not exist in the MultiField rule, all the fields in the MultiField rule will be repeated for "END" number of times. Literal Integer or Integer Math Variable
<Field>   Optional, repeatable element: Contains the instructions for the specified "To" field. This element (and sub elements) may be omitted if the default field values are desired.  
<FromIndexCollection>   Required: A collection of index/value pairs for the target fields. Indices must be unique integers Math variable collection of index/values.
<To>   Required: The target named field in the entity multifield rule Literal field name

<Roles>

Optional Element:

Begins policy role configuration.

 
COPYALL

Cannot coexist with ROLECODE.

Yes|No attribute values

<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

Cannot coexist with COPYALL.

MathVariable to populate role code.

COPY

Optional Attribute

:

Yes|No attribute values

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.

 
<MultiFields>   Optional, repeatable element: Defines the multifields to be updated/inserted  
  Note: The system will validate named "To" fields against the field name in the MultiField rule for the ROLECODE code specified.
  NAME Required: Specifies the named section of the related entity's Multifield rule. Literal name
  END Required: Specifies the total number of instances of multifields for the named section of the related entity's Multifield rule. If NAME is omitted or does not exist in the MultiField rule, all the fields in the MultiField rule will be repeated for "END" number of times. Literal Integer or Integer Math Variable
<Field>   Optional, repeatable element: Contains the instructions for the specified "To" field. This element (and sub elements) may be omitted if the default field values are desired.  
<FromIndexCollection>   Required: A collection of index/value pairs for the target fields. Indices must be unique integers Math variable collection of index/values.
<To>   Required: The target named field in the entity multifield rule Literal field name

<BenefitSplits>

 

Optional Element

 

<BenefitSplit>

 

Creates a new BenefitSplit record for the segment.

 

BENEFITSPLITCOLLECTION

Adds the Benefit Funds and Amounts to the Segment.

Benefit Split Fund Collection

COPYSOURCE

Copies a specified segment’s activity benefit split based on its type code.

Note: This feature only applies if the COPYSOURCE attribute of the Segment parent element is set to Yes.

Yes | No   

TYPECODE

The target Benefit Type Code.

Benefit Type Code

<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
<Programs>   Optional Element:
Defines the pending activities to insert on a new policy.
String:
<Program>   Required and Repeatable

Defines the Program screen fields to populate.

 
  PROGRAM NAME Required Element

Specfies the name of the program to insert

String:
  PROCESS PROGRAM Optional Element:
Specifies if the named program should process upon insert or remain in the pending state. The default value is "No"
String:

"Yes" or "No"

<Tests>   Optional Element:
Specifies the the tests section
 
<Test>   Required and Repeatable

Defines the expression to evaluate before creating the Program

This is comparison expression of strings, fields or transaction math variables

<Fields>

 

Optional

Opening tag for listing program fields configuration.

 

<Field>

 

Optional Opening element for the field definition block

 

<From>

 

Required:

Defines a source for the value being applied to the field indicated by <To> and substituting for the source field value.

Field or the Transaction math variable

<To>

 

Required:

Indicates the target field for the value of the <From> element.

String:

<Activities>

 

  Optional

Opening tag to specify the pending activities to insert in a new policy.

 
<Activity>   Required and Repeatable

Defines the activity fields to populate

 
  TRANSACTION NAME Required Element

Specifies the name of the transaction to insert

String:
<Tests>   Optional Element:
Specifies the tests section
 
<Test>   Required and Repeatable

Defines the expression to evaluate before creating the Pending activity

 

<Fields>

 

Optional Opening tag for listing activity fields

 

<Field>

 

Optional Opening element for the field definition block

 

<From>

 

Required: Defines a source for the value being applied to the field indicated by <To> and substituting for the source field value.

Field or the Transaction math variable

<To>

 

Required:

Indicates the target field for the value of the <From> element.

String:
<Programs>   Optional Element:
Defines the pending activities to insert on a new policy.
String:
<Program>   Required and Repeatable

Defines the Program screen fields to populate.

 
  PROGRAM NAME Required Element

Specfies the name of the program to insert

String:
  PROCESS PROGRAM Optional Element:
Specifies if the named program should process upon insert or remain in the pending state. The default value is "No"
String:

"Yes" or "No"

<Tests>   Optional Element:
Specifies the the tests section
 
<Test>   Required and Repeatable

Defines the expression to evaluate before creating the Pending program

 

<Fields>

 

Optional

Opening tag for listing program fields

 

<Field>

 

Optional Opening element for the field definition block

 

<From>

 

Required:

Defines a source for the value being applied to the field indicated by <To> and substituting for the source field value.

Field or the Transaction math variable

<To>

 

Required:

Indicates the target field for the value of the <From> element.

String:
<ReversalProcessing>  

Optional element:

Defines the processing to be handled when the activity to which this BR is attached gets reversed

 
<ShadowOnReversal>  

Optional element:

Defines the conditions under which the Policy record(s) created from this attached BR should be Shadowed

 

<Tests>

 

Optional element:

Defines the section holding the tests to determine if the Policy record should be Shadowed on Reversal

Standard <Tests> element configuration

All Activity Fields and logged Activity Math variables can be used in Expressions under this Tests element

<DeleteOnReversal>  

Optional element:

Defines the conditions under which the Policy record(s) created from this attached BR should be deleted

In Case the test for both ShadowOnReversal and DeleteOnReversal are True then, ShadowOnReversal takes precedence

<Tests>

 

Optional element:

Defines the section holding the tests to determine if the Policy record should be Shadowed on Reversal

Standard <Tests> element configuration

All Activity Fields and logged Activity Math variables can be used in Expressions under this Tests element

XML Example

<CreatePolicy>
<Policy PLAN="Functional Prototype Plan" COPYSOURCE="No">
<Fields>
<Field>
<From>Policy:IssueStateCode</From>
<To>IssueStateCode</To>
</Field>
<Field>
<From>NewContractNumber</From>
<To>PolicyNumber</To>
</Field>
<Field>
<From>PendingStatusCode</From>
<To>StatusCode</To>
</Field>
</Fields>
</Policy>
<Segments>
<Segment SEGMENTNAME="Base Coverage" COPYSOURCE="No">
<Fields>
<Field>
<From>Policy:PlanDate</From>
<To>EffectiveDate</To>
</Field>
</Fields>
</Segment>
</Segments>
<Roles COPYALL="No">
<Role ROLECODE="11" COPYSOURCE="No">
<Fields>
<Field>
<From>NewCSRClientGUID</From>
<To>ClientGUID</To>
</Field>
</Fields>
</Role>
<Role ROLECODE="23" COPYSOURCE="No">
<Fields>
<Field>
<From>NewPBClientGUID</From>
<To>ClientGUID</To>
</Field>
</Fields>
</Role>
<Role ROLECODE="30" COPYSOURCE="No">
<Fields>
<Field>
<From>NewOBClientGUID</From>
<To>ClientGUID</To>
</Field>
</Fields>
</Role>
<Role ROLECODE="37" COPYSOURCE="No">
<Fields>
<Field>
<From>NewInsuredClientGUID</From>
<To>ClientGUID</To>
</Field>
</Fields>
</Role>
</Roles>
<Activities>
<Activity TRANSACTIONNAME="StatusChange">
<Tests>
<Test>TransactionToAddMV='02'</Test>
</Tests>
<Fields>
<Field>
<From>ActiveStatusCode</From>
<To>NewStatus</To>
</Field>
<Field>
<From>EffectiveDateMV</From>
<To>EffectiveDate</To>
</Field>
</Fields>
</Activity>
<Activity TRANSACTIONNAME="ValuesBlockNoAllocation">
<Tests>
<Test>TransactionToAddMV='01'</Test>
</Tests>
</Activity>
</Activities>
<Programs>
<Program PROGRAMNAME="ProgramB" PROCESSPROGRAM="Yes">
<Tests>
<Test>ProgramToAddMV='02'</Test>
</Tests>
<Fields>
<Field>
<From>StartDate</From>
<To>StartDate</To>
</Field>
<Field>
<From>EndDate</From>
<To>EndDate</To>
</Field>
<Field>
<From>EffectiveDate</From>
<To>EffectiveDate</To>
</Field>
</Fields>
</Program>
<Program PROGRAMNAME="ProgramA" PROCESSPROGRAM="No">
<Tests>
<Test>ProgramToAddMV='01'</Test>
</Tests>
<Fields>
<Field>
<From>StartDate</From>
<To>StartDate</To>
</Field>
<Field>
<From>EndDate</From>
<To>EndDate</To>
</Field>
<Field>
<From>EffectiveDate</From>
<To>EffectiveDate</To>
</Field> 
</Fields>
</Program> </Programs>
<ReversalProcessing>
	<ShadowOnReversal>
	<Tests>
	<Test>Expression</Test>
	</Test>
	</ShadowOnReversal>
	<DeleteOnReversal>
	<Tests>
	<Test>Expression</Test>
	</Test>
	</DeleteOnReversal>
</ReversalProcessing>
</CreatePolicy>

XML Schema

<CreatePolicy>
<Policy PLAN="[Plan Name]" COPYSOURCE="[Yes|No]">
<Segments>
<Segment
SEGMENTNAME="[literal SegmentName]" COPYSOURCE="No|YES" PLANSEGMENTNAMEGUID="[Activity Field Name/Math Variable Name]">
<Programs>
<Program PROGRAMNAME="[Program Name]" PROCESSPROGRAM=”[Yes/No]”>
<Tests>
<Test>[Condition]</Test>
</Tests>
<Fields>
<Field>
<From>[Activity Field Name/Math Variable Name]</From>
<To>[Program Field Name]</To>
</Field>
</Fields>
</Program>
</Programs>
</Segment>
</Segments>
<Roles COPYALL="[Yes|No]"> …
<Activities>
<Activity TRANSACTIONNAME="[Transaction Name]">
<Tests>
<Test>[Condition]</Test>
</Tests>
<Fields>
<Field>
<From>[Source Transaction Variable Name]</From>
<To>[Target Transaction Field Name]</To>
</Field>
</Fields>
<Multifields>
<Field>
<From></From>
<To></To>
</Field>
</MultiFields>
</Activity> </Activities>
<Programs>
<Program PROGRAMNAME="[Program Name]" PROCESSPROGRAM=”[Yes/No]”>
<Tests>
<Test>[Condition]</Test>
</Tests>
<Fields>
<Field>
<From>[Activity Field Name/Math Variable Name]</From>
<To>[Program Field Name]</To>
</Field>
</Fields>
</Program>
</Programs>

</CreatePolicy>

 

 

 

 

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