Application detail — Application tab

The Application tab (left column, default on open) shows product-defined sections of applicant and loan data. Each section is a collapsible accordion. Agents with edit permission can change values inline, then Update with optional re-run of the application flow, or Revert to this step to roll the applicant back.

Parent: Application detail. Header actions (status, OTP): Overview and header.

[NEEDS SCREENSHOT: Application tab — multiple section accordions, read-only]

---

What you see

Content comes from other_data on the application detail API—section title → fields. Sections and field labels vary by product and flow (Acme Personal Loan vs Auto Loan will differ).

Typical section names (examples only):

• Applicant Information
• Employment
• Financial Information
• Loan Details
• Custom questions

Each field row shows:

• Label (may include HTML formatting from product config)
• Value — formatted by display type:
  • Currency (display_type 2): $12,500 style
  • Percent (display_type 3): 42.5%
  • Empty / NA: shown as N/A
• Variable tooltip (brand icon) when engine_name is set — links to variable documentation behavior

If a section has no fields, a fallback empty state appears inside the accordion.

Acme example — app 10501 (Alex Rivera, Personal Loan):

Section	Sample fields
Applicant Information	Full Name, Email, Phone, Address
Employment	Employer, Job Title, Years Employed
Financial Information	Annual Income $85,000, Monthly Debt $1,200
Loan Details	Requested Amount $15,000, Term 36 months

[NEEDS SCREENSHOT: Financial Information section — currency fields]

---

Edit permission

Inline edit is controlled by allow_edit from the server—not by a visible “Edit application” button in the v2 toolbar (the legacy wizard iframe modal exists in code but is not exposed in the header).

allow_edit	UI
true	Each section shows an Edit control in the accordion header
false	Read-only fields only

Auditors and applicants do not get agent edit affordances on this tab.

When edit is off: Stage/status may be locked (e.g. funded/closed), or role may be read-only. Use Update Status in the toolbar only if your role and stage allow it.

---

Read mode vs edit mode

Read mode (default)

• All sections collapsed or expanded per last interaction.
• Values in a two-column grid on medium+ screens.
• Click section Edit to enter edit mode for that section only (one section at a time).

Edit mode (one section)

What happens when you click Edit on a section:

1. That section’s fields become inputs (text, select, date, etc.) via EditableField — control type comes from variable metadata.
2. Changed fields get a green highlight background (dirty state).
3. Footer appears on that section:
   • Revert to this step (secondary)
   • Cancel (secondary)
   • Update (primary)
4. Password-labeled fields are not submitted on save.

What happens when you click Cancel:

• Exits edit mode for the section.
• Discards unsaved edits (form reset).
• Clears selected section label used for re-run.

[NEEDS SCREENSHOT: Section in edit mode — highlighted field + Revert / Cancel / Update]

---

Update workflow

Step-by-step — save without re-running flow

1. Edit on Financial Information.
2. Change Annual Income from $85,000 to $92,000 (field turns green).
3. Click Update.
4. Modal Apply changes to application? opens.

Option	Label	Meaning
A	Update value only	Persist variables only; no decision re-run; applicant not sent back in wizard
B	Re-Run Application flow	Save and re-execute flow from this step (see Re-run below)

5. Leave Update value only selected → Apply changes.
6. On success, edit mode closes; toast success; values refresh from API.

What happens when you click Apply changes (update only):

• updateAppData sends only changed engine_name / value pairs.
• If nothing changed, warning toast: No changes to save.
• Validation errors block save: Please fix validation errors before saving.

Step-by-step — re-run application flow

1. Edit section and change values.
2. Update → choose Re-Run Application flow → Apply changes.
3. Apply changes to application? revert-style modal runs processing (~1s spinner).
4. Outcomes:
   • No change in the flow — applicant does not need new steps; button Done closes.
   • Flow changed — applicant must complete additional steps; optional Notify applicants via email template; Send update runs revert API with re_run_flag.
   • Processing... — wait up to ~10s; UI may fall back to no-change message.

