Decision Table Flow Designer Help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2024 03:30 AM - edited 09-17-2024 03:31 AM
Hello,
I've recently been watching and learning decision tables to find a way to reduce repetitive actions within flows. Our use-case is to use them to remove the need for multiple if statements which we used for task, ritm and request closure logic, e.g.:
So if 1 request has 1 ritm and 1 task, the closure state of the task will determine what the state, stage etc. of the associated ritm and request will be changed to.
I've made a decision table, but when a task is closed it doesn't seem to touch the related RITM and REQ records, below is the way I've currently set it up: (Each of the RITM and REQ are references to these fields).
If I understand decision tables correctly, it should check the conditions and modify the required fields based on what the condition is, in this case if it is complete, incomplete or skipped, the adjacent results will occur.
The flow it has been added to:
I have also attached the export of the decision table, hopefully someone can assist or show me what I am missing.
Thanks!