Multilingual documents and email delivery

Pikbase provides the tenant runtime for template storage, language selection, rendering, PDF generation, attachment assembly, and email execution. The tenant supplies and controls its own delivery provider credentials; Pikbase does not silently send from a shared customer identity.

Application content management

The multilingual infrastructure is not limited to documents. Model application content as ordinary entities and mark localized properties as multilingual. When an application calls setGsbLangCode with the user's selected language, the Core client persists that choice and automatically adds it as variation.langCode on subsequent tenant requests. Entity Service returns the matching language variant, so navigation, catalog content, articles, help text, and other CMS-managed content use the same governed data contract as the rest of the application. A caller can override the language for an individual request when needed.

Multilingual templates

A GsbDocTemplate can store one HTML body or multilingual content keyed by language code, including en_us, tr_tr, de_de, fr_fr, es_es, and other supported variants. Template expressions bind entity, workflow, contact, and parameter data at render time. The renderer selects the language variant from the explicit langCode or the active request/workflow variation.

HTML and PDF generation

Use the document-generation operation to render a selected template as PDF and store the generated file on an entity or workflow instance. The operation supports a target property, generated filename, HTML input, byte-array output, and Puppeteer rendering when the document requires browser-grade layout.

Template email

The email function resolves the recipient language, renders the selected document template, translates the subject, and sends HTML or text content. Email operations support To, Cc, Bcc, Reply-To, priority, distinct delivery, and file attachments.

Generated PDF attachments

In a function or workflow, generate the localized PDF first and pass the resulting file to the following email operation as an attachment. The document and message can use the same language context and entity data, keeping invoices, statements, confirmations, and notices consistent.

Register a delivery provider

Configure SMTP or SES for the tenant with the provider account, sender identity, region/server, port, TLS, and credentials required by that provider. Credentials remain server-side in tenant runtime settings. Pikbase supplies rendering, orchestration, attachment handling, retry-capable SMTP delivery, and execution logs; the provider remains responsible for sender verification, reputation, quotas, and final transport.