
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-13-2020 02:32 PM
I need to create a flow designer that counts down after a specific RITM item has been closed (where active is false). The count down time is defined by a variable inside the corresponding RITM and will vary.
Where I attempt to trigger the flow off the table it cannot be found. Only the request table is an option and that will not work because the variable isn't stored in the request.
Are there alternatives to meet the business need? I'd prefer to not add wait to the RITM workflow as the customer should be alerted the REQ has been completed and the follow up mitigation items should be hidden.
Solved! Go to Solution.
- Labels:
-
Flow Designer

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-13-2020 03:09 PM
Hi Tiffany,
Are you able to attach some images of your issue? I've tested based on your explanation and having no issue.
Flow:
Set "Time" to the duration before closing.
Flow waits the provided amount of time
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-18-2021 02:06 PM
I think I have an answer.
Considering the sc_req_item Table is extended from the Task table... create the trigger on the Task table.
I'm in the midst of doing the same thing (with my requirements is adding certain persons in a department to the RITM, request item, Watch List if anyone from their department submits a request).
.Ray Ennis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-30-2021 04:38 AM
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0749602

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-28-2022 12:18 PM
In case it helps anyone, I had a requirement to ensure Requests are closed out when their child items/tasks are all closed. This could happen if the traditional workflow was not built properly, or, it could happen where ITIL users did not close the Request properly, or some combination thereof.
To solve for this, I chose to use a scheduled Flow. So the Trigger is simply "Daily at 21:00:00". Then in the Actions I use Look up records on the Requested Item table to identify any where updated is today, Active is false, but Request.Active is true.
I then can look for any sibling records, and if no active siblings are found, I can mark the Request as closed and inactive.
I hope this helps!