Skip to Content

Global Connections

Introduction

The Global Connections page is where you manage connections that can be used across projects in an environment. Each environment can be set up with a unique configuration of the global connection that can be used by any project in that environment.

From the Global Connections page, you can view, create, edit, and delete global connections depending on the environment access levels granted to your role. Once a global connection is added to an environment, it becomes visible to users in the design component palette to use in a project.

Tip

When your project lifecycle involves project migration, using global connections is recommended over using project variables in non-global connection configuration fields. Though project variable values can be selectively excluded during migration, this process can be cumbersome with a large number of variables.

Access the Global Connections Page

The Global Connections page can be accessed from either the Harmony Portal menu or the design component palette:

  • Use the Harmony Portal menu to select Cloud Studio > Global Connections:

    cloud studio global connections

  • In the design component palette Global Connections tab, click Manage Global Connections:

    global connections available email

Global Connections Table

Existing global connections are displayed in the Global Connections table within the Connections tab:

These controls are located along the top right of the table:

  • Search Connections: Click the search icon to expand a search box. Enter any part of the global connection name, type, or description into the search box to filter the connections.

  • Add New Connection: Click the add icon to open the global connection configuration screen for a new connection.

  • Refresh: Click the refresh icon to reload the table.

The table includes these columns:

  • Name: The name of the global connection provided in the configuration.

  • Type: The connector that the global connection uses.

  • Description: The description provided in the global connection configuration.

  • Environments: The environments that the global connection is added to, as configured in the configuration.

    When the configuration of a global connection that is used by a deployed operation is edited and any operation using the edited global connection in that environment has not yet been redeployed, a blue Undeployed icon is displayed along the top of the environment pill:

    In addition, each environment can be clicked to bring up an environment drawer from the bottom of the page that provides additional information and actions you can take such as deploying changes, opening the project or operation in Cloud Studio, or removing the connection.

  • Created: The local browser date and time that the global connection was created, and the username of the user who created it.

  • Modified: The local browser date and time that the global connection was last modified, and the username of the user who last modified it.

  • Actions: Hover over the global connection row to show actions available for the connection:

    • Edit Connection: Click the edit icon to open the global connection configuration screen for an existing connection.

    • Delete Connection: Click the delete icon to delete a global connection that is not used in any projects. For additional information see Delete a Global Connection later on this page.

Environment Drawer

The environment drawer opens from the bottom of the page when you click an environment in the Global Connections table:

Tabs along the top of the drawer are displayed for each environment where the global connection has been added.

A circular blue Undeployed icon undeployed is displayed in an environment tab when the global connection that project operations are dependent on has had a configuration change since the global connection was last deployed in this project. This means you need to redeploy operations dependent on the connection in this project to use the connection's latest configuration.

Important

The circular blue Undeployed icon undeployed and the triangular blue Undeployed Changes icon undeployed have distinct meanings. While the circular blue Undeployed icon undeployed indicates that operations dependent on the global connection must be redeployed in the project, the triangular blue Undeployed Changes icon undeployed alerts you to which of those operations have other configuration changes (such as an unrelated activity or script operation step) that have not yet been deployed and will also be deployed when you click the Deploy for This Project button.

You can cycle through the tabs using the left and right arrows left arrow right arrow.

These controls are located along the top right of the drawer:

  • Collapse: Click the Collapse icon collapse to collapse the environment drawer to the bottom of the page so that only the top of the drawer is visible. To restore the drawer to its previous state, click the Return icon return.

  • Expand: Click the Expand icon expand to expand the environment drawer to the top of the page. To restore the drawer to its previous state, click the Return icon return.

  • Close: Click the Close icon close to close the environment drawer.

