Decisions 9: Inefficient Rule Collection Filter
In Decisions 9, Rule Collection filters that converted from Decisions 8 are marked as an issue.
What is the recommended step to use instead?
What is the purpose of the "Declare" statement at the top? (see attached screenshot). Would this statement improve rule execution and improve the health score of the flow?
There is very little documentation on this step, would appreciate any help on how to replace and use a better method in the future.
Comments
-
Hey,
It's essentially used to integrate a formula designer within the rules. I’ve attached the relevant documentation below.
https://documentation.decisions.com/docs/formulas#:~:text=Within%20the%20Rule%20Designer
Could you please share us a screenshot where its marked as an issue?
Thanks,
Manisha
-
Using the Rule Collection Filter triggers "Health" item warning. The wording implies that there is a better way of filtering and that the rule collection is "old"/deprecated?
-
Hey,
In Decisions v9, the Rule Collection Filter step (especially when used inside a rule with a simple one-line condition) triggers a Health warning because it’s considered an older and less efficient approach.
🔄 Recommended alternative:
We suggest using the Filter List step directly in your flow. It allows you to filter collections. This is more performant
https://documentation.decisions.com/step-library/docs/filter-list-step
-
OK, I will stat using Filter List. Thank You
Howdy, Stranger!
Categories
- 4.3K All Categories
- 74 General
- 13 Training
- 206 Installation / Setup
- 1.1K Flows
- 110 Rules
- 268 Administration
- 212 Portal
- 496 General Q & A
- 709 Forms
- 344 Reports
- 3 Designer Extensions
- 48 Example Flows
- 57 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 184 Pages
- 5 Process Mining
- New Features
- 186 Datastructures
- 70 Repository
- 229 Integrations
- 28 Multi-Tenant
- 27 SDK
- 81 Modules
- 58 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 143 Lunch And Learn Questions