7.22.0 Platform Release Notes

Enhancements & Bug Fixes

Applications

Enhancements

• Branch and Merge: Application branches can now depend on other branches, instead of only being dependent on published versions. This enhancement allows branches to take in changes that occur in other branches instead of waiting until a new version is published.

Centauri

Enhancements

• Express View: Removed the Missing Component placeholder that rendered for Vega-only components when previewed in Centauri Express View. Now, no message displays for Vega-only components in Centauri modules.

• File component: Previously, when setting the component to Disable User Input, the component did not display in Express View. To improve accessibility for end-users, the disabled component displays so screen readers can inform the end-user of its location and notify them that they cannot upload a file.

Fixes

• Aggregate operator: Fixed an issue where numeric and empty string ("") values included in an Aggregate operator's Group Key would convert to strings and undefined values, respectively, in the output groups.

• Button component: Fixed issue when the Input Behavior setting was set to Read-Only - Legacy. After saving the component and re-opening its configuration settings, the setting reverts to Enable User Input. User input settings will now remain selected when the read only behavior is selected.

• Chart component: Fixed an issue where the chart colors only reflected in the pie chart type.

• Dynamic Refresh: Fixed an issue where, in certain situations, dynamically-refreshed modules did not load when navigating back and forth between Centauri and Vega modules.

• Number component: Fixed an issue where the Show Thousands Separator did not function correctly if the Number component was set to Read Only View by an Initializer component configured with a Manual trigger.

• Number component: Fixed an issue where decimals did not truncate to the specified limit. For example, if the decimal limit is 2, then 19060.60 displays as 19060.60 instead of 19060.6.

• Number component: Fixed an issue where the number field was displaying the delimiter inside the decimals.

• Number component: Addressed an issue where the Decimal Places setting did not function correctly in Read Only View. Now, the Number component will use the setting to truncate the displayed value to the set limit.

• Rich Text Editor component: Fixed an issue when pasting content from a Microsoft Word document. When pasting content with the spacing at the bottom of the paragraph set to 0, the bottom margin was not retained.

Classic Designer

Enhancements

• Component Notes: Implemented a security enhancement to prevent injection attacks in the Component Settings modal A modal is a window that appears on top of the content you are currently viewing. side notes in the Module Builder.

• Search Select component: Added the ability to use a Data Reference Key in Classic Designer.

Platform Architecture

Enhancements

• Execute via Proxy - POST API: Increased the number of files that can be uploaded at one time using the Execute via Proxy - POST API. Previously, it was five files for a total of 500 MB. The limit is now 25 files at 500 MB total.

• Performance: Improved performance for modules that contain a large number of DOM event signals.

UDesigner

Enhancements

• Browser Tabs: Improvements were made to the display names on UDesigner tabs to help with organization and visibility. Titles will now display more information about the type of page open, as well as the name of the module, application, and environment to assist with work organization—especially when multiple tabs are open.

• Browser Tab Titles: Users can now set a page title in the Module Settings that appends to the browser tab. This feature improves the user experience and promotes accessibility requirements.

• HTML Element, Radio Buttons, and Text Field components: Added a message that notifies the Creator Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform. on the Module Builder canvas that no content has been added to the component before saving it.

• Module Builder: Based on customer feedback, the Module Details drawer will be closed by default to free up canvas space and provide a cleaner configuration experience.

• Module Builder: If a component has a label and tooltip, a tooltip icon displays next to the label or the representation header label on the Module Builder canvas. The Button component's tooltip icon will display on the canvas in a later release.

• Module Builder: Added support to preview a module in the context of the application. From the Preview drop-down, Creators can now select Preview Within Application Context. Use this method to preview the module in Express View with its associated app path: /app/{appname}/{moduleId}. Doing so ensures the module is previewed with the application styles, header, and footer modules. This new option eliminates the need to preview the application (sending Creators to the entrypoint) and then navigate to the desired module in Express View.

• Module Builder: When operations are added to components, there is now a badge representation on the canvas to indicate operations have been added. On hover, this badge displays a list of the operations created for this component to improve visibility and management.

• Module Settings: The module ID has been added back into the Module Settings modal A modal is a window that appears on top of the content you are currently viewing. as a read-only field for quick reference.

• Operations Builder: Swapped the order of the Add Operation and Paste Operation buttons. Add Operation is now the first button in the Operations Builder.

• Operations Builder: Event descriptions are more concise for improved readability.

• Operations Builder: Added validation to the JSON JSON (JavaScript Object Notation) is an open standard file and data interchange format. Unqork uses JSON for submission (record) data. data entered in the Code Editor.

• Operations Builder: All operation names now display in title case.

• Operations Builder: The placeholder text in operation fields is now be prefaced with e.g..

• Operations Builder: Operation descriptions are now shorter for better readability.

• Operations Builder: The SEARCH_CHANGED event is now available in the Operations Builder, including the display name and description.

• Performance: Improved the initial load time of the Module Builder canvas when a module is first opened in UDesigner.

• Restricted Access: To align with behavior in Classic Designer, UDesigner now displays a View Only badge for users with limited access. This enhancement provides greater clarity into user access levels across the platform.

• UDesigner Breadcrumbs: Made improvements to the breadcrumbs for workspaces that now allow Creators to use them to navigate to their desired level of the workspace page.

• UDesigner Wayfinding: Improved the wayfinding experience on the UDesigner homepage to ensure that the View buttons remain accessible to Creators using smaller monitors and laptop screens without having to scroll across the page.

