Configuration and History

The Service Administrator maintains the service definitions used by cases. Each definition belongs to an organization and can carry an effective period and policy reference. People also belong to organizations, giving the office a way to assign case ownership and review work. Source mappings hold reviewed field and transform rules for a service definition. State history records case status changes with the actor, time, reason and source revision.

The Service Administrator maintains active service definitions for the responsible organization. Each definition can carry effective dates and a policy reference. The team uses People records to identify case owners and reviewers within an organization. Source mappings describe how an incoming field should relate to a target field for a service; review the mapping before a connected intake channel supplies case information. State history then shows the actor, revision, reason and time behind a case status transition.

• Record. The Service Administrator maintains active service definitions for the responsible organization.
• Review. Agree who can create or change service definitions and who will review a mapping with a sample input.
• Handoff. Use the selected case to compare its organization and service definition with the configuration records.

Agree who can create or change service definitions and who will review a mapping with a sample input. The Service Administrator manages public services while the configured role reads source mappings; arrange mapping changes through the team that has the required access. Check an organization’s active flag and the definition’s effective period before letting an officer use the definition for a new application.

Name the people who may own cases and those who may review them. A person’s organization should match the case assignment. Decide how the team will investigate a disputed status change: start with the case revision, then inspect the transition actor and reason. Preserve that trail when a later correction changes the current case.

Choose an active organization and a service definition with the right effective period. Open a case under that definition and assign a person in the responsible organization. Check the field mapping that connects an incoming source value to the intended target field. Follow the case through submission and review, then read the state history to identify who changed its status and which revision the transition concerns.

Use the selected case to compare its organization and service definition with the configuration records. Ask the Service Administrator to explain the mapping for one incoming field and the Case Officer to show the chosen owner. After a status change, let the Read Only Analyst identify its actor and source revision from history.

• Active service definitions — Review definitions, owning organizations and effective periods.
• Case status board — Check a selected case against its status trail.

Follow case review from preparation to independent decision. Use delivery and correction when an approved outcome needs execution or an earlier revision needs correction.