Haha, this question is a real brain-teaser! I'm going to go with B and D, just to be safe. Manually adding Change Tasks seems like the way to go, and I definitely don't want to get caught trying to do it during the Closed or Canceled states.
Hmm, I'm a bit confused. I thought the correct answers were A and C - automatically adding the Change Tasks based on the category selected on the Change Request, and via the Change - Implementation subflow. But I could be wrong.
Actually, I believe it's A and C - automatically adding Change Tasks via the Change - Implementation subflow and depending on the category selected on the Change Request.
I think the correct answers are B and D - adding Change Tasks manually during New, Assess, and Authorized states, and during all states except Closed or Canceled.
I'm pretty sure the correct answers are B and D. The user should be able to manually add Change Tasks during the New, Assess, and Authorized states, as well as during all states except Closed or Canceled.
I think A and D are the correct answers. The Change - Implementation subflow should automatically add the Change Tasks, and we can manually add them during all states except Closed or Canceled.
I think both of you are correct. Change Tasks can be added automatically depending on the category selected on the Change Request, and also manually during all states, except Closed or Canceled.
Jessenia
1 months agoLeah
4 days agoLeonor
10 days agoJunita
2 months agoCyndy
1 months agoErasmo
1 months agoFrancesco
1 months agoCristy
2 months agoClorinda
2 months agoElenore
2 months agoSuzan
2 months agoEugene
2 months agoRozella
2 months agoFannie
3 months ago