Understand case activity¶
Case activity helps people follow recorded work: who added a participant, recorded a decision, changed a task, linked supporting work or closed a case. Use it alongside the current case detail. A timeline entry describes an event or saved snapshot; it does not establish the latest state of every linked system or provide a complete history of every field change.
Availability: The intended journey follows the inspected Case Activity final design. The frontend still renders sample activity. The shared activity delivery path also has an unresolved routing mismatch, so connected access and deployment are unverified. Ordering, discussion and some example summaries need reconciliation before this screen can be accepted.
Read the intended activity view¶
- Find the case in the case register, open it and confirm the reference and title.
- Choose Activity alongside Overview, People & accountability and Work & relationships.
- Review the recorded actor, action and time. Compare an important entry with the current case detail or the linked source before acting on it.
- The design pairs the activity list with a selected-update panel and View full activity. The connected selection, destination and companion states remain unverified; do not treat the preview panel as proof that a live event or discussion was loaded.
The design says “newest first,” but the current feed returns the oldest entries first and continues forward in pages. That discrepancy needs correction or an explicitly implemented presentation strategy. Reversing one page would not make it a complete view of the newest activity. Check the displayed dates instead of assuming the first row is the latest change.
Case-read permission still applies. Restricted and Secret cases require the owner or an active participant, and protected HR cases require additional HR authority. A staff member's own HR-query response view is a separate experience. Seeing an activity link does not grant access to the underlying case, workflow or record.
What an entry can establish¶
| Recorded work | Meaning and limit |
|---|---|
| Case creation | A case was created. The entry does not prove that its dossier and other dependent work have finished. |
| Participant added | The person and role were added. This does not prove an invitation or notification was delivered. |
| Decision recorded | A decision has an outcome, optional summary and possible next stage. Read the decision itself before interpreting a short approval or rejection headline. |
| Task created or changed | A task was created, moved into Completed, had its due date changed or received another update. A task update is not case closure. |
| Supporting work linked | A relationship was saved. It does not prove the letter was delivered, record filed or external work completed. |
| Workflow linked | The case stores a workflow link. Its saved title and status can lag behind the workflow's current state. |
| Case closed | Closure recorded the outcome and closing actor/time. Outstanding tasks and workflows remain separate work. |
| Case note | A note was added or its displayed content was revised. It is not a separate immutable row for every edit. |
The feed groups entries into broad categories such as comments, assignments, status changes and decisions. A decision whose outcome is treated as an ordinary status update may appear under status changes. The design's Decision, Task, Linked work and Workflow badges are not a verified set of feed categories.
Approval and rejection labels are currently derived from words in the recorded outcome. They do not independently prove that an approval process ran or that an authorized reviewer approved all supporting work. For consequential decisions, read the actual outcome, summary and current stage.
Staff-party additions, case-type administration and HR operations also have a separate governed activity-log path. A preview's “Staff party added” row does not establish that the ordinary case timeline receives that event. Absence from this timeline alone is not proof that an action failed or went unrecorded elsewhere.
Separate case history from the case timeline¶
Organization activity history also records selected staff-party, HR-query and case-type actions. Use the history reader guide for that view. Its entries and the case timeline do not contain the same events or use the same presentation.
For HR queries, the separate history can record saving a draft, requesting issue, submitting or recording a response, extending a deadline, reviewing the query and withdrawing it. A Completed entry describes the recorded action. Requesting issue does not prove that a notice was delivered; recording a response or outcome does not prove that its document has finished filing. Use the HR-query guide and the current notice, response and filing state to confirm those results.
When an employee submits a response, that employee is the recorded actor. When an authorized administrator records an offline response, the administrator is the actor and the employee is a separate affected person. The history time uses the response record's creation time, which can differ from the date the offline response was received. A response supplement follows the same recording action as its response channel; the short history entry is not a complete response-version history.
Staff-party and HR-query recording resolve affected people through the case's available staff information where needed. Missing affected-person information does not mean there was no staff subject. My activity shows actions attributed to the signed-in account; it does not list everything affecting that employee. The entries omit the notice body, response text, review reason and full before-and-after settings. Use authorized case records for those details.
Case-type creation, update, activation and deactivation have their own entries. Repeating activation or deactivation when the type already has that state can still reach recording using the type's previously saved person and time. Those details may describe an earlier change, and recording can fail if that person's details cannot be resolved. Do not infer a new state change, its time or its initiator from the short entry alone. Report a mismatch with the original action result and case-type reference.
Notes, edits and discussion¶
A case note appears as a comment-style activity entry. Editing or redacting it updates that same entry rather than adding a full series of revision rows. Its position keeps the note's creation time. The displayed actor and headline can remain those from the first projected entry, even after another authorized person redacts it. Do not interpret that original label as the identity of the latest editor or redactor.
The note's saved content and the activity copy are different records connected by background delivery. Delayed or failed delivery can leave them temporarily different. The inspected projection also lacks a check that rejects an older, previously unseen note revision after a newer revision has arrived. A display that appears stale or unexpectedly restores older text needs support investigation; repeatedly editing the note is not a reliable repair.
The design's discussion beside a decision is not backed by a verified general case-discussion operation. Case tasks likewise do not have a verified reply thread through the current shared activity reader. Use the documented case-note operation for case context where available; do not assume that a reply is attached to a specific decision or task.
Protected HR entries can deliberately replace their content with a confidential placeholder. That is not evidence of a failed save. Open the case through your authorized HR journey when the details are needed. The placeholder does not make the entire entry anonymous: references, timing, actor information and status can still be present.
Names, linked work and completeness¶
An actor name is a saved display snapshot. Case activity prefers the available staff profile, with a current-user email or identifier as a fallback. “System” represents an absent actor identity; a generic name or identifier does not by itself explain why that identity was unavailable. Later profile changes do not rewrite every old activity label.
Case activity and workflow activity do not automatically mirror each other. The case's workflow-link event is associated with that workflow, but the current workflow publisher does not add the case to every workflow event. A workflow can progress without each later event appearing in the case list. Open the workflow to check its current progress.
The feed is delivered asynchronously and read in pages. It is not a frozen export of all history. A late event can arrive earlier in the timeline than the page you have reached, so start a fresh traversal when reconciling missing work. The inspected case design does not yet establish the complete paging, filter and empty/error controls.
Recover from missing or misleading activity¶
| Situation | What to do |
|---|---|
| An action succeeded but its activity is absent | Refresh the saved case or task first. Avoid repeating a mutation solely to create a timeline row. |
| The case loads but Activity does not | Report the activity failure separately, with the case reference and time. Connected delivery still needs verification. |
| An entry's label disagrees with the saved result | Check the actual decision, task or linked source and report the discrepancy. |
| A note shows old text or an unexpected identity | Compare the saved note and report the timing through an approved channel. Avoid copying confidential content into an ordinary support message. |
| HR content is replaced by a placeholder | Use the authorized HR case view. Do not try another person's access or infer details from the placeholder. |
| A linked workflow's later work is missing | Open the workflow; linking does not synchronize its whole history into the case. |
| A discussion or full-activity control is only a preview | Do not treat it as a saved conversation or complete record. Ask the case manager to confirm the available connected path. |
For managers and reviewers, use activity to locate supporting evidence and coordinate follow-up. Use the current decision and source records for the final conclusion. Neither a row count nor a completed-looking headline is a complete measure of work quality, delivery or accountability.