ActivitySequenceProcess Element
This element in Transaction configuration allows Activities to be generated with an option to immediately attempt processing the generated Activities. Generation and the optional immediate processing will complete before the current Activity completes its processing. If the generated Activities are not configured to process immediately following activity generation, the Activities are only generated and left for a batch cycle or separate user execution.
Element | Attribute | Parent Element | Description |
---|---|---|---|
<ActivitySequenceProcess> | <Transaction> |
Optional: This section defines activity spawns through the Activity Sequence functionality. |
|
<ActivitySequence> | <ActivitySequenceProcess> |
Required, Repeatable: This section allows the user to name the Activity Sequence and provide the conditions upon which it will generate activities. All the generated activities within the <Activity> child elements contained by this element are part of the same sequence. Activities of the same sequence must be generated and optionally processed before the next <ActivitySequence> element begins its generation and optional processing. |
|
NAME | <ActivitySequence> |
Required: This provides a name to the sequence that can offer an ability to track the sequence's processing. Values:
|
|
IF | <ActivitySequence> |
Optional: This attribute allows configuration to provide the conditions that must evaluate to true to begin processing the sequence. A false value skips all activities contained within this sequence from generation. Processing then moves to the next <ActivitySequence> element. Values:
|
|
<Activity> | <ActivitySequence> |
Required, Repeatable: This element provides a single transaction name to generate as an activity on the current entity or an array of activities to generate on the current entity or another entities. An Activity array can spawn activities to other entities: Client or Group Customer parent to Policy children, Policy parent to Client children, Company parent to Policy children, etc. Generated activities may be processed within the processing scope of the parent Activity and delay the completion of the parent until all children have completed or simply use this sequence structure for a simple spawn without processing the child activities. Values:
|
|
PROCESSIMMEDIATE | <Activity> |
Required: This attribute is the trigger to execute the child activities within the processing scope of the parent activity. Values:
|
|
IF | <Activity> |
Optional: This attribute allows configuration to provide the conditions to evaluate. When the result is true, the process generates the <Activity> element's activities. When false, activity processing skips generation of the <Activity> element's activities and moves to the next <Activity> element. Values:
|
XML Schema
<Transaction> ... <ActivitySequenceProcess> <ActivitySequence NAME="[name]" IF="[condition]"> <Activity PROCESSIMMEDIATE="[No | Yes]" IF="[condition]">[transaction name | activity array]</Activity> <Activity>...</Activity> </ActivitySequence> <ActivitySequence>...</ActivitySequence> </ActivitySequenceProcess> ... </Transaction>
XML Example
<Transaction> ... <ActivitySequenceProcess> <ActivitySequence NAME="PolicyTrxB"> <Activity PROCESSIMMEDIATE="Yes" IF="SelectOperationMV = 'Multiple'">BBBBBActivityArray</Activity> </ActivitySequence> <ActivitySequence NAME="PolicyTrxC"> <Activity PROCESSIMMEDIATE="Yes" IF="SelectOperationMV = 'Multiple'">CCCCCActivityArray</Activity> </ActivitySequence> </ActivitySequenceProcess> ... </Transaction>