Each tab includes this information and these actions:

  • Name: The icon and name of the global connection.

  • Description: The description of the global connection.

  • Components in the Environment: A table is displayed for each project in the listed environment that has components that are dependent on the global connection:

    • Project: The name of the project. The presence of an Undeployed Changes icon undeployed next to the project name indicates that the project contains operations dependent on the global connection that have had other configuration changes (such as an unrelated activity or script operation step) that have not yet been deployed and will also be deployed when you click the Deploy for This Project button.

    • Project Last Modified Date: The date and time that the project was last modified. The date and time are local to the project and are not affected by modifications to any global connections in use by the project.

    • Deploy for This Project: Click to deploy operations dependent on the global connection in this project only. After deploy, the next time this project's operations run, they will use the latest global connection configuration.

      Caution

      Any operations shown with an Undeployed Changes icon undeployed next to the operation name have other configuration changes (such as an unrelated activity or script operation step) that have not yet been deployed and will also be deployed when you click this button.

    • Go to Project: Click the link icon link to open the project in Cloud Studio in a new tab.

    • Hide or Show Project: Click the up or down arrows up arrow down arrow to hide or show the list of operations that are dependent on the global connection for the project.

    • Operation: The name of any operations dependent on the global connection. The presence of an Undeployed Changes icon undeployed next to the operation name indicates that the operation has had other configuration changes (such as an unrelated activity or script operation step) that have not yet been deployed and will also be deployed when you click the Deploy for This Project button.

    • Components Not Used in Operations: The type and name of any components that exist outside of workflows and are dependent on the global connection. These components are listed for informational purposes only; while they do not affect any deployed logic, their existence in a project will prevent you from removing the connection in this environment.

    • Actions: Hover over and click the link icon link to open the project with the operation selected in Cloud Studio in a new tab. Actions are not applicable to components not used in operations.

  • Deploy for Projects Without Changes: Click to deploy operations dependent on the global connection for projects in this environment where the only changes to deploy are those to the global connection (excludes projects that have any operations with the Undeployed Changes icon undeployed). After deploy, the next time these projects' operations run, they will use the latest global connection configuration.

  • Deploy for All Projects: Click to deploy operations dependent on the global connection for all projects in this environment. After deploy, the next time these projects' operations run, they will use the latest global connection configuration.

    Caution

    Any operations shown with an Undeployed Changes icon undeployed next to the operation name have other configuration changes (such as an unrelated activity or script operation step) that have not yet been deployed and will also be deployed when you click this button.

  • Remove Connection: Click to remove the global connection from the environment. This button is enabled only after first deleting components that reference the connection from all projects listed on the tab.

Create a Global Connection

To create a new global connection, click the add icon along the top right of the Global Connections table. The New Global Connection configuration screen opens. This screen is described below.

An existing connection in a project can also be promoted to a global connection, which you can then edit once created. The Promote to Global Connection option is accessible from these locations:

The New Global Connection configuration screen has two configuration steps:

Step 1: Select a Connector

In this step, you select a connector from which to create a new global connection:

  • Search: Enter any part of the connector's display name into the search box to filter the connectors.

  • Connectors: Click to select a connector from which to create a new global connection. All connectors in the organization except for the API, SOAP, and Variable connectors are listed, including custom connectors. Connectors that can be used only in environments associated with a Private Agent Group are indicated with a red dot private agent only 3.

  • Back: The back icon is disabled, as it is not applicable to this step.

  • Next: Click the next icon to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finish button on the last step.

  • Cancel: Click to close the global connection configuration without creating a new connection.

  • Finish: This control is disabled, as it is not applicable to this step.

Step 2: Configure and Test the Connection, and Add or Remove Environments

