- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2025 03:29 PM
I am building a business rule that requires identifying the 'yet to be triggered' approvals and tasks for a given flow. From what I have researched I should see a 'definition' field in the 'sys_hub_flow' table but, it appears to be missing. Does anyone else know where to find these tasks and approvals defined in flow designer?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2025 02:52 PM
- Scalability
- Future investigation if a problem occurs (your logic is in separate places. Flow and BR)
- Any future enhancements need to take into account two pieces of tech debt
- The current BR won't take into account that a flow continuing isn't immediate. That BR could update the RITM state before the next flow step starts
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2025 04:17 PM
Building a business rule to be dependent on flow transactional data sounds risky.
What is the BR doing? There might be a better solution for this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2025 04:27 PM
i need to close the ritm depending on the different task states. However, I also need to make sure all approvals required by the flow, both executed and non executed, are accounted for?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2025 04:30 PM
Why is that not being handled by the flow?
A BR is only going to fire if the record is updated. Assuming this BR is on the ritm table, it would require either the flow or a user to make a modification.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2025 05:06 PM
originally I was using it in a flow but, it only worked if tasks were the last part of the flow. If approvals came after the flow it didn't work. So, I am trying to find a scalable solution I can use across all flows.
