Skip to Content

Data flow between BMC Helix iPaaS and the third-party application

The integration template workflows manage the flow of data between BMC Helix iPaaS and the third-party application. The workflow operations transform data to map BMC Helix Multi-Cloud Broker fields to the third-party application, and the converse. 

Related topic

List of BMC AR System filters, guides, and BMC Helix Innovation Suite processes used by the integration template

Data flow from BMC Helix iPaaS to the third-party application

The following image provides an overview of the backend data flow from BMC Helix iPaaS to the third-party application:

ipaas-tps.png


When the BMC Helix iPaaS integration template operation receives data from the BMC Helix Multi-Cloud Broker:

  1. The transformation defined in the operation transforms the data to a format compatible with the third-party application. 
    The field mappings defined in the transformation element of the operation define the mapping between the BMC Helix Multi-Cloud Broker fields and the third-party application fields.
    For more information about updating existing field mappings, see Field maps.
  2. The operation sends the transformed data to the third-party application, and a corresponding ticket is created in the third-party application, and a label is added to the ticket based on the ticket type; for example, INC for incident, CHG for change, and so on. 

Data flow from the third-party application to BMC Helix iPaaS

The following image provides an overview of the backend data flow from the third-party application to BMC Helix iPaaS when a brokered ticket is created or updated in the third-party application:

tps-ipaas.png

  • When a ticket is created in the third-party application, the integration process sends the ticket ID to the appropriate BMC Helix iPaaS integration template operation.
  • When a brokered ticket is updated in the third-party application:
    1. The webhook created in the third-party application is executed. 
    2. The webhook sends the updated data to the appropriate BMC Helix iPaaS integration template operation.
Warning

Important

When a record is brokered to the third-party application from BMC Helix ITSM, a label is added to the ticket based on the ticket type. If a label exists in the third-party application ticket, the update operation is executed, and the corresponding BMC Helix Multi-Cloud Broker record and BMC Helix ITSM ticket are updated.

If the label does not exist, the Create operation is executed and a new record is created in BMC Helix Multi-Cloud Broker and  BMC Helix ITSM.

 

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

BMC Helix Multi-Cloud Broker 25.3