Sending and receiving data between Remedy AR System forms and third-party applications

You can use AR System connector to send data to or from any out-of-the-box or custom form that you create in the Remedy AR System. Depending upon the AR server version, AR System connector uses the Webhook or REST API for triggering the connector actions. This AR System connector has the following configuration.

"configuration": {
   "name": "Configuration",
   "description": "Configuration",
   "parameters": [
       {
           "type": "url",
           "required": true,
           "name": "AR Server URL",
           "description": "AR Server URL",
           "systemName": "url"
       },
       {
           "type": "textarea",
           "required": false,
           "name": "AR Form List",
           "systemName": "arFormList",
           "description": "AR Form List to support customer forms"
       },
    ]
}

For example, a user logs into Remedy AR System and creates a custom form or selects any out-of-the-box form. The user updates the AR System connector configuration in the BMC Helix Integration Service and creates a flow between the AR System connector and the vendor connector by defining the trigger conditions and selecting from the list of available actions. The user can now send the Remedy AR form data to the vendor application.

To send data from your application to Remedy AR System form

To send data to or from an existing AR form or any custom form that you create in Remedy AR System, update the AR System connector configuration and then create and execute flows from the connector. The following example illustrates how to send incident form data from BMC Helix Multi-Cloud Service Management to Remedy AR System by using the AR System connector.

Log in to BMC Helix Integration Service and search for the AR System connector.
In the connector configuration UI, enter the values for AR Server URL and AR Form List.
AR Form List for incident, incident worklog, and task forms.
[
    {
"label": "Incident",
"name": "HPD:Help Desk",
"trigger": "HPD:Help Desk",
"create": "HPD:IncidentInterface_Create",
        "update": "HPD:IncidentInterface",
"query":"HPD:Help Desk",
        "resultKeyField": "1000000161",
        "keyField":"1000000161"
    },
{
        "label": "Incident WorkLog",
        "name": "HPD:WorkLog",
"trigger": "HPD:WorkLog",
        "create": "HPD:WorkLog"
    },
    {
        "label":"Task",
        "name":"TMS:Task",
"create":"TMS:Task",
        "update": "TMS:Task"
    }
]
To regenerate the schema for the connector, click Custom Fields > Regenerate.
To create a new flow, click My Flows > +Flow Designer.
On the Choose Source tab, select the source for the flow.
In this example, Multi-Cloud connector is selected.
To execute connector action, select the trigger conditions. In the example, the flow is triggered whenever the summary of an existing incident record is updated with the string Sun.
Click Next and on the Choose Target tab, select the AR System connector.
All the available actions defined in the AR Form list are displayed.
To map fields between your vendor application and the AR Form fields in the Map Fields, set the field mappings.
To add multiple actions to the flow, click Add Action and choose target and actions. In the following example, the Instance id and Incident number from the Create a new incident action is mapped with the subsequent Create a new task action.
To create the new incident with the associated task as configured in the example, run the flow.
Incident form data is sent to Remedy AR and a new incident is created in Remedy ITSM.

Sending and receiving data between Remedy AR System forms and third-party applications

To send data from your application to Remedy AR System form

On this page