Difference between revisions of "Runbooks"
Line 9: | Line 9: | ||
These actions are conditional based on information passed to the Runbook and logic controlled by the Runbook's business process. | These actions are conditional based on information passed to the Runbook and logic controlled by the Runbook's business process. | ||
− | Runbooks utilises Hornbill's Powerful Business Process Workflow tool to enable processes to be defined within a Runbook. | + | Runbooks utilises Hornbill's Powerful Business Process Workflow tool to enable processes to be defined within a Runbook. Only features specific to Runbooks will be discussed, further details regarding the Business Process are available in the section [[Business Process Designer]] |
| | | | ||
* [[ITOM Package Library]] | * [[ITOM Package Library]] |
Revision as of 12:32, 15 July 2020
Home > Administration > ITOM > Runbooks | Index |
IntroductionOrchestration 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:
These actions are conditional based on information passed to the Runbook and logic controlled by the Runbook's business process. Runbooks utilises Hornbill's Powerful Business Process Workflow tool to enable processes to be defined within a Runbook. Only features specific to Runbooks will be discussed, further details regarding the Business Process are available in the section Business Process Designer |
|
Runbooks List
- Runbook
- Category
- Created By
- Created On
- Updated By
- Published version
- Active State
- Action Buttons
- Publish
- Copy
- Rename
- Delete
- Invoke
Toolbar
- Filter
- Free Text Filter on Process
- Create New
- Create a new runbook
- Delete
- Delete all selected runbbook(s)
Runbook Business Process
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
- 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