Runbooks

Home > Administration > ITOM > Runbooks

Index

Introduction Orchestration is fulfilled via the creation of a Runbook, enabling different operations to be bound together within a business process to perform a complete end to end solution. Allowing for the standardisation/automation of best practices that improve efficiency, reliability and reducing user error. As an example, the onboarding of a new user could require the following to be set-up / configured: AD User Account creation Mailbox Creation Forum / Wiki Access Software Installation Database Access rights The above actions are most likely conditional based on information passed to the Runbook and logic provided by Hornbill's Powerful Business Process Workflow tool. Only features specific to Runbooks will be discussed and any differences that there may be; for further details, refer to the Business Process Designer documentation. One of the main omissions is the use of Stages and Checkpoints as they are not required for use within a Runbook Process.

Related Articles ITOM Package Library Business Process Designer

Runbooks List

Runbook The name of the Runbook Category Runbook Category Created By The User that created the Runbook process Created On Runbook Process creation date Updated By The User that last updated the Rnbook process Published version Runbook published version number

Active State Identifies Active or De-Activated Runbooks Action Buttons Enables actions to be executed on the adjacent Runbook Publish Open the Publishing Manager Copy Createa a new copy of the Runbook Rename Rename the Runbook Delete Delete the Runbook Invoke Execute the Runbook

Toolbar

• Filter

Free Text Filter on Runbook, Category & Created By

• Dropdown Filter

Active State filter

• Search Button

Searches process for a Set Value

• Manage Executed Processes

Displays all executed processes, provides troubleshooting and process control features

• Create New

Creates a new Runbook process

• Delete

Delete selected Runbook(s)

Runbook Process

One major difference with the BPM, as used within Applications such as Service Manager, is that both input and output parameters can be defined. Runbook process can be called via applications BPM using a Runbook Process node where these Parameters can be used in the same manner as that used by existing nodes.

Process Nodes

The following nodes are available for use within the Runbook processes and function identically to how they would work within the BPM except for the parameter "Auto" and suspend features. It is recommended that all parameters are manually entered or populated using variables and not The "Auto" feature, which relies on the context being within the request process. Any nodes that may suspend a process will not be available for use within a Runbook as all process should be able to execute with no user interaction seamlessly.

• Hornbill Automation

Invoke Actions within a Hornbill Application or Core Feature

• Cloud Automation

Interact with third party systems via Hornbill iBridge automation

• IT Automation

Invoke an ITOM Package operation

• Decision

Conditional execution based on one or more expressions

• End Process

• Abort

• Start Parallel Processing

• Finish Parallel Processing

Currently the Hornbill Automation type "Suspend" is currently available, this will be deprecated from use with a Runbook in future releases and should therefore NOT be used.

Runbook Process Settings

• Input Parameters

Parameters which can be used throughout the process

• Output Parameters

Parameters which will be passed on to the calling process

• Category

Allowing for categorisation & searching

• Description

Allowing for searching

• Display Options

Normal/Projector - providing a more high contrast viewing alternative

• Access Granted To

Access can be granted based on Role, User or Group

IF the "Access Granted To" is set, then the ability to run this particular Runbook will be limited to only specific users and those users who are members of the configured Groups