Update an allocated supplier job
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Change job/supplier/status/amount details through the supported admin action.
- Use an account with Authorised maintenance staff 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 helps you do
Change job/supplier/status/amount details through the supported admin action. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Follow these steps
- Go to Admin Area → Maintenance & Jobs → open job → Edit.
- Go to 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 and options
Rules and limits
- Check supplier portal visibility and invoice state before changing.
- Maintenance hub visibility is tied to customer-view access in the registered menu.
- Supplier completion can create a Pending supplier invoice when one does not already exist.
- Verify linked CRM invoice/payment records before changing a real-estate payment or payout status.
- The module hooks after_payment_added to write property-related activity when the payment is linked.
Check it worked
- The supported update an allocated supplier job 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.
