Service users
Service users
Search across every agreement — people from the ARC, agreements from the SM
The v1 Service and Equipment-serial filters are excluded from this release; terminated agreements have their own segment below.
Results
—| Agreement no. | Customer ref. not a column ⚠ — characteristic / ARC ServiceUser.Tag | Full name | Address | Telephone PersonPhoneNumber.PhoneNumber / .Type | Start date ServiceAgreement.ActivatedOn | Status ServiceAgreementState | Open requests |
|---|
Nothing matches the search.
| Full name PersonInfo.FullName | Date of birth | Address PersonInfo.Address | Telephone PersonPhoneNumber.PhoneNumber | Scheme ServiceScheme.Name | ARC status ServiceUser.Status |
|---|
Every ARC service user has an agreement.
| Agreement no. | Full name | Terminated on ServiceAgreement.TerminatedOn | Reason TerminationReason |
|---|
No terminated agreements.
Active = one row per live
ServiceAgreement, person read from the ARC via ServiceAgreementCorrelationEntry. Unassigned = ARC ServiceUser records with no SM agreement — the working list for creating them. ⚠ Customer ref. has no direct column in either model — candidates: a ServiceAgreementCharacteristic or the ARC's ServiceUser.Tag; build question. The v1 columns-chooser arrives with the shared table tools.Service users › Add new agreement
Add new agreement
Create a service agreement for an existing service user — pick who, then complete the agreement details
1 · Who is the agreement for?
| Service user PersonInfo.FullName | Date of birth | Address PersonInfo.Address | Scheme | ARC status |
|---|
No ARC service user without an agreement matches.
The picker lists ARC
ServiceUser records with no SM agreement. The old SM's duplicate validation (surname / DOB / postcode) applies at save.2 · Agreement
Everything above is prepopulated from the ARC service user picked in step 1 and stays editable before save. The remaining ServiceAgreement columns are lifecycle fields (termination, suspension, referral, parent agreement) — set later by their own flows, not at creation.
Installation work is raised afterwards from the profile's + New request — no request is created here (Zori 14 Sep).
Service users › Agreement
—
Active
—
—
Keywords
⚠ not Tag (= stock condition) — ServiceAgreementCharacteristicEdited in the details popup (the identity card's Edit), like v1.
Actions
Suspend / terminate trimmed per Zori's 9 Sep review — agreement lifecycle actions return in a later pass.
v1 tabs not in this release: Assessments · Messages · Audit — no data behind them yet.
Happening now
the live request or ticket, with its tasks OpenAn example of the active item front and centre (per Zori, 9 Sep) — the full list lives on the Requests tab. SM Request / ARC Ticket, tasks beneath.
Recent activity
| When ServiceAgreementStateHistory | What |
|---|
State changes from
ServiceAgreementStateHistory merged with the latest notes — read-only.Contacts
| Order Contact.Ordinal | Contact Contact.Contact_ → Person | Relation ServiceUserContact.Relationship | Type ContactType | Phones PersonPhoneNumber.PhoneNumber / .Type | Actions |
|---|
One merged list: SM
Contact records and the ARC's ServiceUserContact people — the pencil edits a contact in place (same fields as Add). The v1 availability grid is out — no backing columns. ⚠ SM Person has no phone column; numbers come from the ARC.Requests
Tasks shown under each request| Source | Request | Type RequestTypeTicket.Category | Status | Assigned | Next action Request.NextActionDate |
|---|
The v1 layout: every SM request with its tasks beneath (
Task rows); ARC tickets appear in the same list but are not linked to SM requests — they co-exist (Zori 10 Sep). Live by default — the pills switch the view.Equipment
| Item Stock.ModelName | Serial StockItem.SerialNo | Installed StockItemLocationHistory.MovedOn | By | ARC device ServiceUserDevice → Device.Online |
|---|
SM stock custody joined to the ARC's live device record — the Online pill is ARC telemetry, read-only. Click a row for everything held about the unit (slide-out). v1's battery-due column is out (no backing column).
Call history
| When CallRecord.ReceiveTime | Type CallRecord.EventType | Handled by CallRecord.UserId | Outcome / notes CallRecord.OutcomeOptionId |
|---|
Read straight from the ARC's
CallRecord — read-only in the SM. Alarm calls link back to their DeviceAlarmRecord.Notes
The v1 notes model: Permanent and Temporary notes with expiry, filterable. New notes save to the SM Note.NoteContent; rows flagged ARC are EntityNote records, read-only. ⚠ Neither
Note nor EntityNote has an expiry column — a characteristic or the note prefix carries it; build question.