I have had a several customers who required implementation change tasks to be activated in a sequential order.

In this case, the implementation tasks should be created before the change is submitted for approval and uses the “Change Task Type” and the “Implementation” option.

Firstly, an “Add Implementation Task” related link UI Action has been added to the change form which creates a related change task and sets the state to “Pending”. This is only visible when the change is in a “New” state.

The ootb “Order” field has been added to the change task form. This is where the change raiser can state what order the change task needs to be opened and completed.

If you have multiple tasks that need to be activated simultaneously, you can give them the same order.For Example: –Task 1a – Order 100Task 1b – Order 100Task 2 – Order 200Task 3a – Order 300Task 3b – Order 300

Task 4 – Order 400

I have created a workflow that can be dropped into your change workflow.

– Workflow Activity 1: – Run Script counts the implementation tasks in a pending state related to the change and queues the tasks in the order they need to be activated. I have passed values using the workflow scratchpad so they can be called upon later in the workflow.

– Workflow Activity 2: – If Condition to check if there are any implementation tasks in a pending state;– if the count is greater 0, it moves onto the next activity

– if the count is 0, it moves the workflow to “End”

– Workflow Activity 3: – This sets the queued implementation tasks to an “open” state;

– Workflow Activity 4: – Wait for condition waits for the active implementation tasks to complete.

The workflow then loops until all pending implementation tasks are complete.

I have added the update set to the ServiceNow Share site: –

https://share.servicenow.com/app.do#/detailV2/d42e770cdba09b00b960a6e51b96195b/overview

Labels: