E-Bonding Runbook Platform Configuration
Platform-wide changes can be made via the Platform Configuration form.
As a rule, customers should have to make any changes, as adjustments can lead to a malfunction of E-Bonding Runbook.
Access: The "BGI User" and the "BGI Admin" permissions are required for access
Access: ITSM Homepage > VIPCON E-Bonding Runbook > E-Bonding Runbook Platform Configuration 
Illustration 16 Access E-Bonding Runbook Platform Configuration
E-Bonding Runbook Interface User
In the "User Interface E-Bonding Runbook" ITSM users can be configured. This list of users is a type exclude list represents. If a ticket, task, or other ITSM objects are created, modified or deleted from one of these users, then no E-Bonding Runbook event is triggered and sent to partners. 
Illustration 17 E-Bonding Runbook Interface User
The table field shows the following columns:
Name | Description |
Login Name | The ARS Login name of the user who is to be ignored by the E-Bonding Runbook Event Engine. |
The following actions can be performed in the "User Interface":
Name | Description |
Add | Adding a user to the list of User Interface. |
Remove | Deleting a user from the list of User Interface. |
Interface Add User to List
With this dialog, an ARS user can be added to the list of User Interface.

Illustration 18 Add Interface User to List
The following actions can be performed:
Name | Description |
Add | Add User. |
Cancel | Cancels the action and closes the dialog box. |
E-Bonding Runbook Shared Menu
In this area but global dynamic E-Bonding Runbook menu entries can be maintained. These are as used in the search for log entries and other areas of application.
It is strongly recommended not existing Data menu, modify or delete and create new entries only in consultation with a specialist E-Bonding Runbook.

Illustration 19 E-Bonding Runbook Shared Menu
The table field shows the following columns:
Name | Description |
Schema Name | Form name is used on the menu. |
Field Name | Field name is used on the above specific form for the menu. |
Menu Value | Menu Value |
Status | Enabled |
Order | Display Order (ASC) |
The following actions can be performed in the "Shared Menu":
Name | Description |
Add | Adding a new menu item. |
Modify | Modifying an existing menu item. |
Remove | Deletes the selected menu item. |
Adding a Menu Item
With this dialog, a new E-Bonding Runbook menu entry can be configured. 
Illustration 20 Create a Menu Item
The following actions can be performed:
Name | Description |
Add | Add menu item. |
Cancel | Cancels the action and closes the dialog box. |
Changing a Menu Item
With this dialog, an existing E-Bonding Runbook menu entry can be changed.

Illustration 21 Change menu item
The following actions can be performed:
Name | Description |
Modify | Change menu item. |
Cancel | Cancels the action and closes the dialog box. |
E-Bonding Runbook Messages
In this section, the E-Bonding Runbook messages are listed that can be used per installed E-Bonding Runbook module (e.g. Incident Management or Change Management).

Illustration 22 E-Bonding Runbook Messages
The table field shows the following columns:
Name | Description |
E-Bonding Runbook Module | Name of the E-Bonding Runbook Module. |
Direction | Inbound |
Message Name | E-Bonding Runbook Message Name = E-Bonding Runbook Interface Operation |
Status | Enabled |
Order | Display Order (ASC) |