Request FAF approval
Submit the form to its configured approval route.
Exact navigationAdmin Area → Purchase → FAF Request → open request → Request Approval
Before you begin
- Use an account with purchase_faf capability and confirm the intended record or setting before making a change.
- Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
- Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.
What this guide covers
Submit the form to its configured approval route. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Exact step-by-step process
- Open Admin Area → Purchase → FAF Request → open request → Request Approval.
- Open the source record and verify its recipient, status, totals and attachments.
- Choose the Send, Email, Share or Request action described in the guide.
- Select recipients and attachment/signature options shown by the form.
- Submit once and verify the activity, delivery metadata, public link or approval request created by the module.
Fields, choices and supported possibilities
FAF requestRequester, department, request information, amounts/lines, attachments, approvers and signature evidence exposed by the FAF form.
Decision evidenceApproval status, notes, uploaded/requestor signature and PDF.
Approval setupName, related transaction type, approval type and approver rows/conditions.
DecisionCurrent approver, decision, reason, signature/upload and notification.
Code-backed validations and workflow rules
- FAF access is governed by purchase_faf capabilities.
- Approvers can be selected on the form only when pur_can_select_approvers_on_faf_form is enabled.
- Record access does not automatically grant the dedicated change-status capability.
- The module supports configured approval routes for purchase requests, orders, returns and FAF flows.
Expected result and verification
- The supported request faf approval flow completes without bypassing permission or validation checks.
- The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
- Unexpected validation, provider or linked-record errors are investigated before retrying.
Security, privacy and operational checks
- Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
- Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
- Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
- Test settings and automated jobs with controlled records before production-wide use.