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
3 months agoClemencia
4 months agoMelinda
4 months agoSharika
4 months agoMarylin
4 months agoMelodie
5 months agoBarrett
5 months agoSarah
5 months agoKaron
5 months agoRosendo
5 months agoOmer
5 months agoFrancoise
5 months agoRegenia
5 months agoRosendo
5 months agoLaurel
10 months agoKaran
9 months agoOtis
10 months agoAbraham
10 months agoTrina
10 months agoJutta
11 months agoMarkus
11 months agoDonette
10 months agoSharika
10 months agoAmina
11 months agoAlbina
11 months agoLang
11 months agoMaia
11 months ago