E-Bonding Runbook Outbound Events
The Event Engine generates E-Bonding Runbook outbound events. The Event Engine is a set of BMC Remedy ARS workflow objects, which collect events within the BMC Remedy ITSM Suite module. The events are the source of every outbound interface communication.
A Remedy module, which supports the internal process logic of E-Bonding Runbook, completes the Event Engine. Every E-Bonding Runbook module includes separate outbound events. Events are processed based on defined E-Bonding Runbook rules, enriched with needed transaction data and sent to the E-Bonding Runbook Transaction Database.
For detailed description of the E-Bonding Runbook module events, please refer to the E-Bonding Runbook Message Library guides.
Event Engine Components
For the implementation of the Event Engine, additional workflow was created in the BMC Remedy ITSM Suite. The following filters and forms will be added to ITSM during installation of the E-Bonding Runbook Event Engine. The workflows do not change the ITSM processes at any time.
E-Bonding Runbook Incident – Event Engine Forms
Form Name |
|---|
VIP:BGI:IM:ProcessingTicketStore |
VIP:BGI:IM:ProcessingEvent |
VIP:BGI:IM:ProcessingEventHistory |
E-Bonding Runbook Incident – Event Engine Filters
Filter Name | Primary Form | Execute On |
|---|---|---|
VIP:BGI:EventTrigger_HPD:Help Desk | HPD:Help Desk | Submit, Modify |
VIP:BGI:EventTrigger_TMS:Task | TMS:Task | Submit, Modify |
VIP:BGI:EventTrigger_HPD:WorkLog | HPD:WorkLog | Submit |
VIP:BGI:EventTrigger_HPD:Associations_CI | HPD:Associations | Submit, Delete |
VIP:BGI:EventTrigger_HPD:Associations_Incident | HPD:Associations | Submit, Delete |
E-Bonding Runbook Change – Event Engine Forms
Form Name |
|---|
VIP:BGI:CM:ProcessingTicketStore |
VIP:BGI:CM:ProcessingEvent |
VIP:BGI:CM:ProcessingEventHistory |
E-Bonding Runbook Change – Event Engine Filters
Filter Name | Primary Form | Execute On |
|---|---|---|
VIP:BGI:EventTrigger_CHG:Infrastructure Change | CHG:Infrastructure Change | Modify |
VIP:BGI:EventTrigger_TMS:Task_CM | TMS:Task | Submit, Modify |
VIP:BGI:EventTrigger_CHG:WorkLog | CHG:WorkLog | Submit |
VIP:BGI:EventTrigger_CHG:Associations_CI | CHG:Associations | Submit, Delete |
VIP:BGI:EventTrigger_CHG:Associations_Change | CHG:Associations | Submit, Delete |
Principle of E-Bonding Runbook Events
E-Bonding Runbook Events are needed during outbound communication.
The application handles the processing of events in the following schematic sequence: 
Figure 5 E-Bonding Runbook Event Processing
To understand the Event Engine, two steps must be considered. These are described in the following chapters. From the time when the event has been delivered to the E-Bonding Runbook Core the Transaction Engine is responsible for a successful processing of the event.
Creation of E-Bonding Runbook Events
Events are generated by ITSM user input on one of these ITSM Incident or Change objects:
Incident Management
- Incident
- Incident Task
- Incident Work Info
- Incident Association (Relationships to Incidents or CIs)
Change Management
- Change
- Change Task
- Change Work Info
- Change Association (Relationships to Incidents or CIs)
Validation of E-Bonding Runbook Events
After an event has been generated the Event Engine validates:
- Whether it is necessary to send the object via and
- If yes, to which partner the event will be sent.
Here the following validations are done on base of the ITSM ticket data. Not before the validation is done the event is sent to the partner.
- Was the ticket (or subordinate object and/ or relation) created/ modified by a user or is it a technical CREATE/ MODIFY/ DELETE event? (see chapter 3.1)
- Has the ticket been assigned to a support group (assignee or owner) which corresponds to a E-Bonding Runbook partner? (see chapter 3.3)
- Is the E-Bonding Runbook partner enabled for the current event? (see chapter 3.5)
E-Bonding Runbook covers the complete ticket lifecycle and keeps the partner system synchronous to the data in ITSM as long as the ticket is worked on. For this, updates on tickets ((or subordinate objects and/ or relations) are sent even if the ticket is not any more assigned to a support group (assignee or owner) which corresponds to a E-Bonding Runbook partner. The memory for this is represented by the E-Bonding Runbook TicketStore (see chapter 3.4).