If you have configured Parallel Activities as described in the previous recipe, all activities will be set to the status of In Progress at the same time. If you need to serialize activities inside a Parallel Activity container you must use Sequential Activities.
This recipe will show you how to work with Sequential Activities inside a Parallel Activity container.
To create Sequential Activities in a Change Request Template open the SCSM 2016 console and navigate to Library | Templates. Open the Change Request Service Pack Installation Template that we created in an earlier recipe.
Follow these steps to create a Sequential Activity:
Sequential Activities in SCSM 2016 work like the Parallel Activities described in the previous recipe by providing a single container for one or more activities.
All activities inside a Sequential Activity container are processed in a serialized order. If the Sequential Activity changes to In Progress, the first activity inside it will get the same status. All other activities will be in the status of Pending. When the first activity moves to a Completed status, the next activity will change to In Progress, and so on. When the last activity in a Sequential Activity container is marked as Completed the Sequential Activity container will also be marked as Completed.
Sequential Activities can be used inside a Parallel Activity container if some activities need to be serialized. For instance, in this recipe we used the example of installing the Service Pack in parallel on different systems, but we need to install the Service Pack on two servers in a sequential order.
Here is some more information on how to work with the different types of Activities in SCSM 2016.
Please look at the following recipes in this chapter to see how to work with different types of activities in SCSM 2016:
Microsoft TechNet Library: Managing Changes and Activities in System Center - Service Manager: https://technet.microsoft.com/en-us/system-center-docs/sm/manage/ops-managing-changes-and-activities-in-system-center-2016-service-manager.
3.15.27.232