Runbooks

From Hornbill
Jump to navigation Jump to search
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; for further details, refer to Business Process Designer documentation.

Related Articles

Runbooks List

RunbookListFade.png
  • 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

ITOMRunbooksListToolbar.png

  • Filter
Free Text Filter on Runbook, Category & Created By
  • Dropdown Filter
Active State filter
  • Mannage Executed Processes
Displays all executed processes, provides trouble shooting and process control features
  • Create New NewPackageButton.png
Creates a new Runbook process
  • Delete ITOMGenericDustbin.png
Delete selected runbbook(s)

Runbook Business Process

RunbookProcessDesignerFade.png

One major difference with the BPM, as used within Applications such as Service Manager, is that output parameters can be defined. Applications that use the BPM can utilise the Output Parameters in the same manner as that of provided by Cloud Automation results.

Process Nodes

  • Hornbill Automation
Invoke Hornbill Actions
  • Cloud Automation
Interact with third parties
  • IT Automation
Invoke ITOM Packages or other Runbooks
  • Decision
Conditional execution based on one or more expressions
  • End Process
  • Abort
  • Start Parallel Processing
  • Finish Parallel Processing

Runbook Process Settings

RunbookProcessSettingsFade.png
  • 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
Information
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