Test Dochly After Installation in Salesforce

Updated June 2026 7 min read Getting Started

Before rolling Dochly out to your wider team, run through this structured test sequence to verify every core function is working correctly — document generation, merge field accuracy, document storage, e-signature sending, Flow triggers, and non-admin user access. Each test has a clear pass/fail outcome. Complete all six tests before sharing Dochly with your users. If a test fails, each section links directly to the fix.

Before you test

Have the following ready before starting. The tests use real Salesforce data — dummy records with empty fields will produce misleading results.

Test records needed

One Opportunity with an Account, a Contact (with an email address), and at least 2 Opportunity Products added. This single record covers all 6 tests.

Active template needed

At least one Active Dochly template based on the Opportunity object. If you haven't built one yet, complete Set up your first document template first.

Test user account needed

One non-admin Salesforce user with the Dochly User permission set assigned. Use this account for Test 6. If you don't have one, create a test user in Setup → Users.

Real email address needed

A real email address you can access for Test 4 (e-signature). The test sends a real signature request email — you need to receive and open it to verify it works.

Test 1 — Document generation

Verify that Dochly can generate a document from a Salesforce record and that the process completes without errors.

Generate a document from an Opportunity

Required

1
Open your test Opportunity record in Salesforce
2
Click the Generate Document button on the record (or open the Dochly panel)
3
Select your Active template from the template picker
4
Click Generate and wait for the process to complete

Expected result — Pass

Generation completes without an error message
A PDF file appears in the Opportunity record's Files related list
The file name matches the template name or the Opportunity name

If this test fails

Check the template status is Active, not Draft. Confirm the generating user has the Dochly User permission set assigned. See troubleshooting: document generation failures.

Test 2 — Merge field accuracy

Verify that merge fields in the generated document correctly reflect the values from the Salesforce record — no blanks, no raw field syntax, no "null" text.

Open and review the generated document

Required

1
Download the PDF file generated in Test 1 from the Opportunity's Files section
2
Open the PDF and check every section against the Salesforce record
3
Verify the Account name, Contact name, deal amount, and close date all match exactly
4
Confirm the line items table shows the correct products, quantities, and prices
5
Check that dates appear in readable format (e.g. "June 15, 2026") — not raw date strings

Expected result — Pass

All merge fields show correct values from the Salesforce record
No blank spaces where data should appear
No "{{field}}" raw syntax visible anywhere in the document
No "null" text appearing in any field position
Line items table shows the correct number of rows with accurate data

If this test fails

For blank fields: confirm the field has a value on the record and check the field API name in the template. For raw syntax appearing: the merge field was typed incorrectly — re-insert using the picker. See troubleshooting: merge field errors.

Test 3 — Document storage

Verify that generated documents are correctly stored as Salesforce Files on the originating record and are accessible to the right users.

Verify storage on the Salesforce record

Required

1
On the test Opportunity, scroll to the Files related list
2
Confirm the generated document appears as a Salesforce File
3
Click the file to open it — confirm it opens correctly in the Salesforce file viewer
4
Generate the same document a second time — confirm a second file appears (not overwriting the first)
5
Log in as your test non-admin user and confirm they can see the files on the Opportunity record

Expected result — Pass

Generated documents appear in the record's Files related list immediately after generation
Multiple generations create multiple files — no overwriting of previous versions
Files are accessible to users with record access — not just the generating admin

If this test fails

Check Dochly Settings → Storage — confirm "Attach to originating record" is enabled. Verify the generating user has Create access on ContentDocument in their profile. See troubleshooting: generated document not attached to record.

Test 4 — E-signature sending

Verify that e-signature requests are sent correctly, the signing experience works, and the signed document is stored on the record after completion.

Send and complete a test e-signature request

Required

1
Generate a document from the test Opportunity
2
Click Send for Signature from the Dochly panel on the record
3
Set the signer email to a real email address you can access (use your own email for testing)
4
Click Send — check your email inbox for the signature request
5
Open the email, click the signing link, and complete the signature
6
Return to the Salesforce record and check that the signed document is now in the Files section

Expected result — Pass

Signature request email arrives within 2 minutes
Signing link opens the document for signing without requiring a login or account
After signing, the completed document appears on the Salesforce record
Signature status on the record updates to "Signed" or equivalent

If this test fails

