UnqorkAI 9.0.0 Release Notes

Version 9.0.0 is the general availability of UnqorkAI, including the new AI features, Smart Components, an enhanced Creator experience, Bring Your Own Component, and Embedded UI. All existing platform capabilities — module configuration, services, application management, versioning, and administration — carry forward without any migration required.

AI-powered capabilities require a separate agreement. This includes the UnqorkAI Build Agent, Smart Components, and Agentic Smart Components like the Chat Agent Smart Component and AI Summarizer. Creators whose organizations have not yet activated AI capabilities have access to the improved Creator experience, Bring Your Own Component, Embedded UI, and all existing build capabilities: module configuration, services, application management, and administration. To learn more, contact an Unqork representative.

Updated Designer Experience

Version 9.0.0 introduces a significantly enhanced Unqork Designer: a rebuilt interface with major upgrades to the tools Creators use most. The Designer's UI has been unified end to end, from the workspace to the canvas. Everything behaves consistently and sits where Creators expect it. This release puts meaningful investment into the parts Creators spend the most time in: finding and moving between their work, seeing what a module does, and testing server-side execution.

A unified, streamlined UI. Every surface, from the landing page to the workspace to the canvas to settings, follows the same set of patterns. The Designer feels consistent wherever Creators are working.

A refreshed, more readable look. An updated color palette and a consistent icon set make dense configuration screens easier to scan. A full dark mode is available across the Designer.

Better performance. Load performance is improved across the entire Designer experience, from opening a workspace to switching between modules.

Navigation & Workspace

Moving between work is faster and more direct. This release significantly improves how Creators find, open, and switch between the things they are building.

Global Search. Search carries its own controls, so Creators can filter and target results from the search bar without navigating to a separate screen. It reaches every workspace, application, workflow, module, and administration screen. Inside a workspace, search scopes automatically to the active context. Dismiss the scope pill to expand the search globally.

Workspace Selector. All information about a workspace is available in a single view with tabs. Creators switch between workspaces freely. The Designer saves what was open in each workspace and returns Creators to where they left off.

Explorer Panel. The Explorer panel organizes resources by type in the active workspace: applications, modules, data models, queries, and library elements each appear in their own section. It is accessible from any surface in the platform without leaving the current build context. Modules, data collections, and workflows can be starred from the Explorer panel or their landing pages. Starred items appear in a Favorites section in the workspace switcher for quick access.

Tabs and grouping. Modules, workflows, and data collections open as tabs grouped by application. Tabs can be reordered, pinned, and closed in bulk. Pinned tabs reopen to their last state the next time the workspace is opened.

Module Builder

The Module Builder is where Creators spend the most time. This release adds more ways to see what has been built and fewer interruptions while building it.

Three views of every module. UI View renders the module live, as end-users see it, with logic running and data populating. Logic View maps server-side logic as a navigable node graph. Config View provides the component tree with settings for any selected component. All three are views of the same module; switching between them changes nothing about it.

Component Auto Apply. Configuration changes apply as Creators work. Edit as many components as a change requires, check the result in UI View, and save once when everything is ready. Changed components are marked as work proceeds. The full set can be applied or discarded together from a bar at the bottom of Config View.

Keyboard shortcuts. A comprehensive shortcut set spans the Designer. Every shortcut is remappable, and the shortcuts most relevant to the active context stay visible at the bottom of the screen. For a full reference, see Keyboard Shortcuts.

Undo and redo. Undo and redo now cover the full module component tree, not only the workflow canvas. Undo is context-aware: pressing the keyboard shortcut inside a text field performs field-level undo instead of component-tree undo.

SSE Debugger. The Server-Side Execution Debugger now lives in the Module Builder. Creators can test and debug server-side execution from any module without navigating away, in any environment, with no additional setup. The debugger covers the full platform API surface, not only the Execute endpoint. Running a module execution opens four views alongside the raw response:

• Event Log: every step in execution order, typed (execute, async, data set, trigger, watcher), with the full data payload expandable behind each entry.

• Data Changes: every field the execution touched and the value it was set to, in sequence.

• Timeline: the full execution as a waterfall against a time axis, each step drawn to its real duration.

• Execution Chain: a node graph of what triggered what, with execution counts and total time per component. Remote Execute calls appear in the chain with their own counts and timing.

Transform editor. The transform editor now uses a syntax-highlighted surface with line numbering. Nunjucks expressions and other transform languages are highlighted in the language they are authored in, replacing plain text entry.

Module picker. Every module selection control in the platform searches by module title, module path, or pasted Module ID. Results are sorted alphabetically and load from the server, returning accurate results without loading the full module list.

Server-side execution performance. Module configuration in server-side execution modules now runs in a dedicated worker thread. The main server thread handles other requests in parallel. Long-running operations no longer block concurrent requests.

Module Actions. Creators can copy and paste module definitions, view a module's revision history, and preview the module in a browser. The Module Outline panel provides a searchable, filterable view of the component hierarchy in the active module. Workspace-level actions, including duplicate, move, and share, are available from the module menu.

UnqorkAI Build Agent

Requires AI capabilities agreement. Contact an Unqork representative to learn about activating AI-powered features.

UnqorkAI Build Agent. Creators describe what they want to build in plain language. The build agent generates a structured plan before assembling the module. The plan shows which components and fields it will add, how each will be configured, and which Smart Components it will use. The review step gives Creators full visibility into what gets built before anything is created.