In this step, you configure and test the global connection, and add or remove environments where the global connection can be used:

  • Name: Enter a name to use to identify the global connection. The name must be unique for each global connection of a particular connector and must not contain forward slashes / or colons :. This name is also used to identify the connector endpoint, which refers to both a specific connection and its activities.

  • Description: Enter a description of the global connection to be displayed in the Global Connections table.

  • Environment Endpoints: In this area, you add environments one at a time and configure and test the global connection in each environment. Within the configuration for each environment, you can also remove the connection from the environment.

    Tip

    Adding environments and configuring and testing connection information can be done at a later time, enabling one user to create connections and another user to create connections and add them to environments later.

    • Add an Environment: Click the add icon to open a menu of the organization's environments that the global connection is not already added to. If the connector selected in step 1 is available only on Private Agents, environments associated with a Cloud Agent Group are grayed out and cannot be selected. Select one environment at a time from the menu, using the add icon to add additional environments as required.

    • Environment Tab: As each environment is added, a tab is added to the Environments section containing the global connection configuration for that environment.

      • Configuration Fields: Configure each field for the specific connector as described in the documentation for the specific connector selected in step 1. Documentation for each connector is within the Connectors section.

      • Connection Test Status: The following icons are displayed on an environment's tab when certain conditions are met. The icons do not persist after the configuration screen is closed.

        • Untested Changes: When an environment has connection configuration changes that have not been tested, its tab displays an Untested Changes icon unsaved.
        • Unsuccessful Connection: When an environment's tested connection is unsuccessful, its tab displays an Error icon error.
        • Successful Connection: When an environment's tested connection is successful, its tab displays a Success icon success.
      • Remove Connection: Click to remove the global connection from the environment. (Deleting the global connection can be done from the Global Connections table.)

      • Test Connection: Click to test the global connection using the provided configuration.

  • Back: Click the back icon to temporarily store the configuration for this step and return to the previous step.

  • Next: The next icon is disabled, as it is not applicable to this step.

  • Test All Connections: Click to test all environment endpoints in the global connection. After clicking Test All Connections, a dialog displays a list of the environment endpoints in the global connection and their connection status, with either a Success icon success or an Error icon error.

  • Cancel: Click to close the global connection configuration without creating a new connection.

  • Finish: Click to save the configuration for all steps and close the global connection configuration.

Edit a Global Connection

To edit a global connection, hover over an existing global connection row in the Global Connections table and click the edit icon .

The configuration screen for an existing global connection opens:

  • Name: Enter a name to use to identify the global connection. The name must be unique for each global connection of a particular connector and must not contain forward slashes / or colons :. This name is also used to identify the connector endpoint, which refers to both a specific connection and its activities.

  • Description: Enter a description of the global connection to be displayed in the Global Connections table.

  • Environment Endpoints: In this area, you add environments one at a time and configure and test the global connection in each environment. Within the configuration for each environment, you can also remove the connection from the environment:

    • Add an Environment: Click the add icon to open a menu of the organization's environments that the global connection is not already added to. If the connector selected in step 1 is available only on Private Agents, environments associated with a Cloud Agent Group are grayed out and cannot be selected. Select one environment at a time from the menu, using the add icon to add additional environments as required.

    • Environment Tab: As each environment is added, a tab is added to the Environments section containing the global connection configuration for that environment.

      • Configuration Fields: Configure each field for the specific connector as described in the documentation for the specific connector selected in step 1. Documentation for each connector is within the Connectors section.

      • Connection Test Status: The following icons are displayed on an environment's tab when certain conditions are met. The icons do not persist after the configuration screen is closed.

        • Untested Changes: When an environment has connection configuration changes that have not been tested, its tab displays an Untested Changes icon unsaved.
        • Unsuccessful Connection: When an environment's tested connection is unsuccessful, its tab displays an Error icon error.
        • Successful Connection: When an environment's tested connection is successful, its tab displays a Success icon success.
      • Remove Connection: Click to remove the global connection from the environment. (Deleting the global connection can be done from the Global Connections table.)

      • Test Connection: Click to test the global connection using the provided configuration.

  • Test All Connections: Click to test all environment endpoints in the global connection. After clicking Test All Connections, a dialog displays a list of the environment endpoints in the global connection and their connection status, with either a Success icon success or an Error icon error.

  • Cancel: Click to close the global connection configuration without saving.

  • Save: Click to save the configuration and close the global connection configuration.

    Note

    When a global connection is edited that is used in a project currently open in the designer, a message is displayed in the designer to notify users that the connection has changed and must be redeployed for changes to take effect.

Delete a Global Connection

To delete a global connection, hover over an existing global connection row in the Global Connections table and click the delete icon to delete a global connection that is not used in any projects.

If a global connection is used in any projects, the delete icon is disabled and the global connection cannot be deleted. To see a list of projects using the global connection, click the environment pill as described above under Environments in the Global Connections table. Then open each project, remove the global connection, and redeploy project operations that no longer use the global connection.