Integrating with another application by using a connector

In BMC Helix Innovation Studio, you can use connectors to integrate the application with a third-party system or application. To use connectors, you must add connector configurations, add connector elements in Process or Rule designer, and create alias mapping of the connectors.

Connectors

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

For more information about connectors, see Connectors-overview.

Connector actions

A connector action is an activity triggered to connect BMC Helix Innovation Studio 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 Innovation Studio.
For more information about creating aliases, see Mapping-an-alias-to-connector-configuration.
Provide a literal map of actual values to create mapping of connector actions.

While using aliases, you can change the name of the connector action as per your requirement and usability. However, in literal, you cannot change the name of the connector configuration.
Alias mapping is preferred and recommended for setting up and using connector actions.

Connector development process

BMC Helix Innovation Studio provides out-of-the box connectors to integrate your applications with third-party products. You can use these connectors in your application processes and rules. In the Process designer and Rule designer, these connectors are available as a Connector property of the Connector element.

The following image provides an overview of the connector development process. It describes the roles involved, steps required, and the tools used in connector development and connector utilization:

22_1_Connector development process.png

Role	Action	Reference
Developer	Sets up the connector development environment	Deploying-your-application-for-the-first-time-to-start-working-in-BMC-Helix-Innovation-Studio
Developer	Develops and tests the connector	Developing connectors
Developer	Deploys the connector	Configuring connectors
Administrator	Creates connector configurations	Adding or updating a configuration
Administrator	Creates connector profiles	Adding-connector-configurations
Administrator	Performs alias mapping of connector actions with connector configurations	Mapping-an-alias-to-connector-configuration
Application Business Analyst	Creates a process or rule to integrate a Digital Service application with an external resource	Automating-categorization-and-assignment-of-application-requests
Application Business Analyst	Tailors the Digital Service application	Tailoring-applications-and-automating-processes
End user	Uses Digital Service application that leverages connector	NA

Example of extending BMC Helix Virtual Agent by using connectors

The following video (9:17) demonstrates how to alter the conversation flow in BMC Helix Virtual Agentby using data from an external application such as JIRA. The video shows an older version of the 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

Action	Reference
Create new connector configurations and provide details of the connector configurations such as Name, Type, Configuration.	Adding-connector-configurations
Use the Connector element in Process designer to integrate the application with a third-party application.	Integrating-applications-by-using-process-connector-elements
Use the Connector element in Rule designer to integrate the application with a third-party system.	Integrating-applications-by-using-rule-connector-elements
Perform mapping of aliases with connector configurations for connector actions.	Mapping-an-alias-to-connector-configuration
Perform troubleshooting of connectors.	Troubleshooting-integration-service-connection-issues