Appearance
Header actions
Last updated: 2026–05-27
The detail page header (below the breadcrumb) holds global actions that apply regardless of which tab is active.
Auditor warning: Request OTP, Update Status, and Schedule are hidden entirely for the Auditor role. Download Application PDF remains available.
Download Application PDF
| Item | Detail |
|---|---|
| Control | Download icon with tooltip “Download Application PDF” |
| Action | Generates/downloads a PDF snapshot for the current session |
| Roles | Available to all roles that can open application detail, including Auditor |
Use case
Export a point-in-time summary for compliance, mail packages, or offline review.
Update Status
| Item | Detail |
|---|---|
| Control | Primary button labeled Update Status |
| Opens | Dropdown of allowed transitions, then a confirmation modal |
| API | UpdateAppStageAPIView — updates stage flags, may run workflows, webhooks, and emails |
Status options (manual)
| UI label | API status code | Typical effect |
|---|---|---|
| Approve | 1 | Sets stage to Approved, may continue workflow, triggers application.approved webhook |
| Decline | 8 | Sets stage to Declined, triggers application.declined webhook |
| Doc Requested | 5 | Sets stage to Document, triggers application.request_docs webhook |
| Withdrawn | 100 | Sets stage to Withdrawn, may send withdrawn email template |
| Closed | 10 | Sets stage to Closed |
| Processing | 0 | Resets to Processing stage |
Which options appear depends on the current stage (for example, from Approved you can still Decline, request docs, withdraw, move to Processing, or Close).
Modal fields
| Field | Required | Purpose |
|---|---|---|
| Outcome | Often | Tenant-configured assignment tied to the action |
| Tab / step | Sometimes | For doc request or decline flows tied to a template tab |
| Note | Optional | Appended to activity log; may also create an application note server-side |
| Approve variables | On Approve (if configured) | Extra fields collected before approval is finalized |
Approve with variables
If the product defines approve variables, choosing Approve opens a secondary confirmation to capture those values before the status API runs.
Use cases
| Scenario | Steps |
|---|---|
| Manual approval after review | Update Status → Approve → select outcome → add note → confirm |
| Request paystub | Doc Requested → pick tab/step if prompted → confirm |
| Wrong approval | Decline or Processing (if available) per policy, then re-run workflow from Application tab |
Edge cases
| Situation | System behavior |
|---|---|
| RAI tenant | Approve may route to a review queue and send continue-application email |
| Was in review/doc state before approve | May run child decision tree or continue_application instead of simple approve |
| DealerTrack source | Status change may notify external dealer system; failures can block the API response |
| Sandbox session | Webhooks and async jobs use the sandbox database queue |
Implementation notes
- The UI component is named
UpdateStagein code but the button reads Update Status—it does not move a separate “pipeline stage” (Application → Underwriting → Funding). - Decline uses assignment action mapping
8in the UI but may map outcomes withaction === 2in the outcome picker. - Notes entered here can be duplicated into the structured
app_notesarray on the application record.
Request OTP
| Item | Detail |
|---|---|
| Control | Request OTP button → modal |
| Methods | Email and/or mobile (based on applicant contact data) |
| Flow | Send → applicant receives code → agent can verify six-digit OTP in modal |
| Expiry | OTP send state tracked ~30 minutes per session (client-side persistence) |
Use cases
Verify applicant identity before discussing account details on a phone call, or before sensitive manual steps.
Edge cases
| Situation | Behavior |
|---|---|
| Missing email and phone | Method selection may be limited |
| Resend | Available after initial send |
| Verify failure | User stays in modal; no status change |
Schedule (Cashmax only)
| Item | Detail |
|---|---|
| Visibility | Shown only when the application’s tenant domain includes cashmax |
| Control | Schedule secondary button |
| Modal | ScheduleAppointment — books an appointment linked to the application |
Non-Cashmax tenants never see this control.
What is not in the header
| Feature | Actual location |
|---|---|
| Edit applicant wizard fields | EditApplication modal exists in code but is not exposed via a header edit icon in the current build—use Application tab section edit |
| Assign / tags | Overview panel |
| Revert workflow step | Application tab per-section Revert to this step |