Add JITL OrderStateTransitionJob

Feature

• The JITL OrderStatusTransitionJob is added to JS7 to transition order states.
• The job can be parameterized
  • for order states that require user intervention such as failed, suspended, prompting.
  • for the duration for which the order state persists when the order is in state FAILED.
  • for the desired state transition such as
    • failed => cancelled
    • failed => inprogress
    • suspended => cancelled
    • suspended => inprogress
    • prompting => cancelled
  • for the scope of affected workflows  
    • by specifying a list of folders, optionally recursive (folder/name/*)
    • by specifying glob search patterns for the workflow name (myWorkflow, my?orkflow)
  • for the scope of affected orders
    • by specifying glob search patterns for the order name
• Duration, order state and scopes are additive to create a result list of matching orders
• Users are free to create a schedule for the job at their will

Parameterization

controller_id
Default: Actual controllerId

workflow_folders
A list of workflow folders that contains the orders. Items sepearated by semicolon. When ending with /* the folder will be searched recursivly.
Example: /folder/sub1;/another_folder/sub2/*

workflow_search_patterns
A list of search patterns for workflow folders that contains the orders. Items sepearated by semicolon.
Example: myWorkflow, my?orkflow

order_search_patterns
A list of search patterns for order names. May contain a folder. Items sepearated by semicolon.
Example: myWorkflow, /folder/sub1/my?orkflow

persist_duration
Available for FAILED orders.
Example: 2d

state_transition_source
The source order state. Possible values: failed, suspended, prompting.

state_transition_target
The target order state. Possible values: cancelled, inprogress.

batch_size (default: 1000)

The number of orders that are transitioned in a single transaction. This includes that either all orders in a transaction are transitioned or none. If the number of orders  exceeds the batch size then a further transaction is executed. 

If the value batch_size = 1 is used then each order is transitioned individually with a successful or failed result. 

The batch size should not exceed a value of approx. 15 000 in order to limit the size of requests to the Controller to approx. 4 MB which is a frequently applied limit of Proxy Servers that might be in place between the Agent running the job and JOC Cockpit.