FAF requests

Choose the FAF requester by department

Load/select requestors after choosing a department.

Audience: Purchasing staffPermission: purchase_faf capabilityModule v1.7.9

Exact navigationAdmin Area → Purchase → FAF Request → New/Edit → Department/Requester

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

Load/select requestors after choosing a department. 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 → New/Edit → Department/Requester.
Open the exact setting, option or record named in this guide.
Enter or select the required value; leave unrelated options unchanged.
Save the form and wait for the success response.
Reload the page or open a controlled record to confirm the stored value is being used.

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.

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.

Expected result and verification

The supported choose the faf requester by department 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.