Generate link
Last updated
Last updated
Generate Link helps the user to construct a link which can be used to execute a workflow. This is supported for both User Workflows and Machine Workflows. Generate Link is located in the context menu in the server content panel.
User workflow links point to the web client and provide a direct link to a workflow execution.
Web Client Url this field should contain the url to the web client.
If the link is for the new web client, the URL will always be the same
If the link is for the legacy web client, the URL will differ per server
Server Url
If the link is for the legacy web client, leave this field empty
If the link is for the new web client, add the URL to the server
Execute Only locks the user to the execution view and prohibits the user from quitting the workflow or returning to a menu after execution.
Public User this option configures a public user to run the execution, when a public user is selected no credential prompt will be displayed.
Parameters this sections show the input variables that are configured in the start event of the workflow. Only simple variables can be used in user workflows.
Click Copy to copy the link for the legacy web client.
Click Copy (NG) to copy the link for the new web client.
User workflow links point to the mobile client and provides a direct link to a workflow execution.
Parameters these sections show the input variables that are configured in the start event of the workflow. Only simple variables can be used in user workflows.
Machine workflows can be executed over http request. These requests are made directly to the flow server. The workflow is executed by a machine user and authentication is made by basic authentication.
Method supported methods are POST and GET, POST supports complex structures as input and GET only supports simple variables fetched as query string values.
Server URL url to server, must be accessible from where the request is made.
Input in this section all simple variables are shown and provide a help function for constructing the input parameters. In POST requests the input should be sent as JSON in body content and GET should send input variables as part of the url.
The default execution timeout is 10 minutes for calls to the rpc/json2 endpoint. To increase this timeout, add the workflowTimeout query parameter with the timeout value in milliseconds, like: http://x.com/Novacura.Server/rpc/json2/pEjzkmFwq0Og?workflowTimeout=3600000 For long-running workflows, the above needs to be taken into consideration in addition to the executionTimeout in the server web.config file as well as timeout settings for any proxies in between the client and the Flow Server.
