The following table lists the entities that share a relationship with the Runbook entity and the key property in each entity used to define the relationship.
The following code retrieves a runbook that has a particular GUID using C#. It outputs to the console the name and ID of the runbook and whether it uses a monitor activity. This example uses a service reference named SCOService and uses the credentials of the current user context. You can uncomment the line that specifies alternate credentials if the current user does not have appropriate permissions to the runbook being started. For more information see and .
Operational runbooks may be tied to IT Infrastructure Library (ITIL) incidents to allow repeatable processes supporting specific aspects of the . The runbook is typically divided into routine automated processes and routine manual processes. The runbook catalog begins with an index of processes covered and may be broken down in outline form (e.g. 1, 1.1, 1.1.1) to align the processes to the major elements they support in the service catalog.