Getting Flow Inputs by ID
- 12 Mar 2021
- 1 Minute to read
- Print
- DarkLight
Getting Flow Inputs by ID
- Updated on 12 Mar 2021
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Example Lab Article
While Example Lab projects are resources for public use, articles and assets are not actively maintained. Screenshots and features are from the specified version below. These references may become dated as new versions are released.
Overview
Example Lab Details | |
| Version | 6.9.0 |
| Root Folder | Example Lab - Get Flow Inputs By ID |
| Modules | N/A |
| Dependencies | N/A |
This Example Lab project demonstrates how to use the Get Flow Inputs Step.
Explanation
This Example Lab Project has 2 Flows. One is "Monitor Flow" which takes a Flow ID (String) as input. This ID is passed to the Get Flow Input Step which can be found in the Step Toolbox under Integration > Internal Services > Flow Debug Service. The other Flow is "Input Flow" which is a flow with two inputs used as an example and Unit Test in "Monitor Flow."
Reference Articles
Project Download
The examples attached were developed to be instructional and were not developed as officially supported components. For more information or to engage our service team to develop fully supported, production quality solutions, please contact services@decisions.com. Import the project below to a Decisions environment on version 6.9.0 or later using our Importing/Exporting article.
Was this article helpful?
