Skip to main content

Workflow Editor — Daisy Chaining

Overview

Daisy Chaining within in the Workflow Editor is a useful function for connecting multiple transitions/transactions together. This is meaningful particularly when the form needs to have multiple things occur both automatically and sequentially, without requiring additional clicks for the end user.

This article will be divided into two parts:

  1. How to configure Daisy Chaining in environment versions 5.4 and after

  2. How to configure Daisy Chaining in environment versions 5.2 and before

Other Key Information

Daisy Chaining can be configured for both transitions and transactions. Transactions can be daisy chained to other transactions, as well as transitions. Similarly, transitions can be daisy chained to other transitions, as well as transactions.

The create transition is not available to be daisy chained, meaning, all transactions/transitions are available for chaining, once the form has been created.

Daisy Chaining Configuration — 5.4+

Suppose, for an example scenario, the following workflow configuration exists with 2 transactions (T1, T2). The goal is to daisy chain T2 to T1, such that after T1 runs, T2 will run without having the user interact with a button to launch T2.

The first step to accomplishing the proper daisy chain, is to select T1 from the transaction panel on the left side of the screen. Once T1 is selected, the workflow editor panel will become visible on the right side of the screen. Notice how there is a space to configure something called transaction flow - this is where all daisy chaining will be configured.

At this point, all that is needed is to select the Next Transaction dropdown and select the desired transition/transaction to be chained. In this scenario, it is T2.

Daisy Chaining Configuration — 5.2-

Suppose, for an example scenario, the following workflow configuration exists with 2 transactions (T1, T2). The goal is to daisy chain T2 to T1, such that after T1 runs, T2 will run without having the user interact with a button to launch T2.

The first step to configuring the daisy chain, is to navigate to the advanced editor for the workflow. Select the <> button on the top right of the screen.

Once inside the Advanced Editor, click somewhere within the actual code. The location (line of code) that is clicked does not matter, however, the next step will not function properly if the code is not selected. It will become clear that the cursor is in the right place when the cursor is flashing, and the line of code has a light grey bar directly above and below it.

Once a line of code the advanced editor has been selected (the example above has the cursor placed in line 6), select CTRL+F using your device's keyboard. This will open the Find/Replace Menu.

In the search box, type the name of the first transition. This transition is the first in the sequence. In this scenario, this is T1.

Now that T1 has been located, locate the following lines of code:

  1. "name": {transaction/transition name}

  2. "fields": [

In this example, those are lines 50 and 51.

Once those two lines of code have been located, place the cursor at the end of line 50 (or whichever the top line is) and hit the enter key to start a new line of code.

In the new empty line, type the following code with the desired secondary transaction name:

"next-transaction": "{daisy chained transaction name}",

which will look like line 51 below:

Once this line of code has been added, the Save disc will become selectable. Make sure to select this, otherwise, the changes will not be saved.

Visualizing an Example

The following video will be used to demonstrate what a very simple daisy chain looks like in action. Additional configurations will likely need to happen to meet the requirements of other use cases. These may include, but are not limited to:

  1. Dialog Box design/configuration

  2. Enablement conditions for transition/transaction

  3. Visibility conditions for transition/transaction

  4. Form Updates