Attention Item
What It Is
An attention item is an occurrence of a condition staff need to consider. A closed batch awaiting posting or an uncovered responsibility area has meaning because something is outstanding in its owning application. Platform presents that condition through Home, the attention list and the bell. A group on Home summarizes several occurrences rather than creating a separate piece of work.
The application declares the kind of condition and publishes its occurrences. Each occurrence has facts, an optional due date, a record it concerns, scope information and audience criteria. The provider resolves it when the condition clears, while repair sweeps maintain the projection. A fresh recurrence gets a new generation, allowing a later problem to be distinguished from one a person already handled.
What It Is Not
An item is not a task or an editable business record. Its standing follows the source condition rather than a staff checklist. It is also different from a notification: the condition persists, while a reminder is a delivered message about it. Seeing the condition grants no access to its record and no permission to perform the offered action.
How It Is Used
Staff review their own attention and open an occurrence to understand its cause and relevance. The explanation helps them move to the owning application to act. Personal acknowledgement and snooze manage presentation without clearing the underlying condition. Administrators can inspect others’ attention with separate audited authority or resolve an occurrence manually with a reason. Turning off a kind hides work; it does not establish that the work is complete.
Its Facets
Declared kind. An application defines class, facts, audiences, templates, actions and lifecycle settings. Keeping occurrences of the same condition consistently understandable.
Seriousness. Required, advisory and opportunity are fixed application choices with different personal actions. Preserving priority and dismissal boundaries.
Recipient criteria. Audiences describe responsibility, role or individual matches rather than recipient copies. Applying current holdings when a viewer reads.
Resource ancestry. An application-provided chain identifies increasingly broad scopes and the workspace. Finding appropriate local or wider coverage.
Facts and timing. Declared typed facts and due dates supply explanatory content and urgency. Showing the reader what matters about the condition.
Personal response. Acknowledgement, snooze and permitted dismissal belong to each viewer. Managing visibility while preserving other recipients’ views.
Shared tuning. Workspace settings adjust supported wording, surfaces, rank and follow-up choices. Adapting presentation within the application’s bounds.
Personal visibility. Optional kinds can be hidden in one person’s own summary and list. Reducing unwanted optional attention without concealing required work.
Follow-up. Escalation adds an audience and reminder planning identifies people to prompt. Bringing persistently overdue conditions to further attention.
How It Relates
Responsibility holdings help audience resolution determine whose Home includes an occurrence. The provider owns the condition, its resource ancestry and its business resolution. Platform owns the shared presentation, personal responses and sweep machinery. Current reminder delivery uses communications, although the approved boundary assigns that delivery to Notifications. Supported merges redirect references to surviving records.
What It Could Become
The product should complete the shared settings and personal preference surfaces and align reminder delivery with Notifications. Portal attention and customer-authored kinds remain held. Record-page placement and lifecycle business events are additional delivery edges. Each extension needs evidence of its own surfaces and permissions before the existing attention projection is described as proving it.