- 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-03-2025 04:43 AM
I would say you're potentially going in the wrong direction.
Whats the use case for approvals after a RITM is fulfilled? Are you able to explain the business process you're developing against?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2025 11:14 AM
so I have a series of approvals, follow by a single catalog task. However, as each RITM is in an open state fulfillers can create manual tasks. As such, I need to wait for both the flow task and all the manual tasks to be closed prior to closing the ritm. If any of the tasks are incomplete, the RITM needs a status of incomplete, otherwise it is complete.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2025 12:26 PM
So allowing users to create manual catalog tasks is a deviation from baseline, that's why you're running into this as a pain point.
In your flow, after you process-driven activities you could:
- Use a look up records to find active catalog tasks for the RITM
- Use a wait condition on the catalog tasks to wait until it's closed.
You can put that into a do...until step to re-lookup after the wait condition is fulfilled to recheck if a manual task was created since the last lookup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2025 12:48 PM
I worry about the max iterations for the do ... until and don't want to have a long increment greater than one minute. In using the lookup records and then having a wait condition in the for each loop, I am not sure how to bubble out the task states ... i.e. incomplete or complete.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2025 02:29 PM
Your do until doesn't need to be time based, because the "wait for condition" within the do...until will halt until the record it is watching is updated.
In terms of setting overall RITM state, you can do after this looping process by looking up all the catalog tasks where state is incomplete, and do a max results of 1. If 1 record is found, you know to set the RITM state to incomplete
