Release notes - Create

October 21, 2026 (Build: 20261020.2)

The October release is the biggest Create update yet. Branding, sender details, and reusable data are now managed in one place instead of template by template. Routines add calculated values and rules-driven documents without code, and templates can carry appendices and ready-made files for download. Together with accessibility improvements and faster loading, this makes Create a more flexible, scalable platform for document generation.

New features and improvements

WCAG 2.1 AA UI
Create’s user interface now meets WCAG 2.1 AA requirements, with improved color contrast, keyboard navigation and support for assistive technologies across key workflows.

Profiles
Users can create multiple Profiles with sender details such as name, title, department, and contact information, then select the appropriate profile when generating a document. Profile data can be entered manually or populated from the organization’s identity provider, reducing template duplication and repeated data entry.

Link to end-user documentation: Profiles

Dynamic Themes & Styles
Dynamic Themes & Styles lets template builders manage branding variations within a single theme. Logos, office information, graphics and other visual assets change automatically based on context, reducing the need to maintain separate themes for each municipality, department, subsidiary or brand.

Link to end-user documentation: Dynamic Themes and Styles

Data Sources
Data Sources store reusable lookup data in typed columns, such as text, numbers, dates, elements or images. When a template builder connects a Select node to a data source, the columns become child nodes and the selected row supplies their values to the document. The nodes stay aligned with the data source when the template is opened and can be updated immediately by syncing the Select node. Data Sources can also be used in a theme’s information tree.

Link to end-user documentation: Data Sources

Calculations and conditions with Routines
Routines calculate values in the information tree. Template builders compose them on a visual canvas from cards for input, conditions, maths, text and date operations, and output. Routines run everywhere a document is produced: the preview in Admin, the form in Create, and generation through the API.

Link to end-user documentation: Routines

Download and distribute content with Files
Create can now store and distribute ready-made .pptx, .docx, .pdf and .xlsx files alongside templates. Users can download centrally maintained files exactly as uploaded, without entering data, completing forms or generating a personalized document.

Link to end-user documentation: Files

Add appendices to templates
Templates can include ready-made .docx and .PDF appendices of up to 50 MB from the Files content source, such as terms and conditions or a privacy policy. Template builders add them with the paperclip in the template editor and set their order.

Link to end-user documentation: Appendices

Integrations update: dedicated integration pages
Creating or editing an integration now opens a full page instead of a dialog, with a description of the service, labels for what the integration can do, and copyable addresses for the systems that call it.

KMD Nexus integration
Case workers can start a letter in KMD Nexus, fill it out and generate it in Create, finish it in Word through EditFlow, and send it back to the letter in Nexus as a draft or as a final PDF. If the letter already has a draft in Nexus, the draft opens in Word directly.

API improvements

• Document generation requests now send their data in data.
  • Both the immediate and the queued generate requests now use data, like the rest of the API. Requests that still send values keep working.
• The data can now choose the theme of a dynamic template.
  • Add "$config": {"theme": { "themeId": "<id>" }} to the data, or produce it in the template's dataset transformation. It overrides the theme in the request, and the editor preview and the Create app follow it.
  • outputType switches between the theme's Word and HTML file, and unitId uses a theme from another unit the caller has access to.
• In dynamic templates, $config is now reserved for configuration.
• Sender details can be sent with the request.
  • Add "$config": {"senderProfile": { "values": { "<field key>": "<value>" } }} to the data. Details from the user’s sign-in take precedence.
  • If a key does not exist in the sender form, or a required detail is missing, the request is refused with an error that names it.
• Routines run during API generation.
  • If a routine cannot calculate its value, the generate request is refused and the error names the routine.
• Appendices are included in API generation.
  • PDF appendices are placed before the attachments sent with the request.
• The editing buttons in EditFlow can now be hidden or disabled.
  • showUiActions now hides the editing buttons that are not in the list; before, they were only greyed out. The new disableUiActions keeps a button on screen but greyed out.
  • Both settings also work when EditFlow is opened from another system’s window.
• Changes to how the information tree reads the data.
  • A Select node with multiple selection turned off now uses only the first value it receives, the same as the form. Before, the API accepted several values.
  • A reference to another template that cannot be found now returns an error that names the node, like other information tree errors.
  • Field keys can no longer contain spaces or the characters [ ] / \ " . $. Keys generated from a field’s name leave them out.

Smaller improvements

