Running a Flow using an Alias

Last Updated: 06/07/2018 Introduced in Version:

It is possible to run a flow, either as a service or by showing forms and Decisions user interface in a web browser, just by accessing its URL. This URL can be used to allow execution of the workflow from a browser or as a service.  The URL can be lengthy, and one way to make it more user-friendly is to create an alias.

An alias is a short, user defined name for a flow that can replace a FlowID. The FlowID is the unique ID generated by the system to identify the flow. Typically, to run a flow using a URL, you include this FlowID, however it is possible to make this easier by replacing the FlowID with our user defined alias.
For instructions on how to run a flow from the URL, please see the following document:
To create an alias for a flow, select the flow’s thumbnail  and select Edit > Create Alias from its Action menu. Flows with aliases can be run with the URL,[YourFlowAlias.]
When you access a flow via its URL (alias or not), the Portal will prompt for a login unless the flow is running under the Guest account. However, the full Portal will not load; only the flow itself.


We begin our example with the assumption that you have created flow that you would like to run in a browser window. For more information on creating your first flow, please click here. Our example alias will make it possible to operate this flow through a more convenient URL than the system default

To create an alias, select the flow, then select Edit > Advanced > Create URL Alias from its Action menu.
Enter the any name that you would like to use as an Alias. In our example, we will use “Insurance_Request” (without spaces) and click Save.

Once the Alias is created, view the Integration Details for your Flow by right clicking the flow and navigating to Run[Advanced] > Integration > View Integration Details.


In the new dialog that gets created. When setting up the paramaters of the URL, you will now see “Alias” as an option. Select this and your URL will get generated with the Alias instead of the FlowID. You have now successfully used an Alias in your URL that calls a flow.


Additional Resources