Integrating with another application by using a connector

In BMC Helix Platform, you can use connectors to integrate the application with third-party system or application. To use connectors, you must add connector configurations, add connector element in Process or Rule designer, and create alias mapping of the connectors. The following section provides information about connectors and connector actions. 

Connectors

A connector is used to connect and configure BMC Helix Platform based applications with a third-party applications. 

For more information about connectors, see Connectors overview.

Connector actions

A connector action is an activity triggered to connect BMC Helix Platform with a third-party application, by using a connector. You can trigger the connector actions in two ways:

• Provide a unique alias to each connector action and map the application to BMC Helix Platform.  For more information about creating aliases, see Mapping an alias to connector configuration.
• Provide a literal to create mapping of connector actions. 
  

The only difference between using aliases and literal is that in literal, an administrator does not get the flexibility to change the name of connector configuration. While using aliases, you can change the name of the connector action as per requirement and usability.

Alias mapping is the preferred and recommended way of setting up and using connector actions.

Example of extending BMC Helix Chatbot by using connectors

The following video (9:17) demonstrates how to alter the conversation flow in BMC Helix Chatbot by using data from an external application such as JIRA. The video shows an older version of BMC Helix Platform. The previous product name was BMC Helix Innovation Suite. Although there might be minor changes in the UI, the overall functionality remains the same:

 https://youtu.be/qDxSOeS9I6w

Where to go from here