- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-22-2025 02:00 AM
Business Issue:
When a user logs in to the SSP, they can see tickets that have been raised for their them as an individual and their Customer Account which is the desired behaviour and working as expected. They have the ability to report on and export data which is also working. They also have the ability to create filters on the data presented and this is where the issue resides. If they use the "Location" field of the "Asset" / "CI" in the filter, the input field asks for the user to start typing and then shows any locations that have that character or value even if it is not associated with their Customer Account.
The images below show the query being built and then showing "Damian" which is a test address not associated with the Customer
Expected outcome
The user needs to be able to filter on the location field, but I need to create logic such as a Business Rule / UI Policy / Data Policy that ensures only the locations associated with the Customer Account / User Logged in are displayed.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-22-2025 02:56 AM
you can create a query business rule on cmn_location table such that you can show only those locations to which logged in user belongs or show only those locations which belong to the users belonging to the group you are part of
There is already a query business rule on incident table, check that as an example and create for location table
check this blog
Query Business Rules: A Definitive Guide
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
‎05-27-2025 12:12 AM
Hi Ankur,
Thanks for following up, your approach was the correct approach, but I do not have the skills to develop the rule myself, so has been passed to the Development Team for consideration.
Kind regards,
Damian