8.0.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.

Administration

• Services Administration: Unqork has enhanced the reliability of external service integrations using the Enable Token Persistence feature by implementing strict, real-time expiration checks. Previously, delays in background database cleanup would occasionally let workflows attempt to use expired tokens. The system now applies a 30-second safety buffer to automatically discard these near-expiration tokens and generate new ones. Doing so ensures seamless and uninterrupted service calls, even under high load.

• Environment Administration: Fixed an issue where the helper text in Environment Administration was inaccurate.

APIs

As part of Unqork’s ongoing migration from GraphQL endpoints to REST endpoints, you’ll find the following updates:

• Implemented a high-performance REST /records/:recordId endpoint for retrieving Data Model, module, and workflow records. This new endpoint offers a faster alternative to the legacy GraphQL getRecord resolver. This update improves API efficiency and removes previous request size limitations while ensuring strict access control.

• Implemented a new REST POST /schemas/data-validation endpoint. The former GraphQL POST /models/validateFromSchema endpoint is marked as deprecated, but will continue to be supported until no more use of this old route remains.

• Implemented a new REST getSearchConfig endpoint to support search service replacements with the ADS package.

• Implemented a new REST getRecordsCount endpoint for modules, workflows, and data models.

• Implemented a new REST getRecords endpoint.

• Implemented a new REST restoreSchema endpoint.

• Implemented a new REST getSchemas endpoint.

• Implemented a new REST getModulesByModels endpoint.

• Implemented a new REST getModelsFromSchema endpoint.

• API Documentation: Updated the Update User (PUT /users/{userId}) documentation to clarify the following behaviors:

  • Immutable ID: Explicitly stated that the userId field cannot be modified.

  • Notification Logic: Clarified that the shouldNotify parameter specifically enables the New Account (Token Invitation) email and does not suppress User Changed notifications.

• The /fbu/uapi/pdfbar/combine - flatten parameter is scheduled for sunsetting in version 8.0.0. It will be completely removed from the platform in version 8.2.0.

• The /fbu/uapi/image/parsePDF endpoint is an undocumented API endpoint that is scheduled for sunsetting in version 8.0.0. It will be completely removed from the platform in version 8.2.0.

Applications

• Application Versioning: Service logs have been enhanced to display information about the context of the origin request to improve debugging capabilities.

• Auto-Resolve Conflicts: When using the Auto-Resolve feature for Application Versioning, Creators can view a status of added, modified, or removed after conflict resolution. Now, Creators can view whether the status occurred by the source or the target.

• Unversioned Applications: Optimized performance for loading application settings in unversioned applications, reducing load times.

• [Beta Feature] Application Versioning: Restored the Search Application Elements and Search Values functionality in versioned applications.

• [Beta Feature] Dependencies: Ensured dependencies are correctly displayed even if the dependent application has not yet been promoted to the current environment.

• [Beta Feature] Merging: Improved the performance of module merge operations.

• [Beta Feature] Merging: Improved performance for changeset calls and conflict resolution during merges to reduce UI unresponsiveness.

• [Beta Feature] Promotions: Ensured application commits and states are correctly added to the promotion document.

  Beta features are not yet GA (General Availability) features. They are currently under development.

• Application Versioning: Fixed an issue where the Module drop-down in Workflow Task nodes was not working with the new versioning endpoint.

• Application Versioning: Fixed an issue where a 404 error was returned when calling a transform in a dependency application module in versioned applications.

• Application Versioning: Fixed an issue where updates to a nested transform (one included by another) were not reflected in the versioned application.

• Application Versioning: Fixed an issue preventing the publishing of the first version of an application in specific environments.

• Application Versioning: Fixed an issue where a 400 error was returned when retrieving Data Models for an application in environments with Application Versioning enabled.

• Application Versioning: Fixed an issue where a 409 error returned during Panel Import when navigating to non-application path URLs.

• Application Versioning: Fixed an issue where a 500 error returned when opening the Module History for versioned applications, and no actions, like copy, preview, and restore, were displayed.

• Dependencies Manager: Fixed an issue preventing Creators from searching for dependency applications outside the parent workspace in the Manage Dependencies page.

• [Beta Feature] Application Versioning: Fixed an issue where conflict details were not displayed for deleted components during a merge.

• [Beta Feature] Application Versioning: Fixed an issue where the revert endpoint failed after performing multiple merges.

• [Beta Feature] Application Versioning: Fixed an issue with the generateChangesets parameter usage in merge endpoints to ensure full changesets are processed during validation.

• [Beta Feature] Application Versioning: Fixed an issue where the common ancestor was not detected unless directly referenced by the source or target.

• [Beta Feature] Application Versioning: Fixed the common ancestor and highest base version queries by using the correct creation date field for Branch History.

