Priorities for Orders in a lock instruction

Current Situation

• The JS7 does not implement priorities for orders. If a number orders is waiting for a Resource Lock or for a Process Limit (with an Agent or Subagent Cluster) then they will be continued in arbitrary order acquiring the Resource Lock or a free process.
• Users would like to prioritize specific orders
  • to acquire a Resource Lock at the next possible occasion,
  • to use the next free process from a Process Limit.

Desired Behavior
Order Prirorities are assigned from integer values:

• A higher number represents a higher priority.
• The default priority value is 0 (normal).
• The range is from -2147483648 to 2147483647.

The functionality includes that

• Priorities are considered when orders are waiting for a Resource Lock
• Priorities can be assigned when creating orders from schedules, from file order sources and when adding ad hoc orders on demand,
• Priorities can be modified at any point in time in the life of an order.

When creating child orders from the Fork-Join Instruction or ForkList-Join Instruction, then child orders will inherit the parent order's priority. This similarly applies when adding orders from the AddOrder Instruction.

Delimitation

• Implementation of Priorities for job process limits will be in scope of a later feature.
• Order Priorities for Resource Lock Instructions are resolved by the Controller, for process limits Order Priorities will have to be resolved by the Agent.