Skip to Content

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

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

mcb-ipaas.png

Related topic

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

When the Ticket Brokering Library record is created, the BMC Helix Multi-Cloud Broker webhook performs the following actions: 

  1. The webhook checks if the Webhook Condition Parameter field value in the BMC Helix Ticket Brokering Library record matches the condition defined in the webhook.

    Warning

    Important

    The condition to send the Ticket Brokering Library record to the BMC Helix iPaaS integration template operation in the BMC Helix Multi-Cloud Broker webhook based on the value defined in the MCB_Vendor_Name project variable in the BMC Helix iPaaS integration template. 

  2. Depending on whether the condition defined matches the field value, the webhook performs one of the following actions:
    • If the condition defined in the webhook and the field value match, the webhook is executed.
      The BMC Helix Ticket Brokering Library record data is sent to the appropriate operation in the BMC Helix iPaaS integration template.
      For example, if the record was created for a new incident in BMC Helix ITSM, the record data is sent to the operation defined to create an incident in the third-party application.
    • If the condition defined in the webhook does not match, no action is taken.
Warning

Important

Out of the box, the Webhook Condition Parameter value is defined based on the Resolution Category 2 field of the BMC Helix ITSM form.
For more information about changing the field for providing the Webhook Condition Parameter value, see Configuring-webhook-condition-parameters-for-integration-templates.

 

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

BMC Helix Multi-Cloud Broker 25.2