Client services and goods in Extranet
The Services & goods tab shows only records published to the client’s external work context. It is read-only: the client cannot change an order, agreement, date, or status here.
What a row shows
Conceptual guidance, not a UI screenshot or portal evidence.
A row can include the commitment title or type, status, promised quantity/unit, due date, fulfillment state, remaining entitlement or period, and source context. The visible fields depend on the available data.
If a technical code or ID appears instead of a name or context, do not treat it as the client or commitment name. Keep the frame private and ask staff to verify the source data and access rights.
Remaining is shown only when a separately permitted entitlement with a current period is available. If that field is absent, the portal does not calculate a remainder from the promised quantity: missing remaining does not mean zero.
When the balance is available, read remaining as available / granted in the entitlement unit. The server may normalize time (for example, minutes into hours); a missing ratio means the current balance is unavailable or unreadable, not zero.
The summary groups items by work state:
- To fulfill — work remains;
- Upcoming — due later;
- Fulfilled — completed with a result;
- Closed — completed in another valid state.
These groups are for reading, not state changes. If a date, quantity, or status looks wrong, contact the team; staff should check the source order and agreement.
Summary and statement
Conceptual guidance, not a UI screenshot or portal evidence.
The summary answers “what is available now”: a row may show What, Period, Total, Used, and Left. The state tabs are All, In effect, Upcoming, Done, and Closed. When a row has a statement, open it without changing data; its address has the form /extranet/commitments/<entitlementId>.
The statement shows the remaining amount and period end, and only shows carry-over or expiry when the source proves it. It may include movements, previous periods, and a reconciled running balance; when reconciliation or invoice linkage is unavailable, the portal hides the balance or says that it does not publish which invoice covers the entitlement. Do not read a missing balance, invoice, or link as zero or unpaid. For demonstrations, use synthetic client Client Test, contexts Northwind Demo and Bluebird Demo, and rows with no real IDs, agreements, invoices, or amounts; the flow is read-only.
Contexts and filters
Conceptual guidance, not a UI screenshot or portal evidence.
The panel combines commitments when a client has multiple contexts: a personal contact and one or more companies. An account filter appears only when more than one context actually has commitments; with one source it stays hidden. A work-state filter is also available.
After changing context or work state, wait for the new results. An empty filtered list does not prove that the client has no commitments.
Loading and privacy
Conceptual guidance, not a UI screenshot or portal evidence.
Loading, error/retry, empty, and empty-after-filter are different states. On an error, retry once and then tell staff the time, context, and visible message without copying internal IDs.
The panel must not expose another company, internal task, hidden comment, or service identifier. Use synthetic titles and dates in docs, and leave out bank or contract details.
If the context is stale, reads pause while the portal shows a neutral access-update state, not an empty or generic error list, and automatically rereads after recovery. If access cannot be refreshed, the panel explains that and offers Retry or asks you to reload and contact the manager. Do not treat old data as current or copy a technical code.
Related pages
Conceptual guidance, not a UI screenshot or portal evidence.