7.12.0 Platform Release Notes

• Managed Assets Administration: Fixed an issue where, in certain situations, the Create Folder modal did not correctly display the Create button.

• Application Versioning: When merging applications, Creators can now determine the component changes made between two modules.

• Application Versioning: Branching and merging is now supported in workflow-type applications, letting Creators configure multiple versions for easy rollbacks, patch fixes, and parallel development.

Workflow-type application support is an early-access feature. To get access to this feature, please contact your Customer Success Representative.

Unqork is continuing to improve the versioned workflow-type application experience. It's important to note that if you do choose to opt-in, versioned workflow-type applications are not currently supported in the following UDesigner experiences:

• Homepage

• Recents

• Favorites

• Search

• Application Versioning: Fixed an issue when publishing a branch, the styles did not publish with it. The newly published application will now contain the correct styles that the branch was using.

• Rules: Extended the advanced rule engine to support additional if/then statements. For example, if a Case Status changes, then trigger an API call.

• File component: Added a new setting called Parse File Raw that disables auto date formatting on upload. This setting only applies when the Parse Files on Upload setting is enabled using the following file formats: .csv, .ods, .xls, .xlsx, .xlsm, and .xlsb.

• Decisions component: Fixed an issue where Grid syntax in decisions was being converted to bracket notation when dynamically refreshed. Now, when a Decisions component is dynamically refreshed, it will retain its Grid syntax.

• Application RBAC: Added improvements to infrastructure related to application RBAC. Specifically related to workflow execution and updating submissions.

• Storage: New updates to Unqork's storage structure provides improvements to saving and querying data in new applications. All Unqork APIs continue to be supported, including the system/GetSubmissions (List Submissions for Dashboard) API.

• Columns component: Added a warning message to the component’s configuration pane when Creators update it and reduce the number of columns in the configuration. When Creators reduce the number of columns, it deletes existing data configured in those columns.

• Component Field Tags: Added a Field Tags modal to every Module Builder component. Field Tags are useful not only to organize and group components, but also for targeting grouped fields using logic components.

• Email component: For this release, UDesigner now supports the Email component. You can begin using it as you have in the Classic Designer.

• Dynamic Refresh: This fix addresses an issue when a Decisions or Initializer component are placed into a Columns or Field Group component. If the Decisions or Initializer component uses an Output Type of dynamicRefresh, the Columns or Field Group component, and all components below it on the Module Builder canvas, do not render and become hidden on the canvas.

• Module Builder: Fixed an issue in the Module Builder canvas where Creators could not visually identify the connectivity of components in a module. For example, a Data Workflow component acting as the output to an Initializer component. These component icons are now available in UDesigner as they are in Classic Designer.

• Plug-In component: Fixed an issue when selecting an external service in the component’s configuration menu. When selecting an external service that has a lengthy Data Source URL, the URL becomes difficult to read in the Data Source URL field.

• Vega Table component: Fixed an issue where empty rows were added and saved to the module definition in UDesigner, but not in Classic Designer. Even when removed, these empty rows would continue to display in Express View.

• Cross-Runtime Support (CRS): The feature now supports the following logic component Output Types for targeting Vega components in a Centauri module:

  • vegaExecute: Trigger a Vega component contained in a Vega-enabled Panel component.

  • vegaValue: Send a data value to a Vega component contained in a Vega-enabled Panel component.

  • New Operation - Execute External Command: Use the Operations Builder in a Vega-enabled Panel component to trigger, or send values to Centauri components.

Cross-Runtime Support (CRS) Event Mapping is now behind a feature flag. For performance reasons, Unqork recommends using the vegaExecute and vegaValue types to modify Vega components in a Centauri module.

• Decision Component: Added support for the  Merge Execution Type setting.

• Express View: Added functionality when previewing a module in its application context. Now, header and footer modules remain on the screen and do not reload when navigating to another module in the same application.

• Vega Table component: Added support for Grid syntax to output the value of an entire row.

• Calculator component: Fixed an issue where, in certain situations, the post-trigger was not executing correctly.

• Data Workflow component: Fixed an issue where, in certain situations, the Data Workflow component incorrectly displayed Console logs.

• Data Workflow component: Fixed an issue where the Group Input node did not work as expected.

• Express View: Fixed an issue where the Preview bar would not collapse when the Hide Preview Bar by Default setting in Environment Administration was set to (ON).

• iFrame component: Fixed an issue where, in certain situations, an error would display if the Source URL changed in Express View due to logic components.

• Plug-In component: Fixed an issue where, in certain situations, multipart requests with unicode and Base64 returned an error.

• Search Select, Simple Select, and Menu components: Fixed an issue where, in certain situations, Adornments were incorrectly displaying in the Settings modal in Classic Designer.

• Translations: Fixed an issue where forward slashes ( / ) in the locale value resulted in no translations.

• Vega Table component: Fixed an issue where, in certain situations, Vega Simple Select components were not showing options when configured with a Data Reference Key.

• Vega Table component: Fixed an issue where, in certain situations, Vega Select components could not receive values when added as columns using the Table Add Column operation.

• Timer Start node: Fixed an issue where, in certain situations, jobs started by the Timer Start node would be delayed.