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
worddavc626ec154e3ae92e6abc137f939b7ba6.png
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.
worddav3de618b713fd7b8a44990e764348208d.png
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.
See 6.1.1

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.
worddav5f071a095045fd23688c6bf859c79a49.png
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.
worddav01e9c6af4e0c369364d598083545c457.png
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
Disabled

Order

Display Order (ASC)

The following actions can be performed in the "Shared Menu":

Name

Description

Add

Adding a new menu item.
see 6.2.1

Modify

Modifying an existing menu item.
see 6.2.2

Remove

Deletes the selected menu item.


Adding a Menu Item

With this dialog, a new E-Bonding Runbook menu entry can be configured.


worddav98a3d31aae583570891a13be108c2f16.png
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.
worddavb131a6b6c69253b8b69751db65aa49e0.png
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).
worddavccf3f6cb1b2521021a790bf89dd5c28b.png
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
Outbound

Message Name

E-Bonding Runbook Message Name = E-Bonding Runbook Interface Operation

Status

Enabled
Disabled

Order

Display Order (ASC)

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

VIPCON E-Bonding Run Book for BMC Atrium Orchestrator version 2.0