Using Flow Data in Rules
- 11 Oct 2022
- 1 Minute to read
- Print
- DarkLight
Using Flow Data in Rules
- Updated on 11 Oct 2022
- 1 Minute to read
- Print
- DarkLight
Article Summary
Share feedback
Thanks for sharing 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 | 7.10.0 Revision 68532 |
| Root Folder | Example Lab - Using Flow Data in Rules |
| Modules | None |
| Dependencies | None |
This Example Lab Project demonstrates how to add Flow Data in a Rule. As of version 7.10, Statement Rules and Evaluation Rules in Rulesets now have constants for their ID, Folder, and Name inside Flow Data. This allows the Rule to identify and use this information as part of the Rule. For example, designing a Rule to use its folder path as part of its condition.
Explanation
This project uses a Statement Rule with two string inputs, FolderID, and Name. The Rule will check if these values match the RuleFolderID and CurrentRuleName inside Flow Data. If both values match, the Rule will return as true. If the values do not match, the Rule will evaluate as false. The Rule can be tested using the debugger.
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 7.10 or later using our Importing/Exporting article.
Was this article helpful?
