State Field Issue - Staff changing the State to Complete with Open Tasks

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2024 06:02 AM
Dont know if there is a solution to this or not, since the State field on RITMS is from the Task table, but for some reason, staff are changing the state of an open RITM to Closed Complete even though there are open Tasks still.
What this does results in a broken flow, so the Request state is still open and the Tasks are still open so they both become orphaned....
Is there a way to make that field Read Only just for RITM's and Requests? We need it visible for other forms like Catalog Tasks, Problem Tasks, etc....
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2024 06:18 AM - edited 12-10-2024 06:19 AM
You will want to create a dictionary override for sc_req_item and sc_request to override read only on State.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2024 06:21 AM
Yes. You can use a dictionary override or a ui policy to do this.
But also check the logic: will everything be closed on task closure? Do all RITMs have tasks?
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2024 07:04 AM
Did a ui policy and it didn't break the logic for flows. catalog tasks still show the field so it can be set to closed incomplete or closed skipped if needed. Yes, all of our RITMS have tasks.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2024 02:00 PM
I would caution on UI Policies as they don't always work. People use list view to get around UI Policies all the time. Dictionary Override is on the Server, not the UI.
Client scripts and UI Policies are not enforced on List UI - Support and Troubleshooting
But I'm glad that it's working for you!