Fixes

• Imported Modules: Fixed issue where imported modules were not linking to the correct versions in Express View.

• Initializer component: Fixed an issue where the vegaOperation Output Type was not displaying for existing builds. Because the Initializer component does not include the Operations Builder, it’s strongly recommended to use other components that have Operations Builder to configure operations.

• Module Builder: Fixed an issue when scrolling in the Module Builder did not work correctly. The scroll bar could not be selected to make scrolling faster. This release fixes this issue.

• Module Settings: Fixed an issue when a Creator searches for a component in the Components Tray. If they switch the runtime from Centauri to Vega, or Vega to Centauri, the searched groups become collapsed and the components will not display until they re-opened the groups.

• Operations Builder: The On Double Click event was removed from the available options to research better ways to support it.

• Phone Number component: Fixed an issue where a required Phone Number component's value is cleared from the fields in Express View, its data was not being cleared from the database.

• Server-Side Execution Testing Tool: Fixed an issue with the sse.httpResponseBody display when using the Server-Side Execution Testing tool for an API APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services. module. Previously, when setting sse.httpResponseBody in an API module, the value did not display in the tool. The set value now displays correctly during testing.

• Server-Side Execution Testing Tool: Fixed a missing error response in the tool. Previously, error handling responses did not display in the UDesigner Server-Side Execution Testing tool. This issue has been resolved and Creators will now see the appropriate error responses in the tool.

• Unit Testing: Fixed an issue where unit test results in UDesigner did not match those in Classic Designer. This issues has been corrected and unit test results are consistent across both environments.

Vega

Enhancements

• Performance: Made improvements to page load performance, focusing on modules with a large number of components.

• Performance: Optimized performance in instances where many events are emitted simultaneously.

• Search Select component: The component now contains the Allow Option Creation setting (with a Component State of creatable) that lets end-users add options manually. When enabled, end-users can enter text in the field and create a new option in the list for single and multiple selection Search Select components. To add a new option, end-users click into the drop-down and enter text. When finished, they'll click Enter (Return) on their keyboard. This setting applies regardless of whether Allow Multiple Selections is enabled.

• Search Select component: Added support of the Search Value, or the value that the end-user enters in the component. This enhancement lets Creators configure a Search Select component that filters API results.

• Image component: Added a message that notifies the Creator on the Module Builder canvas that no content has been added to the component before saving it.

• Vega: Components whose Property Id (key) contains a ”.” (period) will no longer render on preview in Express View. This changes matches existing documentation guidelines. UDesigner save will remove characters like ”.” (period)) on component save. A console error is logged in the browser if the runtime detects a malformed property ID, and identifies which component contains the issue.

• Vega Table component: Updated the Show Pagination setting to exclude 50 and 100. The supported options are now 5, 10, 15, 20, and 30. In Express View, end-users can use the Rows Per Page drop-down to select one of these options.

• Vega Table component: Added a new setting called Enable Pagination that controls the pagination of data provided to the component. When enabled, the Vega Table component’s data is paginated. When disabled, all data will be displayed on the Vega Table with no pages.

Fixes

• Aggregate operator: Fixed an issue where numeric and empty string ("") values included in an Aggregate operator's Group Key would convert to strings and undefined values, respectively, in the output groups.

• Dynamic Refresh: Fixed an issue where, in certain situations, dynamically-refreshed modules did not load when navigating back and forth between Centauri and Vega modules.

• File component: Fixed an issue when the Set File Formats to Accept is set to .AVCHD. End-users Express View is how your end-user views your application. Express View also lets you preview your applications to test your configuration and view the styling. This is also the view your end-users will see when interacting with your application. After configuring a module, click Preview in the Module Builder to interact with the module in Express View. could upload other file formats without receiving an error.

• File component: Fixed an issue where the component incorrectly uploaded files to the cloud on submission if the component had Store Data in Database and Parse on Upload disabled.

• iFrame component: Fixed an issue that prevented the component from loading when missing the URL parameter.

• Number component: Fixed an issue where the Show Thousands Separator did not function correctly if the Number component was set to Read Only View by an Initializer component configured with a Manual trigger.

• Number component: Fixed an issue where the component was incorrectly truncating the decimal.

• Number component: Fixed an issue where the thousands separator was not added for different locales, like es.

• Number component: Addressed an issue where the Decimal Places setting did not function correctly in Read Only View. Now, the setting now truncates the displayed value to the set limit.

• Rich Text Editor component: Fixed an issue when pasting content from a Microsoft Word document. When pasting content with the paragraph space below it set to 0, the bottom margin was not retained.

• Vega: Fixed an issue when a Creator tries to log in using a link that includes the ?previewRuntime=2 query parameter, Centauri loads instead of Vega.

• Vega Chart component: Fixed issue where notes added to a Vega Chart component did not save.

• Vega Table component: Fixed an issue where, in certain situations, the maxSize property was not applied to the column.

• Vega Table component: Fixed an issue where pinned bottom rows were displaying as duplicates.

• Vega Table component: Fixed an issue where the Table Set Column Visibility operation did not work on a Vega Table that was nested in a Panel component.

Workspaces

Enhancements

• Data Modeling: The Schema type now has the following updates:

• Data Modeling and Bulk Data Operations: Made general enhancements to Data Models and Bulk Data Operation APIs.

• Data Models - Update Data Model Records API: With this change, when a user attempts to update a model record through 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.