Skip to Content

Data flow from BMC Helix iPaaS to BMC Helix Multi-Cloud Broker

The following image provides an overview of the backend data flow from BMC Helix iPaaS to BMC Helix Multi-Cloud Broker:

ipaas-mcb.png

Related topic

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

When the integration template operation receives the third-party application ticket data:

  1. The transformation defined in the operation transforms the data to a format compatible with the BMC Helix Ticket Brokering Library record. 
  2. Internally, BMC Helix iPaaS checks if the VendorData record exists for the BMC Helix ITSM ticket and performs one of the following actions: 
    • If the record exists, BMC Helix iPaaS updates the VendorData record with the values from the third-party application.
    • If the record does not exist, BMC Helix iPaaS creates a new Ticket Brokering Library record if the template supports two-way integration between BMC Helix ITSMand the third-party application.

 

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

BMC Helix Multi-Cloud Broker 26.1