You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

UNDER PROGRESS

 

Known Issue Status

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

Behavior

  • Passed Test Case
    • Starting Situation
      • A nested job chain has three nodes A, B and C
      • Node A and C has the same sub job chain
    • Action
      • Add a order i.e. Main_Order to the nested job chain
      • Open JOC, righ click on the order Main_Order and start now
    • Behavior
      • Order Main_Order will start at two nodes i.e. Node A and Node C,since  the same job chain is assigned to both of the nodes.
  • 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 as one of the state of sub job chain.
    • Behavior
      • Order will can not be set to sub job chain's state
  • Explanation
    • A nested job chain has other job chains as nodes, so for a order submitted to a  nested job chain , state is ideally a sub job chain.
    • In a practical scenario when job chains are organized under nested job chain, order's state can be set to one of the sub job chain.
    • As of now we don't see any real use case where order assigned to nested job chain need to be assigned to state in sub job chain.

Requirement

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

Workaround

  • Not Available  

 

  • No labels