For email not arriving: check the Contact email field on the record and your spam folder. For signed document not storing: check Dochly e-signature settings → "Store completed document on record". See troubleshooting: e-signature errors.

Test 5 — Flow trigger

Verify that document generation can be triggered automatically from a Salesforce Flow. This test requires you to build a simple test Flow — it takes about 5 minutes and confirms your automation foundation is working.

Build a simple test Flow and trigger generation

Recommended

1
Go to Setup → Flows → New Flow → Record-Triggered Flow
2
Set the trigger: Object = Opportunity, Trigger = A record is updated
3
Add a condition: StageName changes to "Closed Won"
4
Add an Action: search for "Dochly" — select the Generate Document action
5
Configure the action: select your Active template, set Record ID to the triggering Opportunity ID
6
Save and activate the Flow
7
On the test Opportunity, change the Stage to "Closed Won" — verify a document is generated automatically

Expected result — Pass

Dochly Generate Document action appears in the Flow action picker
Changing the Opportunity stage triggers automatic document generation
Generated document appears on the record without any manual action

If this test fails

If the Dochly action doesn't appear in the Flow builder, confirm Dochly is correctly connected (Setup → Installed Packages → Dochly → Connected). Check Setup → Flow Error Emails for error details after the trigger fires.

Once you've verified the Flow trigger works, deactivate this test Flow or update it with the correct stage and template for your actual workflow. Don't leave test Flows active in production — they'll trigger on every matching record change.

Test 6 — Non-admin user access

Verify that a regular Salesforce user with the Dochly User permission set can generate documents correctly. Admin users bypass field-level security — this test catches permission issues that only affect non-admin users.

Log in as a non-admin user and generate a document

Required

1
Log in to Salesforce as your test non-admin user (with Dochly User permission set assigned)
2
Open the test Opportunity record
3
Generate a document using the same template used in Tests 1–2
4
Open and review the generated document
5
Compare the output to the admin-generated version — check for any merge fields that are blank for the non-admin user but populated for the admin

Expected result — Pass

Non-admin user can access Dochly in the App Launcher without errors
Document generates successfully without permission errors
All merge fields show the same values as the admin-generated version

If this test fails

If the user can't access Dochly: verify the Dochly User permission set is assigned. If merge fields are blank for the non-admin: a field is restricted by field-level security for their profile — go to Setup → Object Manager → [Object] → Fields → [Field] → Set Field-Level Security and grant Read access.

Reading your test results

Use this summary to decide whether you're ready to roll out Dochly to your wider team:

All 6 tests pass

Dochly is fully functional and ready for org-wide rollout. Proceed to Configure Dochly settings and then assign access to your users.

Tests 1–4 pass, Test 5–6 fail

Core generation works. Fix the Flow configuration or user permissions issues before rolling out — these affect your automation workflows and non-admin users.

Tests 1–3 fail

Core generation is not working. Do not roll out until resolved. Re-check the installation and connection steps, then contact Dochly support if issues persist.

Tests 1, 2, 3, and 6 are required before rollout. Test 4 (e-signature) is required if you plan to use e-signature in your workflows. Test 5 (Flow trigger) is recommended if you plan to use automated generation — it's optional if you'll only use button-click generation initially.

Frequently asked questions

After a template update, run Tests 1 and 2 (generation and merge field accuracy) to verify the updated template produces correct output. You don't need to re-run Tests 3–6 unless you changed storage settings, e-signature configuration, Flow references, or user permissions.

Run all 6 tests in your sandbox first, then run them again in production after installing there. The sandbox and production environments may have different data, field-level security configurations, and user profiles — passing in sandbox doesn't guarantee passing in production without verification.

For Test 4, always use your own email address as the signer — not a customer's Contact email. Update the Contact email on your test record to your own address before sending, then revert it after the test. This prevents test signature requests from accidentally going to real customers.

Test documents are stored as standard Salesforce Files on the Opportunity record. Delete them like any other Salesforce File — click the file in the Files related list, then select Delete. If you're testing in a sandbox, you can also simply not worry about cleaning up — sandbox data doesn't affect production.

All tests passing means Dochly is fully functional in your org. Next step: Configure Dochly settings in Salesforce — set org-wide preferences, email delivery, storage rules, and e-signature configuration before rolling out to your full team.