The approval e-mail carries the document's print

The customer asks: An e-mail at each approval step with the purchase order's PDF attached, and the uploaded CSV

• Verdict: Ready, with limits (4)
• Door: Configure · area: Documents and print › Approvals
• Recipe: Set a shop up with no code
• Sample: none yet
• Checked: run on a sandbox 2026-10-16 · POS 2.0.0.650 · a notification with Attach Print saved (switched off, then deleted); not run: a mail sent

What you build

A notification set up in Desk by the shop's administrator on the approval step, with Attach print ticked and the print format chosen. In Print Settings, Allow Print for Draft must be on: with it off the notification raises an error on a draft or pending document, and as the notification runs inside the document's own save, that can stop the approval step. Nothing is shipped in a manifest: a notification on a shop's own record type is refused there (chapter 7).

Limits

• An uploaded CSV goes as a link in the message: the installed framework has no attach-from-field, and a manifest cannot carry it (it could mail any private file). The link opens with the reader's own rights.
• Allow Print for Draft is a site-wide setting, and a notification that fails (no print, no recipient mail) can hold the document's save: send the first one to a test document.
• A package's own record types will carry a notification with the package's own print format when POS LANE X row X58, P-MANIFEST4 (multi-select, a settings record, notification attachments) merges. The shop's own documents stay configuration.
• Not run: a mail sent with the print attached.

Tell the customer

Each approval step mails the approver the document as a PDF; an uploaded CSV is a link in the same mail.

What next

1. Tell the customer the 4 limits above, and write them into the proposal.
2. Follow the recipe: Set a shop up with no code.
3. Build and test it on your sandbox (request one if you have none; what is on it).
4. Check it on your sandbox as the people who will use it; where it touches a price or a total, the money kit's release gate proves it (testing and release).
5. Make the same settings on the customer's site, from the list you wrote down, through the customer's own change process.

Nothing to code: write down each setting you make on your sandbox, so it is made the same way on the customer's site.

Related needs

• A branch sees the stock of its own store and the head office's, no other — Ready, with limits (4)
• A coded reason when a cashier voids, returns or discounts — Ready, with limits (3)
• Members pay less, by tier — Ready, with limits (5)
• One more detail on a line, for goods with no serial number — Ready, with limits (2)

Start a project shortlist with this need · Put it in your blueprint · Every need

This card in the kit