- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Hi, is it normal that the state field in SOW for a problem is read only? When I click continue problem it takes me to native UI?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Usually state field will be read-only on PRB in SOW as compared to native.
Did you check which client script or UI policy is doing that?
Also "Continue problem" is an OOTB ui action which will take user to native. It's OOTB behavior.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Problem 'state' field is read-only in classic UI as well as workspace out of the box.
To make it editable, you have to disable UI Policy, Client Script and Dictionary over-ride. It is not recommended to change this behavior but below is for reference,
UI Policy - 'Make Problem State read only'
Client Script - 'Make Problem state readonly'
Dictionary Override - go to state field -> Configure Dictionary -> Open Dictionary Override table 'problem' base table 'task' and disable 'Override read only'
State field - Editable in Classic UI after the changes
State field - Editable in Service Operation Workspace after the changes
Revert the changes to make it back to read-only.
If this helped to answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Usually state field will be read-only on PRB in SOW as compared to native.
Did you check which client script or UI policy is doing that?
Also "Continue problem" is an OOTB ui action which will take user to native. It's OOTB behavior.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Thank you, I found it was a client script so made it inactive
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Problem 'state' field is read-only in classic UI as well as workspace out of the box.
To make it editable, you have to disable UI Policy, Client Script and Dictionary over-ride. It is not recommended to change this behavior but below is for reference,
UI Policy - 'Make Problem State read only'
Client Script - 'Make Problem state readonly'
Dictionary Override - go to state field -> Configure Dictionary -> Open Dictionary Override table 'problem' base table 'task' and disable 'Override read only'
State field - Editable in Classic UI after the changes
State field - Editable in Service Operation Workspace after the changes
Revert the changes to make it back to read-only.
If this helped to answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Did you get a chance to review this ?
As per community guidelines, you can accept more than one answer as accepted solution. If my response helped to answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan