Skip to Content

BMC Remedy integration GUI components

The following table describes the TrueSight Network Automation GUI components that enable integration with the BMC Remedy Change Request System.

You can learn about the points of integration on the Network Automation GUI by reviewing the entries in this table.


 TrueSight Network Automation integration components


Change IDs and Task IDs

In Network Automation, each job is identified by the following fields:

  • Job ID
  • Change ID
  • Task ID

The Change ID and Task ID fields are displayed whether or not BMC Remedy ITSM integration is enabled. When the integration is not enabled, these fields are free-form. You can enter any strings in them to optionally implement a two-level system to track change requests.

When the BMC Remedy ITSM integration is enabled, the Change ID and Task ID fields take on a more specific capability:

  • Job ID: Uniquely identifies a job in the Network Automation system. This ID is assigned to the job by the Network Automation system, the user cannot change the value, and it exists for every job.
  • Change ID: Relates a job to a BMC Remedy change request. A value can be selected or entered. However, it must match a valid Remedy change request ID.
  • Task ID: Relates a job to a BMC Remedy task under the Change ID.
Warning

Note

When configuring system parameters, be sure you require Change ID to be selected for all actions that are subject to Remedy approval. See Managing-system-parameters.

Important: The user should never manually enter the Change ID or the Task ID.

  • BMC Remedy-initiated change: User adds job from Remedy Inbox entry. The Network Automation system fills in the Change ID and Task ID.
  • Operator-initiated change: User leaves Change ID and Task ID blank. The Change ID and Task ID are filled in by the Network Automation system after the Job is Saved and Submitted.

 

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

TrueSight Network Automation 23.2