The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | /console/{tenantId}/crm/contacts/{contactId} | Navigate to a readable contact. | CAP-PFM-OPS-008 | Successful display initiates one recorded visit. | test react-console:e2e/controlled/record-views.controlled.spec.ts#reports one visit per navigation, and the header lists the records newest first |
| 2 | /console/{tenantId}/crm/contacts/{contactId} | Move between tabs on that contact. | CAP-PFM-OPS-008 | The established navigation remains one visit. | test react-console:e2e/controlled/record-views.controlled.spec.ts#switching tab on the same record is still one visit |
| 3 | recordRecordView | Navigate to a readable organization. | CAP-PFM-OPS-008 | The organization report is accepted with its required read and query authority. | test services-platform:modules/audit/tests/e2e/record-views.e2e.spec.js#records a view of an organization for a caller holding organization read and organization query |
| 4 | the console header's Recent Items menu | Open the personal Recent Items menu. | CAP-PFM-OPS-008 | The query presents recent readable records once each with current names. | test react-console:e2e/controlled/record-views.controlled.spec.ts#a record visited again is reported again but appears once in the list |
| 5 | listMyRecordViews | Request the raw visit history. | CAP-PFM-OPS-009 | History returns visit entries in descending order, retaining visits independently of later record deletion. | test services-platform:modules/audit/tests/integration/services/record-views/view-history.integration.spec.js#answers the newest event first |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 2 | Navigation reloads or later returns to the record. | Report a new navigation identity. | A successfully retained visit can move the record into recent work again. | test react-console:e2e/controlled/record-views.controlled.spec.ts#a reload is a new visit, and the list survives it |
| failure | 1 | Visit reporting exhausts its retry budget. | Retry silently with the same navigation identity. | The person’s record work continues even when no visit lands. | test react-console:e2e/controlled/record-views.controlled.spec.ts#a failure to report a visit never reaches the person, and the retries are one visit |
| failure | 1 | The contact never becomes readable. | Report no successful visit. | Recent work remains unchanged by that unsuccessful navigation. | test react-console:e2e/controlled/record-views.controlled.spec.ts#a contact that cannot be read is not a visit |
| Id | Statement | Provenance |
|---|---|---|
01 | One person’s recent-work query excludes visits attributable only to another person. | test react-console:e2e/dev/record-views.dev.spec.ts#somebody else's Recent Items holds none of this person's records |
02 | Recorded views and the header’s query work through the deployed service boundary. | test react-console:e2e/dev/record-views.dev.spec.ts#the records a person opens are recorded in the Platform and read back by the header |
End-to-end policy: required: Navigation, tabs, reloads and silent reporting retries require browser evidence, with deployed tests also checking personal isolation.