Skip to main content

Document Generation: Configuration & Output Enhancements

Document Generation gets its biggest set of upgrades yet — twelve enhancements spanning a faster editing experience, smarter templates, and richer data. Import and export to Word, no-code conditional logic, a live template preview, a brand-new Journey Documents data source, journey-aware versioning, journey-level data, support for special-character languages, and much more all land in this release, turning template configuration into a dramatically faster and more capable process from start to finish.

  • Import and export to Word — Templates can now be imported straight from a .docx file and exported back out to Word. Drafting a template in Word — reusing existing branded document templates, styles, and formatting — instead of rebuilding it by hand can dramatically cut template creation time, especially for long or heavily formatted documents. This is a huge quality-of-life win for anyone configuring templates. Full Screen, Print, Download to PDF, and Code View are grouped alongside these in a ⋯ icon in the template editor toolbar.
  • No-code conditional logic — Configurators can mark a text, table, or loop component as hide-when-empty directly in Template Configuration, so blank fields and their surrounding rows or sections no longer need to be hidden with hand-written HTML.
  • Template preview — A Preview button in the Template tab renders the template as HTML using sample data, without running a journey. This saves configurators from having to trigger a journey or a document generation task just to check what a template will look like.
  • Journey Documents data source — Templates can now list the documents uploaded against the main entity during the journey via a new Journey Documents data source, with filtering available on document type, uploader, and upload or update date. A generated report can now reflect everything gathered during that journey.
  • Journey-level data on documents — Data captured at the journey level (not written back to the entity) can now be selected and rendered in a text component, for the main entity and for related parties.
  • Template versioning aligned with the journey — An Enable Versioning toggle on the Document Generation task lets a journey lock to the template version that was current when the journey started, instead of always using the latest version — preventing blank fields when a template is updated mid-journey.
  • Loop Component configuration now included in Configuration Exchange — Loop Component configuration can now be promoted from a lower environment to a higher one (for example, dev to UAT to production) via Configuration Exchange, instead of having to be manually recreated in every environment.
  • Localisation Code now effective — The Localisation Language setting in Template Configuration now applies to generated documents without requiring HTML changes.
  • Special character language rendering — Text in languages with special characters, such as Chinese, Japanese, and Korean — including values sourced from external data providers — now renders correctly in generated documents instead of appearing blank.
  • Higher capacity for large entities — Document Generation now supports a higher number of related parties and related products per entity, with documents generated safely (via a truncation warning) rather than failing when an entity's related data exceeds the supported limit.
  • Empty field placeholder — A Show "-" for empty fields toggle in Template Configuration renders a dash in place of a blank value for text components and table cells, instead of leaving the field empty.
  • Token highlighting, tooltip, and validation warning — Tokens in the template editor are now underlined teal (valid) or red (invalid), with a hover tooltip showing token details. A warning banner lists any tokens that won't render correctly, so mistyped tokens are caught during authoring rather than at document generation.
  • Component Library reliability fix — Republishing a component no longer causes previously-selected components to reappear as "Available"; matching is now based on component content rather than a volatile internal identifier.

User Guide Reference: Document Generation