This documentation supports the 18.08 version of Change Management.

To view the latest version, select the version from the Product version menu.

Entering task template details

Here you define important task template details, for example, the type of task or the application it applies to.

To enter information in the top pane of the form

  1. On the Task Template form, fill in the required fields.

    Field name



    The company to which this variable applies.


    The name of the task template.


    A brief description of the purpose of this task template.

    Template Category Tier 1

    Select the Template Category Tier 1 categorization from the associated field menu. The content of the Template Category Tier 1 menu corresponds to the installed BMC Remedy IT Service Management applications for which you can create tasks. The menu is populated by the active records in the Integration Configuration form. For information about integrations, see Configuring integrations.

    You can categorize task templates under a three tier hierarchy. The tiers help you to organize related templates. The Tier 1 categorization is mandatory, while Tier 2 and Tier 3 (which are described in the Optional Fields table) are optional.  


    Change Management System -> VM -> Provision
    Change Management System -> VM -> Extend


    The type of task template. The options are as follows:

    • Manual — Requires a person to take a certain action. Usually, the person is notified of their assigned task.
    • Automatic — Performs automatic action, for example, rebooting a server. If you select this option, you must specify an automatic command on the Automatic tab before you can save the task template. For more information, see Creating automatic tasks.


    The status of the task template. The options are as follows:

    • Active — Enables the template for use during the execution stage
    • Inactive — Deactivates the template. Inactive objects cannot be used at runtime. Usually, you set an object to Inactive when it is no longer used at runtime, but might be needed again in the future. When it is needed again, you can reset it to Active.
    • Potential — Puts the template into inactive status. You can design the template without activating it.
  2. Fill in the optional fields.

    Field name



    The application to which group of templates this one belongs. The menu is data-driven by active records in the Integration Configuration form. For information, see Configuring integrations.


    An optional sub-category description.

    Template Category Tier 2 

    Create or select the appropriate template Tier 2 categorization.

    • To create a Template Category Tier 2 categorization, type the category name in the Template Category Tier 2 field. When you save the template, the category name is also saved and added to the field's selection list, where it is available to select when you create the next template.
    •  To select a Template Category Tier 2 categorization, open the Template Category Tier 2 field menu and select the categorization.
    Template Category Tier 3

    Create or select the appropriate Template Tier 3 categorization.

    To do this, use the same method described for creating or selecting Template Category Tier 2.


    A description of the variable template's function or any other helpful text for future administrators and designers.


    The priority of the task template. The priority is applicable during the execution stage.


    Indicates whether this template is visible or hidden to the user for selection during the execution stage.


    The locale to which this template is applicable.
  3. Click Save.
  4. From the General tab, you can specify commands and their parameters, and if the task template is global or used by a specific company.

To enter information in the General tab

  1. On the General tab of the Task Template form, enter the indicated information in the fields that are grouped as shown in the following table:

    Field group name


    Task Location area (Required)

    Company information in the Task Location fields. This task template is specific to the company you select.

    The Region, Site Group, and Site fields are dynamic, which means that the values you can select from these fields are dependent on the previous selection.

    Note: The Company field is on the General tab.


    A Launch Command or Details Command that executes at runtime. Some best practice commands are provided for use when TMS is being used with the BMC BladeLogic Client Automation applications. Additional commands can be defined for any other third-party application.

    • A Launch Command is the TMS_OUT_CMS_POLICYMGR used with the BMC BladeLogic Client Automation Policy Manager task template.
    • A Details Command is the TMS_OUT_CMS_CHKCOMPLIANCE_STATUS used with the Closed Loop Verification task template to set up compliance parameters for Closed Loop Verification.

      For more information, see Application and task integrations.

    Task Attachments

    Attachments that might be necessary for this task template. Attachments might be how-to documents that helps the user complete the task when the template is used during the execution stage.

    Time Out

    The timeout value, status, and status reason for the time out. The timeout value is applied to the Activate time field on the runtime objects. If this timeout value is reached, then the Task or Task Group is set (by an escalation of ten minute intervals) to the predefined status value.

    Note: The clock stops when a Task or Task Group is in Pending status.

    The fields in the Time Out section are:

    • Time Out Value — The amount of time after which the task times out at runtime.
    • Unit — Seconds, minutes, hours, or days.
    • Time Out Status — The status that is set when time out is reached.
    • Time Out Status Reason — A corresponding status reason for the status value, if applicable.

    Both the Launch Command and Details Command on the General tab of the Task Template form are features that, on the runtime task form, require manual intervention to drive them. In both cases, the user must click a button.

    • Only manual task templates should have launch commands. All of the CCM manual task templates have examples of Launch Command.
    • Automatic tasks can have a Details Command. Users might get assigned to monitor such a task, and they might want to do a manual check on an external application, for example, as with the Closed Loop Verification (automatic) task template for CCM.
      For more information, see Predefined task group and task templates.
  2. (Optional) Click the Define Commands button to view existing commands or create a new command.


    Applications for which commands are being defined must be registered in the CAI.

    Commands are defined and stored in the Command Automation Interface (CAI) forms. Every command consists of the following items:

    • Command — Construct a command that is executed at runtime. Commands are static values, for example, Send.
    • Parameter — Construct a parameter for the command. Parameters are dynamic values that are defined at runtime from the Tasks form.
      For more information, see Command Automation Interface   and Defining command parameters in the BMC Remedy IT Service Management Configuration documentation.
  3. Click Save.
  4. Continue setting up the task template, as described in Classifying the Task Template form.
Was this page helpful? Yes No Submitting... Thank you