EligibleTransactionsByPolicyStatus

This business rule lists all eligible transactions that can be added to a policy based on the policy status.  The activities can be both user defined and spawned (i.e., system defined activities). The business rule can be overridden at the plan level.

EligibleTransactionsByPolicyStatus Elements/Attributes
Element/Tag Attribute Definition Element/Attribute Value and Description

<EligibleTransactionsByPolicyStatus>

 

The required opening and closing elements of this business rule.

  

<PolicyStatus> 

CODE

Required:

To indicate the policy's status where the list of activities should be available in the Policy Activity screen.

Required:

String:Policy status code from AsCodeStatus. 

NAME

Required:

The name of the policy status.

Optional:

String: Description of the PolicyStatusCode.

<Transaction> 

  

Required: Repeatable Element:

Indicates transaction name that should be available in the specified policy status.

 String:

TYPE

Defines whether the transaction is user-generated or spawned by the system.

User: Transaction can be user generated or spawned.

System: Transaction can only be spawned.

<Tests> 

 

Optional Element:

Indicates the start and end tag of the Test elements and definition.

1) <Tests> tag are used to limit the transactions on the activity screen based on the another field in the Policy screen.

2) Also used to limit activities from processing based on an activity/transaction already processing. For example, once a DCA Start processes, DCA Start should no longer be available.  

  

<Test>

 

Required, Repeatable Element:

Defines the Expression to compare a PolicyField to validate the Transaction Value. If more than one <Test> tags are used, all the Test conditions should be satisfied in order for the transactions to be listed when the policy is in the indicated status.

 String: Test criteria expression. 

<Transactions>

 

The start tag and end tag for transactions controlled by test elements.

String:  Policy:POLICYFIELD Boolean Operator "VALUE".

<Transaction> 

TYPE

Indicates the transaction name that will be available in the specified policy status, if all test conditions are true.

User: Transaction can be user generated or spawned.

System: Transaction can only be spawned.

XML Example

<EligibleTransactionsByPolicyStatus>
<PolicyStatus CODE="36" NAME="Withdrawn">
<Transaction TYPE="User">Reopen</Transaction>
<Transaction TYPE="User">AgentNotification</Transaction>
<Transaction TYPE="System">AgentNotification</Transaction>
</PolicyStatus>
<PolicyStatus CODE="04" NAME="Canceled">
<Transaction TYPE="User">Reopen</Transaction>
</PolicyStatus>
<PolicyStatus CODE="41" NAME="Decline">
<Transaction TYPE="User">Reopen</Transaction>
</PolicyStatus>
<PolicyStatus CODE="48" NAME="Postpone">
<Transaction TYPE="User">Reopen</Transaction>
</PolicyStatus>
</EligibleTransactionsByPolicyStatus>

XML Schema

<EligibleTransactionsByPolicyStatus>
<PolicyStatus CODE="[Code]" NAME="[String]">
<Transaction TYPE="[System | User]">[String]</Transaction>
<Tests>
<Test>[Expression]</Test>
<Transactions>
<Transaction TYPE="[System | User]">[String]</Transaction>
</Transactions>
</Tests>
</PolicyStatus>
</EligibleTransactionsByPolicyStatus>