7.24.0 Platform Release Notes
Release Schedule
Cohort | Staging Release Date | UAT Release Date | Production Release Date |
---|---|---|---|
Early Release |
Jul 15, 2025 |
Jul 29, 2025 |
Aug 12, 2025 |
GA |
Jul 30, 2025 |
Aug 13, 2025 |
Aug 27, 2025 |
Exception |
Aug 14, 2025 |
Aug 28, 2025 |
Sep 11, 2025 |
Enhancements & Bug Fixes
Administration
Fixes
-
Integration Gateway: Fixed an issue affecting Creators Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform. using the Integration Gateway. After configuring a service and setting up a Plug-In component to trigger it, the component’s Data Source URL field populates with an incorrect endpoint. The desired endpoint now populates correctly.
Applications
Enhancements
-
Version Names: Previously, versioned applications were limited to a semantic version number as their name, like 1.0.0. With this release, Creators can now add an optional name to their versioned applications, providing more clarity and flexibility in identifying your deployments.
Creators can now use names like:
-
1.0.0 MyGreatApp
-
2.1.0 FeatureX-Beta
-
1.5.2 ProductionReady
This change allows for a more descriptive and readable identification of your application versions, making it easier to manage and track versions.
-
Branches: Previously, branches were filtered by their base version, which could make it difficult to view all branches at a glance. Now, all branches display in a single, unified panel. That way, Creators are no longer required to switch between base versions to locate a branch. A search bar is also added so Creators can filter branches, making it quicker and easier to navigate their repositories.
APIs
Enhancements
-
Update Data Model Records API: With this change, when a Creator attempts to update a model record using the Update Data Model Records endpoint, they can pass strictValidation: false to update records created with previous versions of the data model that include breaking changes.
Centauri
Fixes
-
Data Models - Schema/Component Generation: Updated the component generated from Array of Non-Enumerable string data type in the schema to the correct Multi-Select component for Centauri modules.
-
Phone Number component: Fixed an issue when configuring the Phone Number component and setting the runtime to Centauri. In the component’s settings drawer, an unexpected, empty Actions section displays. This issue has now been resolved and the Actions section no longer displays when using the Centauri runtime.
UDesigner
Enhancements
-
Advanced and Global Search: New enhancements have been made to Advanced and Global Search to improve usability:
-
When opening Global Search, or using Cmd + / (Mac) or Ctrl + / (PC) on your keyboard, the cursor focuses in the search box by default.
-
When opening the Advanced Search page, the cursor focuses in the search box by default.
-
After entering a search query in the Advanced or Global Search fields, Creators can now press Enter (Return) on their keyboard to execute the search.
-
Dynamic Grid component: Added a new editable setting called Order to each row in the Column Setup table. If a Creator chooses to add a row before the 0 order, the field accepts negative integers. After adding, the setting reorders the rows to begin with 0 once again.
Fixes
-
Copying Module Definitions: Fixed an issue where copying a module definition that includes imported modules would not copy the imported fields in the JSON JSON (JavaScript Object Notation) is an open standard file and data interchange format. Unqork uses JSON for submission (record) data.. The copying functionality now successfully copies imported fields.
-
Decisions component: Fixed an issue where buttonClick inputs in a Decisions component were being converted to $runtimeEvent.payload.value when viewed in UDesigner. This release prevents further conversion.
-
Environment Login: Fixed an issue, where in certain situations, Creators experienced an endless loop that prevented them from logging into their environment in UDesigner, regardless if the Creator is using the Centauri or Vega runtime.
-
Plug-In component: Fixed an issue where the Amazon S3 authentication type was selectable from the component’s External Services drop-down. This option is no longer available in the Plug-In component.
-
Server-Side Execution Testing: After executing a test and clicking into the Response Body field, the tool supports a Find feature when pressing Cmd + F (Mac) or Ctrl + F (PC) on your keyboard. Fixed an issue where the Find feature did not display after pressing those key combinations on your keyboard. This issue is now resolved.
Vega
Fixes
-
Email, Protected Field, Text Area, and Text Field components: Fixed an issue where, if one of these components (which expect a string A string is an object that represents a sequence of characters. Strings typically hold data represented in text form. value) is incorrectly populated with an object An object is a type of data structure that represents a single, self-contained entity that acts as a container for the characteristics of that entity., they would display a string of [Object Object] instead of displaying nothing. Now, when one of these components receives a value in an incorrect object An object is a type of data structure that represents a single, self-contained entity that acts as a container for the characteristics of that entity. or array An array is a type of object that stores one or more data types. Data types supported in arrays include numbers, strings, and objects. format, it does not accept the value and displays nothing.
-
Embedded UI: Fixed an issue when loading the embedded.js script multiple times broke the embed script. For example, unloading and reloading the script when an embedded module is hidden and then displays.
-
Operations Builder: Fixed an issue where the operation search feature did not let Creators search operations by their description.
-
Vega Table component: Fixed an issue where the Enable Pagination setting was enabled even after a Creator disables it and saves their module. To avoid confusion, this setting is now set to (OFF) by default, leaving it to Creators to decide if they want to show the whole data set, or if they want it paginated.
-
Vega Table component: Fixed an issue where a nested Simple Select component in a Vega Table component displayed duplicate labels, icons, and broken styles.
-
Vega Table component: Fixed an issue where the Global Filter Change and Column Filters Change events were not visible in the component’s Operations Builder Event Selection drop-down.
Workflow Builder
Fixes
-
Navigation: Fixed an issue where using the local browser’s Back button in Express View, instead of the workflow’s navigation buttons, resulted in unexpected Initializer component triggering.
Resources