CycleSequence
OIPA supports the ability to run companies and plans through cycle in a predefined order or sequence. Normal day-to-day cycle processing may be defined in one or more of these sequences. Planned business conditions such as month-end or market closures, may require an alteration of the normal cycle. Sequences allow development of alternative execution orders for the plans and/or companies. Occasionally unplanned business conditions exist which require further alterations of the normally planned cycle. The client’s scheduler can execute individual sequences directly as needs arise and with the individual client’s acceptance to such cycle changes.
The CycleSequence rule holds the definition for all sequences.
- A sequence may be a complete definition of a cycle representing all companies, plans and levels.
- It may break up cycle into a number of sequences to increase flexibility for cycle variability.
- It may combine these two methods as desired.
It is then a client scheduler’s responsibility to call the appropriate sequences necessary, in the proper order, to complete a cycle that is appropriate for a given business condition. Plans listed in a level are executed in the order in which they are configured within that level. Levels are executed in the order in which they are configured within the sequence. Policy level processing (TYPECODE=”03”) is the only multi-threaded level. Once a sequence is started, it will execute the entire contents of the sequence to completion (except in the case of catastrophic error).
If the CycleSequence rule does not exist, cycle processing executes as it did in previous OIPA versions.
Element/Tag | Attribute | Definition | Element/Attribute Value and Description |
---|---|---|---|
<CycleSequence> |
|
Opening element for the rule. |
|
<Sequence>
|
|
Required, repeatable element: Opening element for the defined sequence. |
|
NAME |
Required attribute: Unique identifier for cycle scheduler to call a specific cycle ‘playlist’. |
Text |
|
<Level>
|
|
Required, repeatable element: Opening element for the defined sequence level. |
|
TYPECODE |
Required attribute: Required identifier of the sequence level. Value may be repeated within a defined sequence. |
Code value from AsCodeCycleType (01) Pre-company |
|
<Plan> |
|
Required, repeatable: Identifies the Plan GUID to execute at the specified sequence level. Must be unique within a defined level. |
Literal PlanGUID from AsPlan |
XML Example
<CycleSequence>
<Sequence NAME="Daily">
<Level TYPECODE="01">
<Plan>01616C8F-4430-4F11-9257-B23626C50E99</Plan>
<Plan>732B6635-A468-49FC-A65C-1A78311A6EFB</Plan>
<Plan>F2B797BC-CE3B-49E7-B706-CC4B7D65DAE4</Plan>
<Plan>C5EE0DA4-3003-42C1-9468-D91DA546B79F</Plan>
. . .
</Level>
<Level TYPECODE="02">
<Plan>01616C8F-4430-4F11-9257-B23626C50E99</Plan>
<Plan>732B6635-A468-49FC-A65C-1A78311A6EFB</Plan>
<Plan>C5EE0DA4-3003-42C1-9468-D91DA546B79F</Plan>
. . .
</Level>
</Sequence>
<Sequence NAME="MonthEnd">
<Level TYPECODE="01">
<Plan>C5EE0DA4-3003-42C1-9468-D91DA546B79F</Plan>
<Plan>01616C8F-4430-4F11-9257-B23626C50E99</Plan>
<Plan>732B6635-A468-49FC-A65C-1A78311A6EFB</Plan>
<Plan>F2B797BC-CE3B-49E7-B706-CC4B7D65DAE4</Plan>
. . .
</Level>
<Level TYPECODE="02">
<Plan>01616C8F-4430-4F11-9257-B23626C50E99</Plan>
<Plan>732B6635-A468-49FC-A65C-1A78311A6EFB</Plan>
<Plan>C5EE0DA4-3003-42C1-9468-D91DA546B79F</Plan>
. . .
</Level>
</Sequence>
</CycleSequence>