7.6.0 Platform Release Notes

Version: 7.6.0

Need a slide show version of the 7.6.0 Release Notes to share with your team? Click here to download one.

Release Schedule

Cohort	Staging Release Date	UAT Release Date	Production Release Date
Early Release	May 16, 2024	May 30, 2024	Jun 13, 2024
GA	May 29, 2024	Jun 12, 2024	Jun 26, 2024
Exception/GovCloud	Jun 11, 2024	Jun 25, 2024	Jul 9, 2024

Introducing Unqork's Data Experience

Data Models GA:
- Data models now support Dynamic Refresh and imported modules.
- Data Models now support deeply-nested structures. For example, objects that contain arrays, objects, other arrays, other objects, and so on.
- Improved flow for managing changes to your Data Models. Easily change your data structures as your application evolves.

Data Model Queries Projections:
- Creators can now select which data properties they want returned when accessing records using an API. This functionality reduces dependency on complex data workflows and improves query performance.

Data Model Relation Queries:
- Creators can now perform relational queries that retrieve information from multiple Data Models using a single API call, improving performance. This functionality lets Creators make queries that leverage $lookup and $unionWith options.

Data Model Schema Versioning:
- Beginning with this release, every time a Creator updates a Data Model structure, a copy of the original structure is kept and a new Data Model version is created. Doing so lets Creators understand all changes made to the Data Model and improve Bulk Transform operations for Data Models based on their structure changes.

To learn more about Unqork Data Models, view our Data Modeling page.

Enhancements

Client Tracker Administration: Improved handling of PII (personal identifiable information) by preventing Protected Field component values from being tracked. Added guidance to determine whether to use a Protected Field component if sensitive data is involved.
Environment Administration: This enhancement increases the password length from 8 to 12 characters. This update affects new users only. If a user has a password with 8 characters, they will not be asked to change it to 12 characters once this enhancement is released. But, if they do a reset their password, then they are required to have 12 characters.
Integration Gateway: You can now enable the streaming of job history and collaborator history from your Integration Gateway activity to a log provider of your choice. Choose which events you would like to stream from the job history summary, job history details, and user activity audit logs to monitor activities that occurred in the Integration Gateway. These logs can be streamed to Amazon S3, Azure Monitor, Azure Blob, or a cloud-based logging service of your choice.
If you are an Unqork Integration Gateway customer, and would like this functionality enabled, please submit a support ticket here: https://support.unqork.com/.

Fixes

Client Tracker Administration: Fixed an issue where the context key populated incorrectly if the Panel component configuration was copied or previously had a module import.

Enhancements

createModelRecord: Updated the endpoint to allow an existing _id to be passed on creation. Doing so allows Creators to maintain data references when moving records between environments.
getModelRecords: Updated the endpoint to include the lookup option in order to support multi-collection querying in Data Models.
getModelRecords: Updated the endpoint to include the unionWith option in order to support multi-collection querying in Data Models.

Fixes

Date Input component: Fixed an issue when existing date values changed unexpectedly after deleting a digit from the day, month, or year, and clicking outside of the input box.
File component: Added a new setting that lets Creators customize the error message that displays when a file is uploaded with an incorrect format.
Number component: Fixed an issue when editing values in the Number component when Show Thousands Separator is set to (ON).

Fixes

Dynamic Refresh: Fixed an issue where, in certain situations, if the Panel component’s post-trigger is executed in quick succession, the post-trigger would execute indefinitely.