The problem in two sentences
When an Opportunity needs a 60-page contract, someone still pulls content from multiple records, pastes it into Word, emails it for signatures and then uploads the final PDF back to Salesforce. That manual loop costs time, causes version errors and leaves files scattered across Notes & Attachments or Files.
Salesforce document generation: deeper parent lookups and repeating rows
If your templates hit empty fields because the data lives two or three relationships away, the new parent-lookup depth fixes that. DocuGen now follows up to five levels of parent lookups, so a Quote template can pull fields from Quote > Opportunity > Account > Parent Account > Territory without custom formula fields or extra Flow steps.
Why that matters to you
- You can move logic out of templates and keep a single Word file for a Quote or Contract.
- Less custom work: fewer formula fields and no extra Apex just to get a signer name or a billing address into the template.
- Faster troubleshooting: when a field returns blank, you check record relationships instead of hunting template tags.
Child and grandchild records as repeating table rows
Line-items and schedules now export as repeating table rows coming from child or grandchild objects. That means a 20-row QuoteLineItems list or an installment schedule on a custom object like Payment_Schedule__c can populate a Word table automatically.
The e-signature side got three practical upgrades aimed at reliability and security. Anchor-tag signatures keep signature fields stable across pagination. You no longer need to wrestle with fixed coordinates after the document gains or loses pages.
One-time codes and per-signer passwords
Signer identity can require an emailed one-time code, and you can also require a per-signer password pulled from that signer’s Salesforce Contact or User record. That means the verification step can be automatic and recorded back against the Contact you already use in Salesforce.
Bundles and merged runs
When a single contract package is multiple templates—terms, exhibits, order form—you can bundle them into one signature run. That keeps a legal package together in the signer flow and returns a single merged PDF to the originating record.
Where the signed and generated documents live in Salesforce
DocuGen files the finished document on the record where it was triggered. You can choose Salesforce Files or Notes & Attachments per template. Remember: Notes & Attachments has a 25 MB limit; DocuGen supports documents up to 40 MB, so large PDFs need Files.
Which objects and triggers work
Templates can run from standard objects like Opportunity, Contract, Quote, Account or any custom object. Triggers you can use without code:
- A button on the record page
- A stage change on Opportunity (for example, when Stage = 'Contract Sent')
- A field update (signed checkbox flips true)
- When a new file is attached to the record
Practical scenarios
Scenario 1: Renewals team. If you have 200 renewals a month and every renewal needs a 12-page statement plus a 3-page order form, use a bundled template. DocuGen merges them and sends one signature run instead of three separate emails. That cuts signer confusion and keeps the final PDF together on the related Opportunity.
Scenario 2: Complex billing addresses. Your billing address sits on the parent Account two levels up, and invoice contact data is on a custom object. With five-level parent lookups and repeating rows, your invoice template can pull all fields directly and render line items from Invoice_Line__c.
Scenario 3: Large exhibits. A 60-page exhibit pushes the PDF above Notes & Attachments limits. DocuGen will still create the signed PDF, but you must choose Salesforce Files as the storage target to avoid a failed upload.
Admin tips for a safe rollout
- Test in a sandbox first—DocuGen works in sandboxes exactly like production, so you can validate templates, lookups and signature flows without touching live data.
- Decide per-template storage: pick Files for anything likely to exceed 25 MB or that needs sharing outside Salesforce.
- Use bundles for packages that must stay together. Name bundles clearly so sales users pick the right one from a button menu.
- Set verification to one-time codes or per-signer passwords only where required. Each extra verification step adds friction for signers.
How this affects your existing processes
You won't need a managed package or an install to get these features—DocuGen connects through an authorised connection, so security teams have less to review. Because signature positions use anchor tags, your templates will survive repagination and you should see fewer misaligned signatures. And because it writes the finished PDF back to the originating record, audit trails and file access follow your existing sharing model.
Wrapping up
If your org handles multi-part contracts, deep lookup fields or large exhibits, these updates address the specific pain points that make admins add custom fields, Flows or manual workarounds. DocuGen fills Word and PDF templates from any Salesforce record, follows up to five parent lookups, handles child/grandchild repeating rows, bundles templates into one signature run and writes the signed PDF back to the same record.
Try the new features in your sandbox and validate a full end-to-end run from an Opportunity or Quote record. Ready to test in your sandbox? Try Savvy DocuGen in a sandbox now.
Read next