Auto-Test and Auto-Fix. After building, the Build Agent runs the module in UI View and saves a reusable test case. For API modules, the Agent tests using Server-Side Execution. With Auto-Fix enabled, the Agent diagnoses any failures, patches the module, and re-runs until the test passes. Tests accumulate across turns, so later changes are checked against earlier behavior. Both are on by default.

Cross-module builds. The Build Agent reads and edits any module it can resolve from the active workspace, not only the module currently open. When it writes to a module a Creator has not explicitly opened, it asks for confirmation before proceeding.

Rollback. After a turn where the Build Agent makes changes, a checkpoint divider displays in the chat with a Rollback button. Selecting it rewinds to that checkpoint. The rewind covers all turns after that point and every module the Agent touched, including plans and modules created along the way. A confirmation dialog displays before the rollback runs. There is no redo after a rollback.

Agent responses. The Build Agent names the entity it acted on — the application, branch, module, or Smart Component — instead of a raw identifier.

Smart Components

Requires AI capabilities agreement. Contact an Unqork representative to learn about activating AI-powered features.

Smart Components. Smart Components are a rearchitected component model in UnqorkAI. Each Smart Component is a single definition; editing one propagates the change to every module using it on publish. Four types are available: Logic, UI, query, and Agentic. In 9.0.0, the Build Agent creates and modifies Smart Components.

Logic Smart Components. Logic Smart Components handle data processing, calculations, transformations, and conditional operations.

UI Smart Components. UI Smart Components are interface components built in the Smart Component Editor. Public UI Smart Components are available in the component tray and can be placed in any module.

Query Smart Components. Creators describe their data requirements in plain language. The Build Agent creates a Query Smart Component that retrieves the specified . Query Smart Components are the recommended approach for data retrieval in new builds. The /getSubmissions API continues to work for existing applications. Express RBAC controls are available at the query level. For more information, see Query Smart Components.

Agentic Smart Components. Agentic Smart Components provide AI-powered in-app experiences. The Chat Agent Smart Component adds a conversational interface for end-users to query submission data, fill form fields, upload files, and download conversation transcripts. It is configured through the Build Agent, not the component settings panel. The AI Summarizer component condenses submissions, documents, or records into a concise summary written to a designated component in the module.

Smart Component scope. Smart Components are environment-wide, not scoped to individual applications. A public Smart Component is reusable across modules and preferred by the Build Agent where applicable. A private Smart Component is single-use only. Making a component public is permanent.

Review Changes. Smart Component updates no longer block module saves. When a module holds a Smart Component whose published definition has changed, a badge marks the affected component. Creators can review the drift and accept the update when ready. The Review Changes action displays where the component is used and offers Publish Changes or Discard Changes. Previous saved versions are accessible in the History area if a rollback is needed.

Smart Component revisions. Smart Components track previous saves in the History area, which can be used for rollback. Smart Components do not support independent version pinning. The current published definition is always what consuming modules use.

Smart Component and Theme promotion. Smart Components and Themes cannot be promoted through the Release Management Dashboard. To promote them between environments, use the Unqork application directly or the Smart Components Hub.

AI Components for Applications

Requires AI capabilities agreement. Contact an Unqork representative to learn about activating AI-powered features.

Customer-provided LLM credentials. Agentic Smart Components require customer-provided LLM credentials. Unqork does not provide LLM access. Supported vendors: Google Vertex AI, Amazon Bedrock, Microsoft Azure OpenAI, and Anthropic. Register credentials in LLM Credentials Administration before deploying Agentic Smart Components. Each environment must have at least one registered credential for AI features to function. LLM credential and configuration forms are available to all Creators with Designer access.

Markdown component. Renders formatted Markdown text on the module canvas. Use it to display static content or the output of the AI Summarizer component.

Platform

Embedded UI. Modules can now be embedded in external applications as web components or iFrames. This release includes an enhanced developer experience, support for both WebComponent and iFrame embed methods, module-to-module navigation, Unqork workflow integration, and out-of-the-box style compatibility for embedded deployments.

BYO. Creators with Administrator access can promote BYO bundles to upper environments from the Administration dashboard. The Promotions modal displays available target environments and a history of past promotions, including destination, timestamp, and who initiated each. Creators can now test BYO components locally using the new SDK without uploading to Unqork first. This release also introduces BYO Logic Components.

BI Connector End-of-Life. The legacy Connector for Business Intelligence reached end-of-life on September 1, 2026, driven by MongoDB's end-of-life timeline. Environments using the BI Connector must migrate to Snowflake Data Share. Contact a Customer Advocacy Manager to confirm the migration timeline.

Bug Fixes

• API: Resolved an issue where the x-total-count response header returned incorrect values when limit and skip parameters were used together in GET /getSubmissions requests.

• Applications: Resolved an issue where environment production URLs stopped working after migrating from an earlier platform version.

• Audit Logs: Resolved an issue where the Create Workflow  event was not captured in audit logs.

• Audit Logs: Resolved an issue where GET /getSubmissions calls were not captured in audit logs.

• Number component: Resolved an issue where the Number component lost its decimal formatting after navigating away from and returning to a module.

• Services: Resolved an issue where service execution failed when the response payload exceeded 100 MB and response payload logging was enabled.