• Templates: nested content (repeat rows, select options) can now use nodes from the levels above it, for example the customer's name in every row of a repeat. Nodes that can't be used where you're editing show a disabled insert button with the reason as a tooltip.
• Elements: A new option is added to the Element node providing the user with a free or scoped selection of which element to insert from a content source.
• Information tree update: Read-only, hidden or editable are new selections available on nodes and sections. Hidden fields are not shown in the form, but their values still go into the document.
• Office add-in: users can create documents, insert phrases and use files directly from Word, PowerPoint, Excel and Outlook, and switch between organizations in the add-in.
• Performance: Admin and Create load faster; the applications are downloaded in a compressed form when the browser supports it.
• Templates used inside other templates, such as phrases, now run their own data transformation first. A phrase can reshape the data it receives wherever it is used.
• Turn on Store form data in document on a template to save the answers from the form inside the generated Word document.
• EditFlow now accepts Office file uploads of up to 500 MB; large files no longer fail to upload.

Bug fixes

• Required fields inside a repeat or table no longer block the form and API generation when every row is filled out.
• Required fields inside dropdown options that were not selected no longer block generation.
• Pressing Enter at the end of a heading now starts a normal paragraph instead of keeping the heading style.
• Bold, italic and link formatting is preserved in Word output when text is wrapped in a styled span.
• Nested list items keep their level in Word output when the list uses a single style.
• Line breaks in field descriptions no longer disappear in the form.
• Buttons below the preview in Admin are no longer cut off when their labels are long, for example in Danish.
• Code editors now follow the light or dark mode chosen by the user.
• Create and Admin now load for organizations whose web address starts with create or admin.
• PowerPoint no longer asks to repair created presentations when the template had very high slide numbers inside the file and many slides were added.
• Save in EditFlow no longer gets stuck without a message when the document has been open for a while without activity.

September 10, 2026 (Build: 20260909.7)

This release adds two organization settings for customers whose data processing agreement limits what may be stored about their users.

New features and improvements

• Added the "Only store claims in token" organization setting.

  • Claims from the identity provider are no longer stored in Create. They travel with the user's session and are read at the moment a document is generated.
  • Claims components, roles auto assignment, and the claim columns of the User Identities data source are not available in organizations with this setting.

• Added the "Anonymous users" organization setting.

  • Users are stored and shown as Anonymous (email) instead of the display name from the identity provider.

• A display name is no longer required from the identity provider.

  • Users signing in without a display name are shown as anonymous.

Both settings are chosen when the organization is created and cannot be changed later.

September 2, 2026 (Build: 20260902.1)

This release completes the transition to Word style names, adds an interactive API reference, and brings the platform onto a common observability and framework baseline.

New features and improvements

• Completed the transition to Word style names.

  • This means a template authored with English style names now aligns correctly with documents created in a localized version of Word.

• Added organization type selection when creating an organization.

  • The organization type is now chosen from a dropdown: Default (Create), Operator (Create), or Create Classic.
  • New organizations use the new Create experience by default. Select Create Classic explicitly if the organization should use the Classic experience.
  • An organization on the new Create experience no longer has to be an operator, so a customer organization that is not meant to manage other organizations can now be created directly.

• Added OpenTelemetry support.

  • Create and the document engines now export traces, metrics, and logs through OpenTelemetry, alongside the existing Application Insights support.
  • This makes it possible to run Create with standard observability tooling outside Azure.

• Updated the platform to .NET 10 across all engines.

  • The Word, PowerPoint, Excel, HTML, and transformation engines are now aligned on the same long-term supported framework as Create.

API improvements

• Added an interactive API reference.
  • A browsable API reference is available at /openapi, where you can explore all documented endpoints, inspect request and response schemas, and try requests directly against your environment.

Bug fixes

• Fixed multi-line text not being rendered correctly in HTML output — line breaks in a text field now produce paragraphs or line breaks depending on context.
• Fixed alternative text on images not being encoded in HTML output, which could break the surrounding markup when the text contained characters such as > or ".

August 20, 2026 (Build: 20260820.11)

This release introduces image support in dynamic templates, a new interactive API reference, and continued accessibility improvements.

New features and improvements

• Added the Image node to the information tree.

  • A new Image node lets a document include an image provided when filling out the form or through an integration.
  • Images can be sized by fixed width or fixed height, with the other dimension adjusting automatically to keep the aspect ratio, or kept at their original size.
  • Alternative text is supported for accessibility.

• Added image insertion in the editor.

  • Images can now be inserted directly into dynamic templates from the editor toolbar, browsing the images available in your content sources.
  • Inserted images can be resized by dragging the edges or by entering exact dimensions.

• Introduced the Images content source.

  • Images are managed in a dedicated content source type, including alternative texts that are applied automatically when generating documents.

• Added last item separator for Select and Repeat fields.

  • In addition to the existing separator, a separate separator can now be configured between the last two items — for example Alice, Bob and Charlie.
  • The separators can be defined as a default configuration on the node or directly on the inserted field.

• Improved accessibility (WCAG).

  • Icon buttons and custom clickable controls now expose accessible names, roles, and states to assistive technologies across the applications.
  • Settings controls are now associated with their visible labels, and the rich text editor announces itself as a labeled text box.

