- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2025 10:08 AM
Should an SCTASK be reassigned from one RITM to another, what is best practice? Any information that can be shared will be greatly appreciated.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2025 10:15 AM
I would advise not reassigning a task from one RITM to another. Ideally, Tasks are created via a Flow and follow a specific process. Reassigning those tasks will break the flow. Also, it will potentially change the Requested For person.
If it's a manually created task, then there is less danger of the flow breaking, but most users don't realize which ones are manually created vs. ones that are created with the flow, so I would caution them not to do that so that they don't reassign the wrong one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2025 10:56 AM
Hi @RMendoza ,
We should not change the SCTASK's RITM number because worflow context which is running on RITM, as the SCTASK mainly created via workflow/flow and the running context hold the sys_id of those SCTASK, if you change the SCTASK & RITM the other running workflow may not understand about this new SCTASK becase of different sys_id.
-Thanks,
AshishKM
Please mark this response as correct and helpful if it helps you can mark more that one reply as accepted solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2025 12:27 PM
Thank you! This aligns with what I had recommended, but I wanted to confirm I was on the right track.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2025 10:15 AM
I would advise not reassigning a task from one RITM to another. Ideally, Tasks are created via a Flow and follow a specific process. Reassigning those tasks will break the flow. Also, it will potentially change the Requested For person.
If it's a manually created task, then there is less danger of the flow breaking, but most users don't realize which ones are manually created vs. ones that are created with the flow, so I would caution them not to do that so that they don't reassign the wrong one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2025 10:56 AM
Hi @RMendoza ,
We should not change the SCTASK's RITM number because worflow context which is running on RITM, as the SCTASK mainly created via workflow/flow and the running context hold the sys_id of those SCTASK, if you change the SCTASK & RITM the other running workflow may not understand about this new SCTASK becase of different sys_id.
-Thanks,
AshishKM
Please mark this response as correct and helpful if it helps you can mark more that one reply as accepted solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2025 12:27 PM
Thank you! This aligns with what I had recommended, but I wanted to confirm I was on the right track.