Skip to main content
Skip table of contents

OBM events to ServiceNow incidents

Use Case

Requirements

#

OBM

ServiceNow

Connected Systems

Authentication (supported methods)

  • Connected Server:

    • Username and Password

  • Username and Password

Permissions

  • Connected Server:

    • Type → External Event Processing

    • Synchronize and Transfer Control → Enabled

  • Event Forwarding Rules (optional):

    • Target Servers: Forwarding Type → Synchronize and Transfer Control

  • incident (READ, WRITE, CREATE)

  • sys_db_object (READ)

  • sys_dictionary (READ)

  • sys_journal_field (READ)

  • sys_glide_object (READ)

Environment

  • Connected Server

  • Event Forwarding Rule (optional)

  • Integration User:

    • Timezone → “GMT”

    • Date Format → “yyyy-MM-dd”

    • User ID → Same as the “Username”

Network Requirements

Setup

  1. Log in to your ZigiOps instance.

  2. Go to ZigiOps → Configurator and load the integration template.

  3. Select the desired Integrated Systems and Integrated Systems and click the Save button to continue.

  4. Enable the integration from the Slider button located in the middle section of the screen.

How does the OpsBridge ServiceNow Integration work?

  1. When there is a new event in OBM, ZigiOps will automatically collect it, and transfer it to ServiceNow as a new incident. All necessary fields will be transformed and also moved to ServiceNow (based on the defined mapping in ZigiOps).

  2. Once there are updates or annotations on the OBM event, ZigiOps will get them and change the corresponding ServiceNow incident with the necessary fields (including comments, attachments, and more).

  3. When the ServiceNow incident is closed or updated, ZigiOps will close or update the corresponding event in OpsBridge with the applicable information.

Visit our website for more information, about our OpsBridge ServiceNow integration.

Specifics

No specifics are available for this integration.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.