Decision

This is used to set conditions and create branches as per the requirements. The decision node is used to select the flow path based on the criteria.

Decision node can be added and defined using a JavaScript expression.

Multiple Branches

In this example, View tickets can follow any one of three options: Ticket ID, TicketTitle, Most Recent Tickets.

${flagList.key.equalsIgnoreCase("Ticket ID")} means if the user input value is“Ticket ID”, then continue with the Ticket ID branch.

Click the “+” sign under the decision node to add two more branches for “TicketTitle” and “Most Recent Tickets”.

As more nodes have been added to the flow, the minus button “-” on the decisionbranch can be used to collapse the branches. On the other hand, the plus button“+” and “expand” menu can also be used to expand the nodes of the branch.

User Input + Decision

This example denotes when the user has any issue with files and selects MS teams as application from user inputs option provided by the flow. A decision node under each application type (example below uses MS Teams) branch to determine the issues of the application (again in this case with respect to MS Teams).

Please note that to determine the issue type, here two branches are used for each decision node to represent the - ‘Sending a file in meetings and webinars' and‘ Sending a screen capture file and photo’.

The following sample javascript expression for a branch denotes that if the user input value is “Sending a file in meetings and webinars”, then continue with that particular branch with the following command - ${zoomSelection.key.equalsIgnoreCase ("Sending a file in meetings andwebinars")}