In Orchestrator, when a runbook runs, each activity in the runbook publishes data that can be used by other activities.

For additional help, please refer to the on-line documentation for System Center 2012 - Orchestrator.

Data Types

Published Data Value Types

The following table shows the value types by which published data are categorized.

Type Description

String value

Text information. For example, an error message description.

Date value

Date and time information. For example, the date and time that a specific error occurred.

Number value

Numeric information. For example, the number of rows returned by a database query.

Boolean value

true or false. For example, command completed.

Published Data with Multi-Value Data

When an activity runs in a runbook, it can return any number of data items. Subsequent activities in a runbook are automatically provided and can subscribe to the activities’ published data and use it in their configuration. Link conditions also use published data to add filtering and decision-making capabilities to runbooks.

Each data item is passed to the activity that follows after going through link conditions filtering. When the next activity in the runbook runs, it runs one time for each item of data that the previous activity produced. For example, the Query Database activity runs and retrieves three rows from the database. These three rows of data make the next activity run three times, one time for each row returned. This next activity does not have to subscribe to the data for this action to occur.

An activity can also retrieve information from an outside source. “Get” activities and “Monitor” activities demonstrate this behavior. Data output from an activity might be a list of computers. Data can be passed on as multiple individual outputs, which invoke the next activity as many times as there are items in the output.

Note
You also have the option of passing on data as a single output.

For information about how to configure published data with multiple values, see Common Tabs.

Adding Published Data to Activity Configurations

Many activities can subscribe to published data. When an activity has subscribed to published data, a placeholder is inserted where the value of the data will be added. An activity can only subscribe to published data from an activity that is linked before it runs in the runbook.

Use the following procedures to add published data to an activity, to change the published data subscription, and to copy and paste published data items.

To add published data to an activity

  1. Right-click an activity from your runbook, select Properties from the menu, and then select the Details tab to open the activities properties dialog box.

  2. From a text box, right-click to open a menu, select Subscribe, and then select Published Data to open the Published Data dialog box.

  3. From the Activity drop-down list, select the activity that returns the data that you want to subscribe to. By default, the dialog box only displays published data that is specific to that activity. To include published data that is common to all activities, click Show common Published Data.

  4. Select the Published Data item that you want to use, and then click OK.

    A placeholder {published data item} will be inserted into the text box.

To change the published data subscription

  1. From the text box click the data placeholder to open the Published Data dialog box.

  2. From the Activity drop-down list, click the activity that returns the data that you want to subscribe to. By default, the dialog box only displays published data that is specific to that activity. To include published data that is common to all activities, click Show common Published Data.

  3. Click the Published Data item that you want to use, and then click OK. The published data placeholder changes to reflect the new activity and published data that you selected.

To copy and paste published data items

  1. Find a published data item that has already been inserted into a box in the Properties dialog box of an activity.

  2. Select the published data item that you want to copy.

  3. Use the keyboard shortcut CTRL+C, or right-click the selected item, and then click Copy.

  4. Open the Properties dialog box or document to which you want to copy the published data item.

  5. Place your cursor where you want the published data item to appear and use the keyboard shortcut, CTRL+V, or right-click the insertion point, and then click Paste. The published data item appears.

Transforming Published Data Items

With System Center 2012 - Orchestrator, you can transform the existing published data content or variable items into new content according to rules that you specify, by using the Map Published Data activity.

Common Published Data

Name Description

Loop: Delay between attempts

The amount of time (in seconds) between each loop attempt.

Loop: Enabled

The setting that determines whether per-activity looping is enabled for the activity.

Loop: Loop error message

The error message if the loop is not successful.

Loop: Number of attempts

The number of iterations that the loop has been through.

Loop: Total duration

The total amount of time (in seconds) that the looped activity ran.

Activity name

The name of the activity as it appears in the workspace. If you customize the name of an activity in the workspace, the customized name appears here.

Activity type

The default name of the activity. It does not change from the default even if you rename the activity in the workspace, and it can be useful in identifying an activity in runbooks where activity names and display icons have been changed.

Activity ID

The unique identifier of the activity. For example, {4BD3F27A-8F1B-4F60-8245-F69469075EF1}.

Activity Process ID

The process ID of the job process where the activity runs.

Activity status

The result status of running the activity, for example, Success.

Activity start time

The time when the activity started.

Activity end time

The time when the activity finished.

Activity end time(year)

The year when the activity finished.

Activity end time(month)

The month when the activity finished.

Activity end time(day)

The day when the activity finished.

Activity end time(weekday)

The day of the week when the activity finished.

Activity end time(hours)

The hour when the activity finished.

Activity end time(minutes)

The number of minutes past the hour when the activity finished.

Activity end time(seconds)

The number of seconds past the minute when the activity finished.

Activity duration

The total time that activity was running.

Runbook name

The name of the runbook to which that the activity belongs.

Runbook Process ID

The process ID of the runbook module’s executable program running on the runbook server.

The job process contains the logic for the activity. It is started when the runbook server starts the runbook, and it is stopped when the runbook is stopped. Each runbook runs in its own job process executable program.

Server name

The name of the runbook server where the runbook is running.

Error summary text

A summary of the error information published by the activity.