$ Credential Flow · Object Model
The Loan_Application__cschema, its automated stamping behavior, and the structural parallel to Farpost’s own reputation graph.
## LOAN_APPLICATION__C
| Field | Purpose |
|---|---|
| Applicant | Lookup to the standard Contact object |
| Account | Lookup to the standard Account object |
| Amount Requested | Currency field |
| Status | Picklist — Draft, Submitted, Under Review, Approved, Denied (plus Archived, reachable only by editing Salesforce directly) |
| Submitted Date | Stamped server-side on creation |
| Decision Date | Stamped automatically by a Flow — see below |
## AUTOMATED_DECISION_DATE
Decision Date is never set by manual entry. A Record-Triggered Flow sets it to the current date automatically the moment a record’s Status changes to Approved or Denied, and leaves it untouched for any other Status change — the same real Salesforce Field History Tracking audit trail this integration’s status-change timeline is built from, not a derived or synthetic timeline.
## FARPOST_PARALLEL
The Applicant → Loan Application → Account relationship model here is structurally the same shape as Farpost’s own professional-reputation graph — entities (adjusters, inspectors, contractors, agents, building owners) linked through records that carry status and a decision trail. Both are computed from a real event/history log, not a derived or fabricated summary: Farpost’s reputation is assembled fresh from logged actions on each request, and this integration’s status-change timeline is sourced from Salesforce’s own Loan_Application__History object — the same underlying pattern, a graph of related parties and the records that move between statuses, applied to a different domain.