Use Case

  • Collect ServiceNow Applications and Creates new vROps Custom Groups

Requirements

This section provides information about the requirements, which should be met, In order for the integration template to function properly.

Integration Requirements


vROps RequirementsServiceNow Requirements
Authentication
  • Integration User
  • Integration User
Permissions
  • Administrator role
  • cmdb_ci_business_app (READ)
  • sys_glide_object (READ)

Network Requirements


Network Requirements
Communication
  • ZigiOps → vROps (80/443)
  • ZigiOps → ServiceNow (80/443)

Setup

To enable the integration, you should follow the steps below.

  1. You should start with the selection of the integrated systems and the integrated entities. The integrated entities should be pre-selected if there are no issues with the credentials/permissions, used in the connected systems configuration.

    Click here to expand...

  2. Press the Save button to save the changes.

    Click here to expand...

  3. You should enable the operations to start the integration.

    Click here to expand...

Operations Explanation

This section provides information about the predefined operations of this integration template, including the default field mapping configuration. Each operation consists of two tabs - Source, Field Map. The Source tab contains the trigger, trigger conditions and expressions configuration. The Field Map tab contains the mapping configuration. 

Create Custom Group

This operation polls the data via the ServiceNow Table API. It is designed to collect Applications from ServiceNow and create custom groups in vROps. The Application is collected from the ServiceNow, then it is internally processed through the field mapping configuration, and finally, a request is sent to vROps to Create a Custom Group.

Source

From this tab you could customize the polling interval, trigger conditions and expressions or use the defaults.

Click here to expand...

Field Map

From this tab you could customize the field, value, and conditional mappings, which suit your requirements.

Click here to expand...

Recommendations

This section provides information about the recommended considerations, which should be taken into account, before starting the integration.

Correlation

It is recommended to keep the default correlation configuration, unless you're familiar with the integration and the specifics of the integrated systems. You could contact our support team for assistance, prior further changes to the correlation configuration.

Mapping

The predefined templates are complied with the specifics of the integrated systems. It is recommended to confirm if your integrated systems have any required fields, which must be reported, so you could map them accordingly. Please note that if a required field is not mapped, the operation might fail. In this case, you could review the troubleshooting page for more information about the operation's execution history.