UiPath.SystemCenter.Activities package offers activities for integrating with Microsoft System Center Orchestrator.
This set of activities empowers UiPath’s users to include and interact with System Center Orchestrator automations in UiPath workflows. The package offers activities for Runbook Servers, Runbooks, Jobs and Events.
System Center Orchestrator Scope - Connects to System Center Orchestrator and provides a scope for other Orchestrator activities.
Get Runbook Servers - Gets all runbook servers collection.
Get Runbook By Id - Get details about a runbook based on its unique identifier.
Get Runbook By Path - Get details about a runbook based on its full path.
For Each Runbook - Performs an activity or a series of activities on each runbook matching the filter criteria.
Get Runbook Instances - Gets the instances of a runbook matching the filter criteria.
Start Runbook - Starts a runbook.
Stop Runbook - Stops a runbook.
Get Job - Gets details about a runbook job.
For Each Job - Performs an activity or a series of activities on each runbook job matching the filter criteria.
Stop Job - Stops a runbook job.
For Each Event - Performs an activity or a series of activities on each event matching the filter criteria.
UiPath.SystemCenter.Activities package is available in the Official feed, as a prerelease. In the Official feed, check ‘Include Prerelease’, search for “UiPath.SystemCenter.Activities”, and install the latest version.
** Important - We must reiterate, make sure you check the ‘Include Prerelease’ checkbox
System Center Orchestrator activities should be visible now in UiPath Studio, as shown below:
The following UiPath process demonstrates how to use System Center Orchestrator activities in practice. It consists of two workflows:
RunRunbook : Runs
Get Disk Sizerunbook and displays the values of the output parameters.
- GetFailedRunbooksReport : Generates a report with all failed runbooks since a specified date.
UiPath Studio sample project:
SCOrchestrator_Sample.zip (24.6 KB)
RunRunbook workflow in action:
GetFailedRunbooksReport workflow in action:
To exemplify, let’s go step by step through the process of creating RunRunbook workflow:
Let’s start by adding a System Center Orchestrator Scope activity, in order to connect to System Center Orchestrator and provide a scope for other Orchestrator activities. The values for the activity parameters should be similar with these:
- Orchestrator : “http://orch1.devs1.local:81/Orchestrator2012/Orchestrator.svc”
- Username : “email@example.com” or “devs1.local\test.user” (the format shall be user@Domain or Domain\user, where Domain shall be provided as FQDN).
Let’s add a Get Runbook By Path activity to get the details about the runbook (ID, name, parameters, etc.). The value of RunbookPath parameter is “\Ovidiu\Demo\Get Disk Size”.
This is how
Get Disk Sizerunbook looks in Runbook Designer:
Let’s prepare the value for RunbookParameterValues parameter of Start Runbook activity. For this, add a Build Data Table activity and define two columns of type String, the first one representing the parameter’s ID and the second its value. The Start Runbook activity returns the job that runs the runbook. Store the output in
jobForRnbkGetDiskSizevariable (this is needed later to retrieve the result of the runbook execution).
To wait for the runbook job execution to complete, add a Delay activity and wait for 5 seconds, which is enough for the runbook job to complete (I want to keep things simple here). Get Job activity is used to return the current state of the runbook job.
Finally, add a Get Runbook Instance activity to get access to the output parameters of
Get Disk Sizerunbook execution. I do not need all runbook instances of
Get Disk Sizerunbook, just the one associated with the
jobForRnbkGetDiskSizejob from above. To get only this specific runbook instance, set the value of the optional parameter JobId to
jobForRnbkGetDiskSize.Id. As result, RunbookInstances collection will contain only one item. That’s all folks! Enjoy