This documentation supports the 20.02 version of Remedy Change Management.

To view an earlier version, select the version from the Product version menu.

Task templates

A task template defines a unit of work that carries out a single step in handling a change. At runtime, task templates are generated as tasks. In the execution stage of a task, the Task form at runtime displays an extra tab labeled Data. This Data tab makes available a pool of fields (for example, Character01, Character02, and so on) that you can dynamically use with variable templates. The field label was updated to show the new variable name.

Tasks consist of a combination of the following components:

  • An automatic action that runs by itself and must be carried out
  • A specified action that must be accomplished
  • Data that is entered or mapped in the form of input variables
  • Data that is written from the task to another task or task group in the form of output variables

These components are configured within the task template.

Change Management, Incident Management, and Problem Management integrate different amounts of the TMS functionality. The BMC BladeLogic Client Automation integration is launched from within Change Management.

The task is the main action component of the TMS; all the work that is done toward managing and implementing a change request at runtime is carried out through tasks. In short, a task is a unit of work that is completed as a step in implementing a change request.

The administrator can create the following distinct types of task templates:

  • Manual, in which an action (for example, replacing a cable) is performed by a person
  • Automatic, in which a predefined instruction is automatically executed by the task

At runtime, you can generate tasks in the following ways:

  • Automatically as part of a task group or a change request. For example, if a change occurs and the change manager selects a task group, any tasks that are contained within the task group are generated according to how the flow has been defined.
  • By selecting from a list of task templates. For example, if a change occurs for which no task group has been defined, the change manager still has access to all defined task groups and task templates.


    If the task template has its Visible value set to No, it cannot be directly selected at runtime.

You can specifically create an ad hoc task to perform some action during a change where no defined task template is appropriate.

For additional information about creating tasks at runtime, see Viewing tasks at runtime.


Six predefined, best practice task templates are automatically installed with Change Management for integration with BMC BladeLogic Client Automation. As an administrator, you can predefine additional task templates to use with Change Management.

Was this page helpful? Yes No Submitting... Thank you