Overview
Reindeer case pages can be configured to match the way each workflow is reviewed. This means different agents can show different fields, actions, layouts, statuses, and review controls depending on what users need to decide.
Dynamic case UI helps teams turn agent output into an operational workspace: reviewers see the right business information, make corrections where allowed, and record decisions without needing a custom application for every workflow.
Questions This Article Answers
- What can change in a Reindeer case page?
- Why do different agents have different case views?
- Which parts of the UI are usually configurable?
- When should users request a UI change?
- What information should be included in a request?
What Can Be Configured
Dynamic case UI can support different review experiences for different workflows.
| Area | What it allows | Example |
|---|---|---|
| Case summary | Show the most important fields for scanning and triage. | Vendor, amount, due date, status. |
| Case details | Organize deeper case information for review. | Extracted values, validation reasons, source details. |
| Field labels | Use business language familiar to the team. | "Supplier" instead of "Entity." |
| Field visibility | Show, hide, or mask fields based on usefulness and sensitivity. | Hide raw source text; show a masked account number. |
| Review fields | Let users record decisions, corrections, and notes. | Approved, rejected, needs more information. |
| Status display | Show where the case is in the workflow. | New, in review, exception, complete. |
| Actions | Provide workflow-specific actions where appropriate. | Reprocess, approve, reject, assign, send for review. |
| Search and filters | Help users find cases by business values. | Invoice number, order number, customer, period. |
The exact options available depend on the workflow and the user permissions in your workspace.
Why Case Views Differ by Agent
Each agent supports a different business process. An invoice workflow may need amounts, payment terms, and validation results. A shipment workflow may need origin, destination, carrier, and delivery date. A support workflow may need requester, request type, priority, and resolution status.
Dynamic UI allows each agent to present the fields and actions that matter for that workflow instead of forcing every process into the same page.
What Users Can Usually Do
Depending on the workflow, users may be able to:
- Review extracted or generated information.
- Compare fields against source documents, emails, or records.
- Correct values that are wrong or incomplete.
- Add notes or reasons.
- Record approval, rejection, or exception decisions.
- Search for related or existing logical cases.
- Reprocess a case after a correction when the workflow supports it.
Some fields may be read-only because they are produced by the agent, controlled by another system, or used for audit and reporting.
What Requires an Admin or Reindeer Support
Most users cannot directly change the structure of a case page. Ask an administrator or Reindeer support when:
- A needed field is missing from the case page.
- A field label is confusing.
- A field should be searchable or filterable.
- A field should be editable but is currently read-only.
- A field is visible but should be hidden or masked.
- Reviewers need a new status, decision, or action.
- The case page shows too much information for daily review.
- Duplicate or related cases are hard to identify.
Good UI Change Requests
Good requests describe the workflow problem, not only the UI change.
Include:
- The workflow or agent name.
- The user group affected.
- The current case behavior.
- The requested behavior.
- The business reason.
- Example case links.
- Any sensitivity or access concerns.
Example:
| Request item | Example |
|---|---|
| Workflow | Invoice review. |
| Current behavior | Reviewers cannot search by supplier invoice number. |
| Requested behavior | Make supplier invoice number visible and searchable. |
| Business reason | Reviewers need to find existing logical cases before creating or continuing a new one. |
| Examples | Include two or three case links. |
Design Guidance
Dynamic UI works best when the case page stays focused.
Recommended patterns:
- Put high-value triage fields in the summary.
- Keep long explanations in detail sections, not list views.
- Use clear business labels.
- Make important identifiers searchable.
- Separate agent recommendations from human decisions.
- Show supporting fields needed to compare possible duplicate cases.
- Mask sensitive values when a partial value is enough.
Avoid adding every available field to the page. Too many fields can make review slower and increase the risk that users miss the important ones.
Related Articles
- Understand Case Fields and Views in Reindeer
- Review and Correct Case Information
- Request Changes to Case Fields and Layouts
- Manage an Agent Case Schema
- Avoid Duplicate Logical Cases
Comments
0 comments
Please sign in to leave a comment.