- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2026 05:57 AM
My RITM field is showing empty and read-only, but the SCTask description is populated from Flow Designer. How can I sync values back to the RITM?
Solved! Go to Solution.
- 929 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2026 11:14 AM
You can update the RITM description field via a Business Rule when sc_task.description is updated, or when you are setting this field in the Flow, also add an activity to update the trigger record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2026 11:58 AM
One thing to note - if your flow is built to create the task as a "task" on the "sc_task" table, rather than as a "catalog task" (specifically), you may face synchronicity issues between the records or other unexpected results. I've been there before - so maybe double check your flow and make sure you need to fix the problem this way first...you may find that you fix it upstream instead.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2026 11:46 PM
I fixed the issue with my UI policies by deactivating one and adjusting the order of the other. Everything is working as expected now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2026 11:14 AM
You can update the RITM description field via a Business Rule when sc_task.description is updated, or when you are setting this field in the Flow, also add an activity to update the trigger record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2026 11:52 AM
Use business rule
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2026 11:58 AM
One thing to note - if your flow is built to create the task as a "task" on the "sc_task" table, rather than as a "catalog task" (specifically), you may face synchronicity issues between the records or other unexpected results. I've been there before - so maybe double check your flow and make sure you need to fix the problem this way first...you may find that you fix it upstream instead.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2026 11:46 PM
I fixed the issue with my UI policies by deactivating one and adjusting the order of the other. Everything is working as expected now.
