Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Define task templates

Define task templates

Each execution plan contains one or more task templates that define actions that must be taken to fulfill a request.

About this task

To define an execution plan task template:


  1. Navigate to Service Catalog > Catalog Policy > Execution Plans.
  2. Open an execution plan.
  3. In the Execution Plan Tasks related list, click New.
  4. Fill in the fields on the Execution Plan Task form (see table).
  5. Click Submit.
    Figure 1. Cat DP Task1
    Table 1. Defining Task Templates
    Field Description
    Name Name of the task. This becomes the created task's name.
    Fulfillment group The group that performs the task. Whenever a user requests a catalog item associated with this execution plan, the task is automatically assigned to the fulfillment group. Leave blank if automatic assignment to a group is not required.
    Assigned to The individual who performs the task. Leave blank if automatic assignment to a user is not required.
    SLA The service level agreement that applies to catalog items associated with this execution plan.
    Note: This field is normally left blank, as the functionality has been superseded by the service level management functionality.
    Delivery plan The parent execution plan for this task.
    Order A number representing the task's sequence in the execution plan. It is good practice to "leave gaps" between order numbers (for example, 100, 200, 300, and so on) so you can insert new tasks without changing the order number of existing tasks.

    (If the order for several execution plan tasks is the same, each of these tasks starts at the same time.)

    Delivery time Amount of time the task is expected to take. This value becomes a component of the overall time to complete the execution plan.
    Condition Condition under which the task is performed (if the condition is not met, the task is skipped).
    Short description Brief description of the task's activity. This information populates the created task's short description field.
    Instructions Details of the activities to be performed for the task. This information populates the created task's description field.
    Work notes A journal field for entering comments about the task template. Note: this information is separate from the created task's work notes field.