LEARN. PRACTICE. GROW.Concept and mechanism
A list represents a set of records subject to conditions. Confirm the table and AND/OR logic before interpreting a count. Breadcrumbs show the current filter and allow conditions to be removed; creating a record from a filtered list can preset values from that filter. Review those values before saving. Templates also populate fields, but do not prove that the values remain correct for every case. Journal fields append entries to the activity history when saved. Choose communication content and audience using the effective configuration; do not assume confidentiality solely from the Work notes label.
Guided application
During a production shift, a shared tag helps find tasks for the same event, while a guided Visual Task Board represents tasks and field values. Leaving the filter can remove a card without deleting its task. Notifications require separate analysis of trigger, recipients, and content. A generated message does not prove delivery or reading. For historical analysis, distinguish current data from scores collected over time. Historical Performance Analytics collection can replace previously collected scores for selected indicators and periods; it is not a harmless visual refresh. To compare teams, keep population, period, timezone, and indicator definition consistent. Use underlying records to resolve differences before drawing performance conclusions.
A card can disappear because it no longer matches the filter.
Common pitfalls
Count without population; tag treated as an ACL; historical collection treated as refresh.
Related topics: Instance, navigation, and context · Configuration, access, and interfaces · Knowledge and catalog
Connect every visualization and message to its source records and rules.
Reference: Filters and breadcrumbs · CSA blueprint January 2026