2.3.1. Lists, Filters, and Tags
š” First Principle: Providing flexible mechanisms for users to view, categorize, and narrow down records enhances productivity and ensures they can quickly access and manage relevant information.
Scenario: An IT manager needs to quickly see all high-priority incidents assigned to their team. They also want a way to personally mark certain incidents for follow-up without changing their official status.
Lists are fundamental to interacting with records in ServiceNow, presenting data in a tabular format (rows and columns). Filters and tags are powerful tools that allow users to efficiently manage and make sense of these lists. The fundamental 'why' of these features is to empower users to cut through information overload and focus solely on the data relevant to their current task or role. This significantly enhances productivity and streamlines daily operations, from managing incidents to tracking changes.
Key concepts of Lists, Filters, and Tags:
- Lists: Displays multiple records from a table in a row-and-column format. Each row represents a record, and each column represents a field. Lists are the primary way to view multiple records at once (e.g., "All Incidents," "My Open Changes").
- List Layout: Controls which columns are visible and their order. Users can personalize their list layouts, and administrators can define default layouts.
- Filters: Allow users to narrow down the records displayed in a list based on specific conditions.
- Filter Builder: A graphical interface for creating complex queries using conditions (e.g., "Active is true AND Priority is High AND Assignment Group is IT Support").
- Breadcrumbs: A visual representation of the current filter applied, allowing users to easily modify or remove conditions.
- Saved Filters: Users (and administrators) can save frequently used filters for quick access, enhancing efficiency.
- Why use them? To quickly find specific subsets of data (e.g., "Incidents assigned to my group," "High-priority unassigned tasks").
- Tags: User-defined labels that can be applied to individual records for personal organization or informal categorization.
- Visibility: Tags can be private (only visible to the creator) or shared (visible to specific groups or globally).
- Filtering by Tags: Lists can be filtered by tags, allowing users to quickly pull up records grouped by custom labels (e.g., "Critical Bugs," "Follow Up").
- Why use them? To add a layer of personal or ad-hoc categorization that isn't part of the formal data model.
Mastering lists, filters, and tags is essential for any ServiceNow user, especially administrators and fulfillers, as it directly impacts their ability to navigate and manage their work efficiently. It's a key part of personalizing the user experience and ensuring data is actionable.
š” Tip: Encourage users to save their frequently used filters. As an admin, define useful default saved filters for key modules (e.g., common incident views) to guide users and improve consistency across teams. Practice building complex filters in your PDI.
ā ļø Common Pitfall: Over-relying on global filters for individual needs. Encourage users to save their own filters or use tags for personal organization, rather than constantly asking administrators for new global filters.
Key Trade-Offs:
- Flexibility (User Filters/Tags) vs. Standardization (Global Filters): Empowering users with personal filters and tags increases flexibility, while administrators defining global filters ensures consistency across teams.
Reflection Question: How do lists, filters, and tags collectively empower users to manage their workload more efficiently and gain relevant insights from large datasets in ServiceNow?