Allow uploaded e-signatures for approval
Enable approval signatures to be supplied as uploaded files where the views support it.
Exact navigationAdmin Area → Purchase → Settings → Purchase Options
Before you begin
- Use an account with purchase_settings: Edit 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
Enable approval signatures to be supplied as uploaded files where the views support it. 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 → Settings → Purchase Options.
- 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
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
- Save through the module settings form and test with a controlled transaction.
- Do not change unrelated purchase options during a scoped configuration update.
- 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 allow uploaded e-signatures for 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.