7.30.0 Platform Release Notes

Release Schedule

Announcement: 2026 Release Schedule

Great news for your planning and testing teams. Based on your valuable feedback, we're excited to announce that Unqork is moving to a quarterly General Availability (GA) release calendar starting in 2026.

This new 12-week cycle replaces the current 6-week model, giving your teams more predictability and time to adopt new capabilities. This change will start with our 8.0 release in Q1 2026. It’s also important to note that critical patch releases will continue to happen weekly.

To learn more, view our 2026 Release Calendar.

Feature: Branch History

Branch History introduces the ability to track changes made to an application when you choose to merge your branches into one another. Additionally, Branch Rollback lets you reset a branch to the state it was in before an event in the Branch History happened.

Branch History provides the following advantages:

• Better understanding of feature development. Track change history between different branches.

• Understanding design decisions. Messaging provided with each merge can clarify what changes were made.

• Auditing and traceability. Clarity on who made what changes and when.

The Branches of Branches feature is currently in closed beta. Please contact your Unqork representative for more details and access.

Feature: Branches of Branches

The Branches of Branches feature extends Unqork’s versioning flexibility by letting Creators create a branch from existing branches, not only from the published versions. This layered branching capability lets teams experiment and iterate in sub-branches before merging them into a parent branch or version.

This feature is similar to nested development, where each branch of a branch represents an independent sandboxed environment that lets you build, test, and refine configuration changes without disrupting the main application.

The Branches of Branches feature is currently in closed beta. Please contact your Unqork representative for more details and access.

Feature: Automatic Dependency Manager

Migrating an unversioned application to a versioned application has previously required you to know which other applications are used as dependencies. Manually setting dependencies in the Dependency Manager can be tedious, as knowing all dependencies requires you to access each module to locate all references to other applications.

The Automatic Dependency Manager navigates through the application and finds all its dependencies and adds them to the Dependency Manager for you.

The Automatic Dependency Manager provides the following advantages:

• Reduces the time required to enable application versioning.

• Increases versioned applications.

• Encourages Creators to implement versioning into their application SDLC.

The Automatic Dependency Manager feature is currently in closed beta. Please contact your Unqork representative for more details and access.

Administration

Enhancements

• Administrator role: Unqork is removing a legacy fallback behavior that would automatically assign the Administrator role to certain execution requests if an explicit role is not defined. This change ensures that all executions operate under the correct and intended user permissions, resolving security inconsistencies and streamlining permissions management.

  In the following cases, the module currently runs as Express Admin. Now, the module runs with Designer Admin permission.

  • If you have a scenario where Module A, with Execute as Super-User, executes Module B without Execute as Super-User, it works as expected.

  • If you have a scenario where a Designer Admin user is executing a module directly from an API, it should run without any issues.

APIs

Enhancements

We are transitioning GraphQL-based services to our Unqork REST API. For those currently using these services, Unqork will contact you with details and instructions. Additionally, parts of the GraphQL schema will begin to show as deprecated, and we recommend leveraging the REST API for any new configurations.

• archiveSchema: The GraphQL resolver archiveSchema has been migrated to the REST API PUT /fbu/uapi/schemas/{schemaId}/archive.

• createSchema: The GraphQL resolver createSchema has been migrated to the REST API POST /fbu/uapi/schemas.

• generateModuleComponents: The GraphQL resolver generateModuleComponents has been migrated to the REST API POST /fbu/uapi/components?type=module.

• getCollections: The GraphQL resolver getCollections has been migrated to the REST API GET /fbu/uapi/workspaces/:workspaceId/:resourceType/submissions.

• getComponnentsFromSpec: The GraphQL resolver getComponentsFromSpec has been migrated to the REST API POST /fbu/uapi/components.

• removeScheme: The GraphQL resolver removeSchema has been migrated to the REST API DELETE /fbu/uapi/schemas/{schemaId}.

• updateSchema: The GraphQL resolver updateSchema has been migrated to the REST API PUT /fbu/uapi/schemas/:schemaId.

Updated the in-product API documentation (/#/apidocs) with details on the following endpoints:

• Delete Module Attachments

• Delete Workflow Attachments

Applications

Enhancements

• Application Versioning: Added an enhancement to the context value used with Application Versioning. Context can now be used in a human-readable format in Express View. For example, context=v1.0.0.

Centauri

Enhancements

• Map V2 Component: Removed the non-functioning Multiple Value Toggle setting from the component settings drawer.

Fixes

• Dynamic Grid component: Fixed an issue where, in certain situations, additional rows could be added by the end-user beyond the configured row limit. Now, if a row limit is configured in the component, additional rows cannot be added, and the Add Row button becomes disabled.

• Dynamic Refresh: Fixed an issue where a Rich Text Editor component inside a Uniform Grid component did not render when dynamically refreshed.

• Navigation component: Fixed an issue where page headers were not translated correctly.

• Number component: Fixed an issue where Number components set to Read Only View would display an incorrect value.

• Rich Text Editor component: Fixed an issue where, in certain situations, the cursor of the Rich Text Editor component returned to the beginning of the field shortly after page load, even if the end-user was entering text beforehand. Now the cursor remains in the location determined by the end-user.

• ViewGrid component: Fixed an issue when the ViewGrid component's column filtering and sorting were used at the same time. If so, the component did not render results correctly.

• ViewGrid component: Fixed an issue where the Source Has Pagination setting did not work when the Accessibility feature for the ViewGrid component was enabled.

Classic Designer

Enhancements

• Visual Query Builder: New Contains (Case Insensitive) and Not Contains (Case Insensitive) operations have been added to the Visual Query Builder to query records without matching exact cases.

Platform Architecture

Fixes

• MongoDB: Updated MongoDB version. This enhancement is a zero-downtime upgrade process that will not require application or environment modification.

UDesigner

Enhancements

• Data Models: Data models can now be deleted from the platform UI, as long as they are not connected to any modules or record queries.

Fixes

• Data Workflow component: Fixed an issue in the Data Workflow canvas where operator setting values did not save if the Creator clicked Save Component immediately after editing an operator.

• Module Builder: Fixed an issue where components with a Property ID of iterator did not render correctly on the Module Builder canvas.

• Server-Side Execution Debugger: Fixed an issue where, in certain situations, the search bar for a response body was not visible.

Vega

Enhancements

• Map V2 component: Removed the non-functioning Multiple Value Toggle setting from the component settings drawer.

• Page Load: Updated the page load spinner behavior in Vega to match Centauri.

Fixes

• Bring Your Own (BYO): Fixed an issue where, if a misconfigured manifest.json asset was uploaded, the Module Builder would not load for a module that has the asset with the misconfigured manifest.json. Now, the Module Builder will correctly load in this scenario.

• Bring Your Own (BYO): Fixed an issue when using Cross Runtime Support (a Vega Panel inside a Centauri module), Error: Runtime does not match errors displayed when previewed in Express View when the Centauri parent module includes Centauri header or footer modules. Now, a Vega Panel with BYO components renders correctly in Centauri modules that have Centauri header and footer modules for an application.

• Chart component: Fixed an issue where Chart Legend colors did not reflect custom hex color codes defined in the color parameter for chart data. The legend now correctly displays the same color as the corresponding bars or columns in the Chart component.

• Logic components: Fixed an issue where formulas pasted into the Output or Formula fields lost their double quotes when the cell was manually activated in edit mode. Now, Creators can paste formulas directly without needing to double-click the cell beforehand.

• Operations Builder: Fixed an issue where the Operation Search feature did not let Creators search by the displayed description.