Acme scenario: Taylor fixes Alex’s income on Financial Information, re-runs flow; outcome Flow changed → selects template Continue Application → Send update. Alex receives email to complete updated steps.

[NEEDS SCREENSHOT: Apply changes modal — two radio options] [NEEDS SCREENSHOT: Re-run result — Flow changed with notify template]

---

Revert to this step

Revert to this step appears in the section footer while editing (when allow_edit is true).

What happens when you click Revert to this step:

1. Modal Revert the application to this step? opens.
2. Warning: applicant must return to this step; progress after this point is cleared.
3. Optional Notify applicants via — email template select (continue or application-reverted templates).
4. Revert confirms; Cancel aborts.
5. While submitting, button shows Reverting... and other footer buttons hide.

On success: Section edit mode closes; applicant wizard rewinds to the section’s saved step; optional email sent.

When to use vs Update:

Action	Use when
Update (value only)	Correct data; keep applicant on current step
Update (re-run)	Data change should re-evaluate flow/decisions
Revert to this step	Applicant must re-complete from an earlier step without your new field values driving a re-run first

Acme example: Alex skipped employment verification. Underwriter opens Employment → Revert to this step → notify via Application Reverted template.

[NEEDS SCREENSHOT: Revert modal — warning banner and template select]

---

Cancel during edit

Control	Effect
Cancel (section footer)	Exit edit mode; discard changes
Closing browser tab	Unsaved edits lost

Revert pending state disables Cancel and Update until revert completes (only Revert button shows loading).

---

Field-level tooltips

Fields with an engine_name show a tooltip trigger (variable icon). Use this to trace values back to Model Studio / variables on the application.

What happens when you interact with the tooltip: Displays variable context for the session (implementation follows shared InputWithTooltip behavior).

---

Validation and errors

Situation	User-visible result
Invalid field (schema)	Toast: fix validation errors
No changes on save	Toast: No changes to save
Missing app ID	Toast: Application ID is required
API failure	Error toast from API message

Password fields are skipped silently in the payload even if touched.

---

Use case mini-scenarios

1. Fix typo in employer name (CSR)

Goal: Employer spelled “Acme Corp” vs “Acme Corporation” — no decision impact.

1. Application tab → Employment → Edit.
2. Fix Employer text.
3. Update → Update value only → Apply changes.

Outcome: List and underwriting see new text; applicant not disturbed.

2. Income change requires new decision (underwriter)

Goal: Income increased; offers must refresh.

1. Financial Information → Edit → update Annual Income.
2. Update → Re-Run Application flow → Apply changes.
3. If Flow changed, pick notify template → Send update.
4. Check Underwriting and Offers tabs after completion.

3. Applicant skipped a step (manager)

Goal: Force redo of identity section.

1. Open correct co-borrower session if multi-applicant.
2. Applicant Information → Edit → Revert to this step.
3. Select notify template → Revert.

4. Read-only review (auditor)

Goal: Confirm submitted values for exam.

1. Open Application tab (no Edit buttons).
2. Expand sections; use variable tooltips as needed.
3. Cross-check Overview Status and Outcome.

---

Relationship to toolbar Update Status

Tool	Scope
Application tab edits	Individual variables in configured sections
Update Status (toolbar)	Workflow actions (Approve, Decline, Doc Requested, etc.)

You may do both on the same visit: e.g. correct income on Application tab, then Update Status → Approve in the header.

---

Troubleshooting

I do not see Edit on any section.
allow_edit is false for this application stage or your role.

Update is disabled or shows no changes.
Only dirty fields count; re-enter the value or change a different field.

Re-run stuck on Processing.
Wait for timeout (~10s) or refresh detail; check Activity tab for engine runs.

Section empty.
Product may not map variables to that section for this stage; check Data tab or underwriting for raw values.

---

Related links

• Application detail
• Overview and header
• Assigning and tags
• Rules and outcomes