Add a general Purchase note
Create a note against a supported purchase record.
Exact navigationAdmin Area → Purchase → open record → Notes → Add
Before you begin
- Use an account with Capability of the related Purchase record 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
Create a note against a supported purchase record. 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 → open record → Notes → Add.
- Choose the New, Add, Create or Start action exposed on that screen.
- Complete the required fields described below and review any linked record, currency, tax, approval or recipient selection.
- Save or submit the form once; correct any validation message rather than bypassing it.
- Open the resulting record and verify its number, status, totals, files, activity and downstream links.
Fields, choices and supported possibilities
ActionAdd a general Purchase note
Exact navigationAdmin Area → Purchase → open record → Notes → Add
Module version1.7.9
VerificationConfirm the saved record, status, output or setting in the same workspace and review any linked activity, file or notification.
Code-backed validations and workflow rules
- The action is available only when the module, current record state and required capability allow it.
- Use the displayed validation response to correct the record; do not bypass controller or model checks.
- Verify downstream files, notifications, linked records and status changes after saving.
Expected result and verification
- The supported add a general purchase note 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.