- 12 Mar 2021
- 1 Minute to read
- Print
- DarkLight
Using the "Wait on External System" Step
- Updated on 12 Mar 2021
- 1 Minute to read
- Print
- DarkLight
Overview
Example Lab Details | |
Version | 6.9.2 |
Root Folder | Example Lab - WOES Example |
Modules | None |
Dependencies | None |
This Example Lab project demonstrates one of the features of the Wait On External System step in the Flow Designer.
Explanation
In this Example Lab project, the 'Wait On External System' step functions to wait for a new user account that is added to the local Decisions instance. For this Flow to work, the 'Wait On External System' step must check for a change to the user accounts every 10 seconds. The Flow cannot complete until a new account has been added to the local environment (this can be created with a mock email for testing purposes). To see the Flow work, set up two internet tabs that are logged in to a local install of Decisions.
In the first tab, find the WOES Example Flow from this project and edit the Flow, then start the debugger. As shown, the Flow pauses at the 'Wait On External System' step every 10 seconds to check for account changes. In the second tab, navigate to System > Security > Accounts and select Create Account. Once the account has been created, return to the first tab where the Flow will now complete in no longer than the 10-second interval. The time interval can be configured from the properties of the 'Waiting On External System' step.