• Improved organization management for operators.

  • The subdomain field now shows the full resulting URL when creating or updating an organization.
  • Organizations created by an operator automatically include the operator suffix in their subdomain.
  • Renamed "Invite user" to "Add user" for clarity.

API improvements

• Added endpoints for organizations and units.

  • New endpoints return organizations, the units in an organization, and the sub-organizations of an operator:
    • GET /api/v1/organizations
    • GET /api/v1/organizations/{organizationId}/units
    • GET /api/v1/operator/{operatorId}/organizations

• Made the offline_access scope optional for OIDC.

  • When configuring an OIDC identity provider, the offline_access scope can now be disabled. It remains enabled by default for backwards compatibility.

Bug fixes

• Fixed table column resizing misbehaving in the dynamic template editor after switching between editors.
• Fixed the back arrow on the generation page clearing the generation context, affecting prepared generation flows.

July 30, 2026 (Build: 20260730.7)

This release focused on design consistency and storage stability.

New features and improvements

• Completed the transition to the updated design system.
  • Legacy styling has been replaced with the updated design system across the applications, improving visual consistency and WCAG compliance.

Bug fixes

• Fixed an issue that could cause duplicate file id errors in units using GridFS file storage.

July 23, 2026 (Build: 20260723.3)

This release includes the dataset authoring experience in the dynamic template editor, new field configuration options, and a platform upgrade.

New features and improvements

• Introduced dataset authoring in the dynamic template editor (initial release).

  • A dynamic template can now hold a dataset: sample data (JSON) is run through a transformation into a result that can be previewed directly in the editor.
  • Nodes can be dragged from the dataset result into the information tree, and information tree nodes can be converted between types.

• Added separator options to Select fields.

  • Select fields with multiple selection enabled can now be configured with a separator between the inserted items.
  • The separator can be defined as a default configuration on the node or directly on the inserted field.

• Added current date as a default value for Date nodes.

  • Date nodes can now use the current date as their default value, so the field is pre-filled when the form opens or the document is generated.

• Updated the platform to .NET 10.

  • The underlying platform has been upgraded, keeping Create current with the latest long-term supported framework.

• Themes now update their last modified time when the underlying template file changes.

• Adjusted neutral color tokens for WCAG compliance in light mode.

API improvements

• Increased the document generation timeout to 5 minutes for large documents.
• A legacy endpoint now correctly returns 403 Forbidden instead of 500 when access is denied.

Bug fixes

• Fixed hidden theme content sources being shown in the theme selector in the end-user application.
• Fixed the publish changes overview failing to load in some cases.
• Fixed field labels not including their parent group names.
• Fixed element fields not rendering their references when no data was provided, particularly when using multiple data providers.
• Fixed changing the identity provider type on an existing organization.
• Fixed the upload status not being shown when drag-and-dropping files into the upload dialog.
• Fixed text color changes in one table cell unintentionally removing colors from sibling cells.
• Fixed backup restore failing for units using GridFS file storage.

June 9, 2026 (Build: 20260609.4)

New features and improvements

• Introduced Datasets (initial release).
• Added text color support in the rich text editor, applied through to Word output.
• Added separator support for Select fields in HTML output.
• Continued the transition to style names for improved Word compatibility.
• Broadened formatting-element support in Word output.
• Updated layout adjustment rules in HTML output.
• Improved breadcrumb display for long content paths.

API improvements

• Added support for filtering by tags via a query parameter.

Bug fixes

• Fixed pre-filling of Select fields (used for visibility) from data providers.
• Fixed populating table, repeat, select and element nodes from multiple data providers.
• Fixed user-identity Select fields when an identifier field name is used.
• Improved error handling when parsing values.
• Fixed a sizing issue with two consecutive tables in Word output.
• Fixed an unintended paragraph being inserted before a table in HTML output.

May 12, 2026 (Build: 20260511.7)

This release includes enhancements focused on the new Create experience, integration capabilities, document styling, and overall stability.

New features and improvements

• Updated Create front-end.

  • The /create application now includes a dedicated layout focused on the functionality relevant for new experience.
  • A new Contents page has been added, replacing the previous documents overview.
  • A new Recents page has been added, allowing users to quickly return to recently viewed recipes.
  • Users with two or more recent items are now automatically taken to the Recents page when opening the application.
  • A dedicated Search page has been added, allowing users to search across the entire unit with support for search queries and tag filtering.

• Added Favorites in Create.

  • Users can now mark content as favorites in Create.
  • This makes it easier to quickly access important or frequently used items.

• Removed time picker from date node default value.

  • The time picker has been removed from the date node default value configuration.
  • This aligns the default value behavior with the active date flow.

