ServiceNow CIS-FSM free question 4 / 10 · Domain 1: Field Service Management Fundamentals
A work order has two work order tasks, and the second one must not start before the first one is finished. A qualifier opens one of the tasks and clicks New in the Depends on related list to create a Finish to start dependency. According to the Create dependencies between work order tasks page, which condition must be true for the dependency to be created?
- Neither the predecessor task nor the successor task is assigned yet
- The predecessor task is assigned, and the successor task is not yet
- Both tasks are already assigned, to the same agent or to two agents
- The successor task is assigned, and the predecessor task is not yet
Show the answer and explanation
Answer: A
Why this is correct
The Create dependencies between work order tasks page explains that, when a work order contains several tasks, dependencies determine the order in which the tasks are performed, whether one agent or several agents do the work. The dependency type table lists Finish to start, the default type, together with two Finish to start variants that tie the tasks to the same agent or to the same day and the same agent, and two types that need the Field Service Task Dependency plugin. Directly under the table, a note sets the condition for creating any of them: dependencies can be created only when the predecessor and successor tasks are not assigned. This fits the purpose of the feature. A dependency is meant to shape how the tasks are assigned and scheduled, so it has to be in place while both tasks are still waiting for an agent.
Why the other options are wrong
"The predecessor task is assigned, and the successor task is not yet" … The note under the dependency type table covers both ends of the relationship: dependencies can be created only when the predecessor and successor tasks are not assigned. An assigned predecessor already breaks that condition, so the qualifier has to create the dependency before the first task is assigned to anyone.
"Both tasks are already assigned, to the same agent or to two agents" … Some dependency types say that the successor and predecessor should be assigned to the same agent, but that describes how the two tasks are to be assigned later. The note asks for the opposite at the moment of creation: neither task may be assigned yet.
"The successor task is assigned, and the predecessor task is not yet" … An assigned successor fails the note in the same way as an assigned predecessor. The page states that dependencies can be created only when the predecessor and successor tasks are not assigned, so the order in which the tasks were assigned does not matter.
The steps on the page
You navigate to the work order, open a work order task, and click New in the Depends on or Dependents related list. On the form you choose the Successor, the Dependency type, and the Predecessor, and you can enter a maximum or minimum lag time before you click Submit. A single task can have more than one dependency.
Go to the ServiceNow CIS-FSM practice app (10 free questions; purchase unlocks all questions)