- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2025 11:04 AM
Hello,
We are considering making certain fields in the RITM and SCTASK read-only. What are the best practices or recommendations for achieving this? Additionally, we need to ensure this applies to both the workspace view and the module view.
Any information that can be shared is greatly appreciated.
Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2025 06:10 AM
Hi @RMendoza
Here you will have the best practice to make field read only:
best-practice-to-make-fields-read-only
I hope my answer helps you to resolve your issue, please mark my answer helpful and correct.
thank you
Rajesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2025 12:24 PM
It depends if you want this to be a platform-wide change or for specific scenarios. If it's platform wide, you can check the "Read only" box on the dictionary record for the table column. I would not recommend that though. I would recommend using UI Policies for your specific use cases. You can set the UI Policies to apply globally or to specific views.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2025 03:37 PM
Hello, is there a reason you don't recommend using the read only box on the dictionary table column? I appreciate your response!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2025 03:52 PM
I guess I would caution against it because it's a global/platform-wide change. In effect, it'll do the same thing as the UI Policies, but I don't believe you can override it (i.e. make the field editable) with a UI Policy in the future; you'd have to uncheck that box on the dictionary record. Out of curiosity, which fields are you looking at locking down?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2025 07:25 PM
If simply readonly then use UI policies which applies to Global so that it works in all the views
Also don't make them readonly at dictionary since if in future any requirement comes in to make them editable based on some condition then at that time you will have to simply update UI policy condition instead of touching the dictionary
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader