Savvy DocuGen updates every Salesforce admin should know

Savvy DocuGen updates every admin should know

If you run document generation and e-signatures in your org, small platform details cause the biggest failures: the signature PDF files land in the wrong place, anchor tags move when a 60-page agreement repaginates, or a renewal batch of 200 contracts stalls because child records didn't merge. This post walks through the specific Savvy DocuGen updates and settings to check so your templates, signature runs and file storage work first time.

Salesforce e-signature: signature identity, anchor tags and signed PDFs

Signature runs in Savvy DocuGen use your customer’s Circularo account, and the signed PDF is written back to the same Salesforce record. That means two things you must configure deliberately:

Signer identity options. You can require an emailed one-time code, and you can also require a per-signer password that you read from a field on the signer’s Contact or User record. Make sure the password field is populated before you send. Example field: Contact.Signer_Password__c.
Anchor tags for placement. Signature positions use anchor tags, so they survive repagination. Don’t switch to fixed coordinates for long, variable-length documents. If you’ve got a 60-page services agreement or terms that expand, use anchor tags in the Word template so signatures land on the right line after a merge.

Practical scenario

Say you send 200 renewals a month and each renewal is a bundle of three templates: a summary, the order form and the T&C. If you used fixed coordinates you’d have to check every page size and margin. Using anchor tags means one template works whether the price table is two rows or twenty.

Savvy DocuGen updates: file storage, size limits and sandboxes

File storage behaviour is one of the common surprises. Savvy DocuGen can file the finished document on the record in Salesforce Files or Notes and Attachments, per template. But Salesforce’s Notes and Attachments has a hard 25 MB limit—Files accepts up to 40 MB from the connector. Pick Files for large signed PDFs or bundles.

If a template bundle totals more than 25 MB you must select Files on the template. Notes and Attachments cannot be raised to accept bigger files.
Sandboxes work exactly as production does. Test signature flows, anchor tags and Files vs Notes choices in a sandbox first; you won’t see a behaviour change after deployment.
There’s no managed package to install. The connector works through an authorised connection, so there’s no package that your security team needs to review or update in the future.

Templates and data: lookups, child records and repeating tables

Savvy DocuGen fills Word and PDF templates from any Salesforce record, standard or custom. Important things to check when you build templates:

Parent lookups: the connector reaches five levels of parent lookups. If your pricing clause needs fields from Opportunity > Account > Parent Account > Corporate Group > Region, that path can be populated. Map your merge fields to the right object API names.
Child and grandchild records as repeating table rows: use the child-record repeating table rows for line items on Quote or a custom object like Subscription__c. If your agreement pulls in product detail and discount lines, test with a record that has many rows so page breaks and anchor tags behave as expected.
Bundling: you can merge several templates into one signature run. Use bundles when your process needs a cover, order form and signature page combined into a single PDF for the signer.

Template checklist

Confirm parent lookup fields exist for the primary record you’ll send from (Opportunity, Contract, Quote, Account, Contact or custom __c).
Test repeating tables with a record that has many child rows to check pagination.
Use anchor tags for signature positions so repagination won’t move them.

Triggers, automation and real-world triggers

Savvy DocuGen triggers are flexible and made for admin-friendly automation. You can launch generation from a button, a stage change, a field change, or when a new file is attached. Choose the trigger that fits your process:

Button: use for ad-hoc sends from an Opportunity or Contract page. Good for sales reps who review the draft first.
Stage change: use when you want the send to happen automatically when Opportunity.StageName hits a specific value like Closed Won.
Field change: useful for checks like Ready_for_Signature__c toggled by a Flow or integration.
New file: useful if an external system drops a PDF on the record and you need to bundle and send that document for signature.

Example: reduce a four-day signature chase

Automate the send on Opportunity stage change, require emailed one-time codes for signer identity, and file the signed PDF back to the Opportunity as a File. That removes manual handoffs and avoids the common mistake where signed PDFs are lost in an agent’s personal email. The result: fewer manual reminders, and a single signed PDF filed on the Opportunity record.

Final checks before you roll out

Test in a sandbox exactly as production - sign a document, check the signed PDF writes back, and confirm anchor tags hold across repagination.
Decide Files vs Notes and Attachments per template based on file size.
Populate any signer password fields on your Contacts or Users before doing a live send if you require per-signer passwords.
Bundle templates when you need one PDF for the signer; otherwise keep templates single-purpose for easier maintenance.

Savvy DocuGen fills Word and PDF templates from any Salesforce record, reaches five levels of parent lookups, supports child and grandchild repeating tables, files documents on the record in Files or Notes and Attachments, and sends for signature through your Circularo account with anchor-tag-based signature placement. Try these checks in your sandbox and you’ll avoid the common rollout issues that cost hours to fix.

Try Savvy DocuGen in your sandbox today.