• Improved default styling for lists.

  • Numbered lists now use the correct default numbering styles, and bulleted lists use the correct default bullet styles.
  • This improves consistency and predictability in generated documents.

• Started transition from style IDs to style names.

  • The engine now begins using style names as the foundation for style handling.
  • This improves compatibility with templates authored in different language versions of Word.

API improvements

• Improved AppFlow document delivery with metadata

  • The AppFlow integration now supports sending form metadata back with the generated document.

• Added webhook support for prepare flows.

  • Webhook handling has been added for the legacy prepare flow.
  • MIME type support has also been added to both regular and legacy prepare flows.
  • This improves compatibility in scenarios where generated documents should be returned through webhook instead of being downloaded directly.

• Expanded webhook success message metadata.

  • Webhook success messages now include a metadata object.
  • The metadata contains generation data and the recipe ID of the generated recipe.
  • This provides downstream integrations with more useful context.

Bug fixes

• Fixed cloning issue affecting information tree bindings.

  • Resolved an issue where cloning a recipe could detach information tree nodes from their corresponding bindings.

• Fixed query parameters disappearing during navigation.

  • Resolved an issue in the user front-end pages where query parameters could be lost during navigation in some cases.

• Fixed table overflow for fixed-width columns.

  • Resolved an issue where tables with large fixed column sizes could overflow the page width in LibreOffice and PDF output.

• Fixed list numbering restart behavior.

  • Resolved an issue where numbered lists were not always restarted correctly, resulting in incorrect ordering in some generated documents.

• Fixed nested table conversion issues.

  • Resolved issues causing nested tables to produce invalid documents or incorrect sizing behavior.
  • This improves both document correctness and visual consistency.

• Fixed table size unit handling in conversion.

  • Table conversion now correctly interprets size units such as px, pt, cm, in, and mm.
  • This improves consistency between the editor preview and the generated Word document.

• Fixed disappearing whitespace in rich text conversion.

  • Resolved an issue where whitespace between adjacent links could be lost during HTML-to-DOCX conversion.

March 26, 2026 (Build: 20260325.6)

This release includes enhancements focused on editor usability, performance, and the administrative experience.

New features and improvements

• Added hyperlink support in the editor.

  • Users can now add hyperlinks directly to selected text in the editor.
  • This makes it easier to create richer documents without leaving the editing flow.

• Improved web application load time.

  • This release includes the first round of performance optimizations in the web application, resulting in a noticeable improvement in load time.
  • Additional optimizations are planned for the upcoming sprint.

• Improved information tree behavior.

  • Fields are now automatically removed from the editor when the corresponding information tree node is deleted.
  • Double-clicking a regular field now reveals its position in the information tree.
  • This makes it easier for administrators to manage fields and understand how they relate to the structure.

• Added support for default node configuration.

  • Formatting can now be defined either on fields placed under a table or repeater node, or directly on the inserted field itself.
  • This provides greater flexibility in how formatting is configured and maintained.

API improvements

• Improved core API error handling.
  • Error responses are now clearer and more actionable, making integrations easier to troubleshoot.

March 4, 2026 (Build: 20260304.2)

In this sprint, we introduced a major release of Create focused on Independent Software Vendors (ISVs). The release introduces the foundation of our ISV platform, including a dedicated ISV environment and new capabilities for template management, branding, accessibility, and integrations. Customers interested in this experience should contact their Omnidocs representative for more information.

New features and improvements

• Introduced the foundation for a new ISV platform in Create.
  • This release includes a dedicated ISV environment for software vendors that want to integrate document generation into their workflow and case management solutions.
• Added a new browser-based Dynamic Template Editor.
  • Template builders can now create and manage templates directly in the browser.
  • The editor supports HTML and .docx themes, reusable elements, and repeating structures for more flexible template creation.
• Added full Dutch and German localization for the Create user interface.
  • This improves usability for customers and partners in key ISV markets.
• Introduced Operator-based organization management.
  • ISV administrators can now create, manage, and delete customer organizations with greater independence and control.
• Added support for shared templates.
  • ISVs can centrally manage and publish templates across customer organizations, while still allowing end customers to apply their own branding where relevant.
• Added white labelling capabilities.
  • ISVs can tailor the Create experience with their own logos, styling, and communication elements, making it a more seamless extension of their own solution.
• Expanded authentication and API integration capabilities.
  • This includes support for OIDC, OAuth 2.0, API Secrets, and a new token endpoint to support a wider range of integration scenarios.
• Added support for asynchronous document generation with webhooks.
  • Create now supports both synchronous and asynchronous integration patterns, including callback notifications for completed or failed document generation jobs.
• Added a new Template Preparation Flow for server-side orchestration.
  • This enables guided document generation flows through API-based preparation and browser-based finalization.