• [Beta Feature] Application Versioning: Fixed a merge validation failure when merging version 0.0.0 with a branch in specific promotion scenarios.

• [Beta Feature] Application Versioning: Fixed an issue where the base version post-merge did not match the expected value from the merge screen.

• [Beta Feature] Application Versioning: Fixed a corrupted import cache issue that occurred when creating a draft from a version containing imports.

• [Beta Feature] Application Versioning: Fixed a requirement for the context query parameter when making external calls to modules in versioned applications. The system now defaults correctly if no context is passed instead of failing.

• [Beta Feature] Application Versioning: Fixed  an issue where repromoting a default dependency did not automatically update the primary application.

• [Beta Feature] Application Versioning: Fixed an issue where the Created By field is empty when viewing a merge commit.

• [Beta Feature] Application Versioning: Fixed an issue where the application wayfinding failed to link a newly created branch to its parent workspace in the UDesigner.

• [Beta Feature] Application Versioning: Fixed an issue where a 404 error returned when an unversioned application attempted to call a transform residing in a versioned application.

• [Beta Feature] Application Versioning: Fixed an issue where selecting a Login module from a dependent application caused errors. Creators can now successfully select a Login module from a dependent application without encountering errors.

• [Beta Feature] Application Versioning: Fixed an issue where Dynamic Refresh dependencies resolved incorrectly because the full application path was missing.

• [Beta Feature] Application Versioning: Fixed an issue where a 500 error returned when calling the List Submissions for Dashboard API module in a versioned application from an unversioned application.

• [Beta Feature] Application Versioning: Fixed navigation errors (missing workspace IDs) in the breadcrumbs and Branch & Version Management drawer when accessing modules in specific environments.

• [Beta Feature] Application Versioning: Fixed the Application Versioning wayfinding and Branch & Version Management drawer issues that prevented Creators from navigating correctly in specific modules.

• [Beta Feature] Application Versioning: Fixed an issue where nested calls between versioned applications executed successfully even if the dependency was not defined in the Manage Dependencies page. The system now correctly enforces dependency requirements, causing these calls to return errors as expected.

• [Beta Feature] Application Versioning: Fixed an issue for nested transforms (transforms calling other transforms) in versioned applications.

• [Beta Feature] Application Versioning: Fixed an issue where the application context was lost when making API calls between two versioned applications.

• [Beta Feature] Application Versioning: Fixed a merge failure caused by missing component definitions in the resolved layout.

• [Beta Feature] Application Versioning: Fixed an issue where the Content Search endpoint returned duplicate matches for identical values.

• [Beta Feature] Application Versioning: Fixed an issue preventing Creators from setting a specific branch as a dependency.

  Beta features are not yet GA (General Availability) features. They are currently under development.

Bulk Data Operations (BDO)

• Performance: Improvements have been implemented to increase the stability, data integrity, and performance of Bulk Data Operations (BDO).

• BDO Import: Fixed an issue where revisions were not generated when importing submissions or Data Model records using BDO Import.

Centauri

• Plug-In Component: Added a new setting called Disable Input Formula. If enabled, the Plug-In component does not attempt to resolve values that begin with = (equal sign). This setting is useful in a case where a Creator wants to send values to a Plug-In component that begin with an equal sign but are not acting as a formula. If this setting is disabled, the Plug-In component will treat the value as a formula.

• Advanced Datagrid Component: Fixed an issue where the New Row Trigger setting would trigger when a row is edited. Now, only the Edit Now Trigger setting triggers a component when a row is edited.

• Chart Component: Fixed an issue where, in certain situations, series labels did not display properly with stacked column charts.

• Date Input Component: Fixed an issue where the Date Input component Error Message and its value are cleared when focus is lost if the entered date is invalid.

• Data Grid Component: Fixed an issue where, in certain situations, data set in the Data Grid component by a Plug-In component would not render correctly.

• Dynamic Grid Component: Fixed an issue where, in certain situations, clicking Tab on your keyboard incorrectly triggered logic components if a trigger was configured using When Column is Edited.

• Freeform Grid Component: Fixed an issue where column headers of the Freeform Grid component did not translate correctly.

• Intl Phone Number Component: Fixed an issue where validation would incorrectly be applied when in Read-Only accessible mode.

• Number Component: Fixed an issue where Number components set to Read Only View displayed an incorrect value.

• Plug-In Component: Fixed an issue when a null or empty value is returned, and that value is assigned in the Outputs table of a Plug-In component with the replace option, it was not replaced. Now, null or empty values mapped as outputs replace the values if replace is enabled.

• Plug-In Component: Fixed an issue where, in certain situations, the Plug-In component’s Retry setting did not work correctly.

• Rich Text Editor Component: Fixed an issue where, in certain situations, the Rich Text Editor component was not being populated when placed in a modal.

