Business Rules / UI Policies / Client Scripts not applying to Service Operations Workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2025 09:07 AM
We have a lot of things to prevent users from being able to make modifications to changes / incidents / etc., for instance, depending on the state of each.
None of these rules are applying to the service operations workspace.
People are able to use the various Workspaces to essentially bypass all the security rules we have in play. What am I missing? Why are the rules we applied in the normal view of the servicenow backend not applying to SOW?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2025 09:14 AM
Hello @Venjamin
In case of business rules you need to check the parameter after getting the url.
Sysparm_view == 'sow' - then you apply changes here as well.
In case of client scripts , there is a separate field called 'View' where in you can write - service operations workspace and it will apply on it.
In case of UI Actions - there is a workspace configurable section as a whole and also client script section where you need to configure.
For data policies, there are separate policies which you can apply in UI Builder directly by selecting elements in the form.
I hope this answers your queries.
Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket.
Regards,
Shivalika
My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194
My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY