Apex API#

Call Welisa DocGen from your own Apex — triggers, scheduled jobs, service classes, Lightning components. welisa.DocGenService is the global, subscriber-callable API. The package's controller classes (DocGenController, DocGenBulkController) are its own UI endpoints and are not callable from subscriber code; automate through DocGenService or the Flow actions.

Backwards compatibility: the methods below are stable global entry points. New optional overloads may be added; existing signatures are not removed without a major version and a deprecation notice.

welisa.DocGenService — synchronous generation#

// Trigger PDF generation from an approval process
Id contentDocId = welisa.DocGenService.generateDocument(
    'a0zXXXXXXXXXXXXX',   // template Id
    accountId,            // record Id
    'PDF'                 // force PDF regardless of the template's default
);

// Template Id from a Custom Label, so it deploys cleanly
Id invoicePdf = welisa.DocGenService.generateDocument(System.Label.Invoice_Template_Id, invoiceId);

// Render in memory and e-mail without ever creating a File
Map<String, Object> result = welisa.DocGenService.generatePdfBlob(templateId, oppId);
Blob pdf = (Blob) result.get('blob');
String title = (String) result.get('title');

Exceptions. All methods throw welisa.DocGenException on validation failures (locked output format, missing template, PowerPoint → PDF, null data map). Catch it by name: catch (welisa.DocGenException e) { … }.

Sharing and field-level security. DocGenService runs with sharing — record access is enforced for the calling user. Field-level security is not re-checked inside the merge engine; a user with row access but restricted FLS on a referenced field still sees that value in the document. The …FromData overloads bypass the package's SOQL boundary entirely: the calling code is responsible for CRUD/FLS on the values it puts in the map. Gate them in your own code if you expose them to lower-privilege actors.

Flow actions from Apex#

Every invocable action can be called from Apex with Invocable.Action.createCustomAction(…). Full input/output signatures:

The old signers (List<Signer>) input on Create Signature Request is a deprecated inner type Flow cannot populate — always use signerRecords (List<DocGenSigner>). A Flow Apex-Defined variable requires a top-level global class with @AuraEnabled members and a global no-argument constructor, which DocGenSigner provides.

welisa.DocGenDataProvider — custom data source#

Implement this interface to feed a template from an external API, computed values or cross-object aggregations, then bind the template to the class (Data Source → Apex Class). The map's keys match the merge tags; nested maps become parent-lookup tags, lists of maps become loops.

global interface welisa.DocGenDataProvider {
    Map<String, Object> getData(Id recordId);
    List<String> getFieldNames();
}

A complete example and the binding steps are on the Query configuration page.

welisa.DocGenAiProvider — your own AI model#

Implement isAvailable(), getName() and generateHtml(String prompt) to let the designer generate and revise HTML templates through a model your org has access to; register the class in Welisa Settings → AI Provider Class. A provider must not make HTTP callouts from inside generation. Details: Templates.

Objects you may query#

All package objects are readable through the permission sets. The ones automation most often touches, with their welisa__ prefix: