I struggled a bit with this (and the documentation out there), so figured I’d share with the community.
In relation to: https://docs.servicenow.com/bundle/orlando-platform-administration/page/administer/list-administrati...
I was looking for a use case that would allow managers to rank incidents without creating a custom field. The rub is, context ranking only works on related lists…and I struggled to think of an OOB “related list” that would be appropriate for a manager to go in and rank incidents for any employee to work.
This was my solution:
- System Definition | Relationships:
- Create a relationship (Insert and stay on Incidents by same caller)
- Name it "Incident Ranking"
- Change the script to break it, so the query returns nothing (e.g. current.addQuery('assigned_to', "returnnothing"). Note: You are breaking intentionally because the query WILL NOT keep the ranking order and IMHO, it's just confusing to have a list of incidents sorted by one thing, then to click rank and have a list of incidents likely sorted differently.
- System Definition | Ranking Definitions:
- Name = Incident Rank
- Record table = incident
- Context column = assigned to
- Relationship table = incident
- Context column = assigned to
- Browse to Incidents | All - click on any incident to load the incident form:
- Context menu | Configure | Form Layout
- View name | New | Ranking | Save
- Back on the incident, switch to the ranking view:
- Context menu | View | Ranking
- Add related list "Incidents Ranking" (created in first step)
- Context menu | Configure | Related Lists...
- End results is related list tab which returns no records, but has a “rank” button. Clicking it allows you to rank incidents where the “assigned to” is the equal to the incident you originally went into. Every individual assigned to creates a different ranking index. Below is a image of what it looks like once you click RANK.
