Job plans
Job plans for release management can be divided into two categories: workorder-level job plans, which provide a structure for processing an entire release, and activity-level job plans, which contain a group of related tasks. You can use one or more activity-level job plans as part of a workorder-level job plan.
A job plan that is included as part of another job plan, such as an activity-level job plan, is called a nested job plan.
You can easily assign a job plan to a Release; when you do so, the Release is automatically populated with the activities and tasks that are contained in the job plan. You can modify the activities and tasks from within the Release without changing the job plan.
You can view a list of all of the job plans that are available with this product by clicking
. You can access complete information about the structure of job plans; instructions for modifying, removing, and creating job plans; and help with managing a workable collection of job plans for your data center. If you create your own customized job plans, you can use a built-in job plan as a starting point. You can include any of the nested job plans and any of the tasks that are defined within the nested job plans.Because workorder-level job plans encompass entire release processes, they are assigned the type Process. Sequential sets of nested job plans (of the type Activity) contain sequential sets of tasks.
Job plans that are shared with other process managers
The PMRELDB, PMRELMW, and PMRELSB job plans correspond to similarly named and structured job plans that are provided with change management, and with the Service Catalog component.
You can manually substitute an activity or task in any of these job plans with the corresponding activity or task in either of the job plans provided with the other process managers. You can also pass the operation off to one of the other process managers, so that the operation is fulfilled using that process manager's job plan.