Administration#
The Command Hub is the single entry point for administrators. This page tours it, then covers signature settings, error logs, the PDF rendering release update, custom fields, languages and security.
The Command Hub#
App Launcher → Welisa DocGen. Tabs:
- Your Templates / Create New — create, edit, version, clone, export and import templates; the Copy-Paste Tags tab inside a template lists every field, loop, aggregate and image tag for its object as ready-to-copy pills.
- Bulk Generation — mass-generate against a SOQL filter or saved query; Job History shows every job.
- Signature Settings — the public site URL, the sender address, link expiration, reminders, signer-verification defaults, Hide Decline, and the setup checklist.
- Assets — the central image library; reference any asset from any template with
{%asset:key}. - Email Templates — the seven signature-flow e-mails, per brand.
- Brands — reusable sender identities a template points at through its Sending Brand field.
- Buttons — build record-page one-click buttons (visible only to Welisa Button Manager + Customize Application).
- Learning Center — links to Welisa.
The app's navigation also carries the object tabs — Templates, Jobs, Signature Requests, Signers, Signature Audits, Error Logs — and the Welisa Licence and Welisa Envelopes tabs for users holding Welisa Signing.
Signature Settings#
Covers: Site URL; the org-wide Send Emails From address (a template's Sending Brand can override it per brand); signing-link expiration default in days; reminder enable + hour schedule; Require Email Verification and Pre-fill Signer Email defaults; Hide Decline Button; and the setup validation checklist with pass/fail per prerequisite. E-mail wording, colours and logos live on the Email Templates tab; sender identities on the Brands tab. Setup steps: E-signature setup.
Error logs#
The Welisa Error Logs tab lists DocGen_Error_Log__c records: non-sensitive exception details captured automatically when generation, bulk jobs or signature processing hit an error, with the failing context (operation, template, job). Start here whenever someone reports "it didn't work" — most failures leave a row that beats guessing. Silent degradations (a logo that could not be loaded, a chart that came back empty) are logged too.
sf data query -o <org> -q "SELECT CreatedDate, welisa__Operation__c, welisa__Context__c, welisa__Message__c FROM welisa__DocGen_Error_Log__c ORDER BY CreatedDate DESC LIMIT 5"The PDF rendering release update#
Mandatory for PDF output: Setup → Release Updates → "Use the Visualforce PDF Rendering Service for Blob.toPdf() Invocations" → Get Started → Enable. Without it PDFs do not resolve relative image URLs and some orgs show raw CSS at the top of generated PDFs.
The page is easy to misread: a greyed-out Enable Test Run button means the update is not enabled; when it is, the button reads Disable Test Run. If you cannot enable it from Setup, open a Salesforce Support case for the affected org. Suggested wording:
Please enable the "Use the Visualforce PDF Rendering Service for Blob.toPdf() Invocations" release update in this org. We generate PDFs with a managed package that calls
Blob.toPdf(). The Release Updates page still shows "Enable Test Run", and generated PDFs render raw CSS at the top of the document.
Custom fields on package objects#
You can extend Welisa Template, Welisa Signature Request, Welisa Signer or any other package object with your own fields. Grant field-level security on every permission set whose users need them (Welisa Admin, Welisa User, Welisa Guest Signature) in the same change.
Languages#
The document runner's interface is translated into ten languages — Dutch, German, French, Spanish, Italian, Brazilian Portuguese, Japanese, Korean, Simplified and Traditional Chinese — and each user sees their own Salesforce language automatically. The Command Hub and bulk runner are in English.
Scheduled jobs#
| Job | Purpose |
|---|---|
| Welisa Licence Check (nightly) | Re-checks the org's licence with Welisa |
| DocGen Signature Reminders (hourly) | Sends due signature reminders when reminders are enabled |
| DocGen Chart CV Reaper (daily) | Removes transient chart files left by interrupted generations |
Security#
- Your data stays in your org. Generation, rendering, charts and signing are native Apex and Lightning; the package makes no outbound call except the nightly licence check, which carries the org's identity only.
- Object and field access are enforced by the permission sets (platform-enforced). Standard-object reads run in user mode; admin-context classes run with sharing.
- Signing guest access uses a 64-character SHA-256 token per signer (48-hour default expiry, 1–365 days configurable), an optional 6-digit PIN (SHA-256 hashed, 10-minute expiry, 3 attempts), explicit consent with an audit entry, a SHA-256 hash of the final PDF, field history tracking on audit fields, and server-side IP capture. The guest user is never granted create, update or delete on package objects.
- Bundled JavaScript (PDF.js, pdf-lib, Chart.js) is vendored as static resources and contains no network calls.
- Found a vulnerability or need a vendor security questionnaire completed? Contact Welisa at [email protected].
Where consultants go next#
- E-signature setup — the one-time signing configuration.
- Upgrading — moving an org to a newer version safely.
- Troubleshooting — symptom to fix.