I've got a good feeling about this one. The work order has to be in the Draft state to set dependencies between the tasks. That way you can plan out the workflow before finalizing the order.
Ah, I remember learning about this in class. I believe the correct answer is that the work order request must be in the Draft state in order to set dependencies for the tasks.
I'm a bit confused on this one. I know dependencies can be set, but I'm not sure which specific state that's allowed in. I'll have to review my notes on work order management.
Okay, let's see. The question is asking about the state a work order request must be in to set dependencies. I'm pretty sure it's one of the earlier states, like Draft or Approved.
I'm stumped on this one. Maybe the answer is A) Draft, since that's where you start before the work order gets approved and qualified. *scratches head*
D) Waiting Approval seems like the obvious choice here. You need the work order to be in a state where it's waiting for approval before you can set dependencies.
I'm not sure, but I think it could also be in Waiting Approval state to set dependencies. It makes sense to wait for approval before setting dependencies.
Frederic
9 months agoClemencia
10 months agoMelinda
10 months agoSharika
10 months agoMarylin
10 months agoMelodie
11 months agoBarrett
11 months agoSarah
11 months agoKaron
11 months agoRosendo
11 months agoOmer
11 months agoFrancoise
11 months agoRegenia
11 months agoRosendo
11 months agoLaurel
1 year agoKaran
1 year agoOtis
1 year agoAbraham
1 year agoTrina
1 year agoJutta
1 year agoMarkus
1 year agoDonette
1 year agoSharika
1 year agoAmina
1 year agoAlbina
1 year agoLang
1 year agoMaia
1 year ago