Create Incident With Template

Applies To: System Center 2012 - Orchestrator, System Center 2012 R2 Orchestrator, System Center 2012 SP1 - Orchestrator

The Create Incident with Template activity is used to create a new incident from an existing Incident Template. You have the option to overwrite template values with existing incident values or apply template values.

Important

Orchestrator does not support mandatory fields in child activities that the Create Incident with Template activity creates. These template activities will fail in Service Manager if there are mandatory fields in any of the child activities it tries to create because there is no way for the user to provide the mandatory properties for the associated activity.

The Create Incident with Template activities create an incident record by presenting the workflow author with a property grid of values associated with the change. This includes mandatory properties that will cause the create operation to be rejected by Service Manager if they are not provided.

The configuration user interface for Create Incident with Template does not provide a way to configure child work items. It can only access the parent incident. Therefore, if any of the child work items contain mandatory properties, the creation of the incident will be rejected by Service Manager.

The following published data elements are specific to Create Incident with Template activity. Additional published data is generated based on the class that you select when you define the activity. For a list of the data elements published by each class, see Service Manager Published Data.

Create Incident with Template Published Data

Element Description

Object GUID

The unique identifier (GUID) of the incident

Number of Objects

The number of objects returned by the Create Incident with Template activity

Configuring the Create Incident with Template Activity

To configure the Create Incident with Template activity

  1. From the Activities pane, drag a Create Incident with Template activity to the active runbook. Double-click the Create Incident with Template activity icon.

  2. On the Details tab, in the Properties section, click the ellipsis button (...), and then select the Connection to the Service Manager computer that you want to use for this activity.

  3. Click the ellipsis button (...), and then select the Class that you want to use to define this object. For a list of the available classes and their respective fields, see Service Manager Classes, Fields, and Filters.

  4. Click the ellipsis button (...), and then select the Template that you want to use to define this object. The required fields for this template appear in the Fields section.

  5. To use additional fields to define this object, click Select Optional Fields. In the Add/Remove Property dialog box, select the properties you want to apply to this object from the Available list, and then click the right arrow button (>>). The properties appear in the Selected list. To remove a property from the Selected list, click the property, and then click the left arrow button (<<). Click OK.

  6. Assign a value to each of the selected fields. Or, to automatically populate the value for the additional fields from the data published by a previous activity in the workflow, right-click the field box, point to Subscribe, and then click Published data. Click the published data element you want to use, and then click OK. To view additional elements, select Show Common Published Data.

    The published data for each activity depends on the class that was selected when the activity was created. For a list of the data elements published by each class, see Service Manager Published Data. For information about the Common Published Data items, see Published Data in the System Center Orchestrator 2012 Runbook Guide.

  7. For information about the settings on the General and Run Behavior tabs, see Common Configuration Instructions for all Activities.

  8. Click Finish.

Other Activities

The Integration Pack for System Center Service Manager contains the following additional activities: