Flow components

Flow components include constants that allow users to manipulate variables easily, endpoints to track where and how to communication with the apps in your toolchain, and script libraries that enable the sharing of code across all workflows.

Constants

Workflow designers use constants to help non-technical users manipulate variables. For example, you could use a constant to represent:

  • the time zone when posting date stamps to a customer's help desk;
  • the name of a third-party user account when making updates via an API; or,
  • the "From" name when sending messages to a chat client.

Constants are available to all flows, and are included when exporting and importing a flow.

By default, a maximum of 100 constants can be added to a workflow. You can see how many constants have been added and the total the number of constants allowed at the bottom of the Constants window.

Endpoints

Each application you want to integrate with is represented by an HTTP endpoint. An endpoint provides a simple way to define the base URL and authentication credentials to use when making HTTP requests from Flow Designer.

By configuring endpoints separately, you can quickly modify all references to an endpoint across a workflow rather than editing each instance of the target URL in each step.

Endpoint authentication

Integration endpoints can be defined to support basic and OAuth 2.0 authentication. Customized OAuth 2.0 endpoints are available for BMC Remedy, Microsoft Graph API, Salesforce, ServiceNow, and Slack.

Configuring an endpoint with the required configuration and credentials for OAuth 2.0 authentication simplifies HTTP requests to an API secured with OAuth 2.0. When using an OAuth 2.0 endpoint, you do not need to include reference to the access token URL, or any of the OAuth 2.0 fields associated with the endpoint.

When workflows are exported, all authorization content is cleared, and endpoints are set to "No Authentication".

Libraries

Libraries allow you to write common code functions once and use them in any workflow in your deployment.

For example, you can use a library to hold code that:

  • parses, manipulates and displays date and time information
  • trims leading and trailing white space
  • trims strings to a maximum length