• Rich Text Editor Component: Fixed an issue where, in certain situations, links displayed in the Rich Text Editor component did not open in a new tab.

• Rich Text Editor Component: Fixed an issue where the Rich Text Editor component did not display data properly when it was populated by a Plug-In component.

• Uniform Grid Component: Fixed an issue where, in certain situations, the Uniform Grid component did not display in the editing state on load.

• ViewGrid Component: Fixed a style issue where the column header did not display properly when using the unqork-v2 stylesheet.

Classic Designer

• Navigation Component: Fixed an issue where Titles shown for a navigation panel were not being translated.

• ViewGrid Component: Fixed an issue where formulas in the Grid Columns table were removed on save if a Heading value was not added. The expected behavior is that only the ID is required for each row, and all other columns are optional when configuring the setting.

Data Modeling

• Express Roles: Creators can now set Express roles to any level of access from the Data Model Permissions tables for the model or its fields.

Module Builder

• Module Settings: Some changes were made to the way modules execute when Act as Super-User When Server-Side Executing is enabled.

  • Modules configured to Act as Super-User When Server-Side Executing now execute with elevated access instead of an Express Administrator. This change ensures that all executions operate under the correct and intended user permissions, resolving security inconsistencies and streamlining permissions management.

  • A new field called currentUser.isActingAsSuperUser was added to indicate when a server-side module is executing as a Super User.

  • When a server-side module runs as a Super User, the currentUser.expressRoles and currentUser.role fields display the actual role(s) of that user instead of incorrectly displaying as Administrator in certain cases.

  To learn more, explore the Unqork Community here (log-in required).

• Duplicating Modules: Fixed an issue where the Duplicate Element modal would incorrectly display the module type of Other instead of the correct module type.

• Module Save: Fixed issue where Creators could save a module name that consisted only of whitespace. This issue has been corrected to promote best practices and ensure data integrity.

Platform Architecture

• Moment.js Formulas: Fixed an issue where the tz function in Moment.js formulas returned an Out of Range error for certain locales.

• Submission Revisions: Fixed an Object Not Found error affecting specific submission revisions.

Record Collections

• Exporting Records: Fixed an issue when a warning message was displayed when stopping an active Export Records job. The previous message incorrectly referenced import instead of export.

• Job Tracker: Fixed an issue where the Job Tracker page failed to load the first created job.

UDesigner

• Applications: Fixed an issue where modules moved between applications would fail to load in UDesigner if a previous version was restored. This issue occurred when the restoration process incorrectly reverted the module's application association to its original location. The restore logic was updated to ensure a module's current application and workspace association is preserved during restoration, preventing data inconsistencies.

Vega

• Embedded UI: Updated the mount module and other embed methods to now pass exceptions when internal errors occur during execution. Previously, these errors were only logged to the Console, making them invisible to the end-user and preventing Creators from programmatically handling them. Now, Creators can use standard JavaScript try/catch blocks to intercept these errors, enabling user-friendly messages or other customized error handling logic for a better end-user experience.

• Bring Your Own (BYO): Fixed an issue in the Custom Assets Administration pages where errors were being displayed when uploading a valid BYO package.

• Button Component: Fixed an issue where Button components marked as hidden by default display on page load if the Disable on Invalid Forms setting is enabled.

• Date Input Component: Fixed an issue where the Date Input component would unexpectedly close when clicking the Month or Year selectors if the component was being used in an embedded HTML environment. The calendar component now remains open as expected when clicking these options.

• Date Input and Vega Table Component: Fixed an issue where the calendar selection in the Date Input component did not display properly in a Vega Table component.

• Embedded UI: Fixed an issue where the Date Input component calendar was not rendering properly when embedded in an external application with Embedded UI.

• File Component: Fixed an issue where the File component did not work when system file access was disabled on Microsoft OS.

• Logic Components: Fixed an issue where ButtonClick did not trigger logic components watching for clicks.

• Role-Based Access Control (RBAC): Fixed an issue where groups applied to roles by default were not visible in currentUser object in Express View.

• Search Select Component: Fixed an issue where the Add Value functionality did not display in the Search Select component if the component had previously been reset using a Data Workflow component. The option to add a new value now displays correctly after the component is reset.

• Search Select Component: Adjusted the behavior of an On Change event configured in the Search Select component so that it only emits when the selection value is changed. Previously, it emitted when the end-user tried the search but made no selection.

• Simple Select Component: Fixed an issue where options would be incorrectly cleared if the Clear button is clicked by the end-user with no selections made.

• Text Field Component: Fixed an issue where the reset Output Type did not work correctly when applied to a Text Field component.

• Vega Chart Component: Fixed an issue where empty data did not display properly in the chart.

• Vega Table Component: Fixed an issue where a GroupBy selection would display the property name of the column that is grouped instead of the label.