Skip to end of metadata
Go to start of metadata

 

Known Issue Status

Occurrence KNOWN ISSUE OCCURRING FROM RELEASE 1.3  
Change Management Issue JS-1255 - Getting issue details... STATUS  

Behavior

  • Passed Test Case
    • Starting Situation
      • In a nested job chain an order is wating to be executed.
    • Action
      • Open the JOC, right click on the order and select the order state.
    • Behavior
      • The order can only be assigned to the states of the nested job chain but not to any state of a sub job chain.
  • Failed Test Case
    • Starting Situation
      • as above
    • Action
      • Open the JOC, right click on the order and select the order state, try to set the order's state to the state of a sub job chain.
    • Behavior
      • The order cannot be set to the sub job chain's state.
  • Explanation
    • A nested job chain includes other job chains as nodes, so for an order submitted to a nested job chain, the state is ideally a sub job chain.
    • In a practical scenario when job chains are organized under nested job chain, then the order's state can be set to one of the sub job chains.

Requirement

  • In a nested job chain the order's state can be assigned any state of a sub job chain.

Workaround

  • For ad hoc orders, i.e. with option "add order" from JOC, "Select an order state" option is available.  

Resolution

  • This behavior will not be fixed. As of now we don't see any real use case where permanent orders of a nested job chain need to be assigned to a specific state in a sub job chain. The workaround can easily be applied by using an ad hoc order that could be assigned any state of a sub job chain. 

 

  • No labels
Write a comment…