6.80 Platform Release Notes

Version: 6.80.0

TIP  Need a slide show version of the 6.80 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

Jun 22, 2023

Jul 13, 2023

Jul 27, 2023

GA

Jul 12, 2023

Jul 26, 2023

Aug 9, 2023

Exception/GovCloud

Jul 25, 2023

Aug 8, 2023

Aug 22, 2023

Resources

Contents

Administration
Components
Workflow Builder

FEATURE FLAG  This feature will be released behind a Feature Flag. Users must opt-in to see these improvements. Please contact your Unqork representative if you would like to opt-in.

Release Highlights

Introducing the new API Access Management page!

Administrators can use the API Access Management page to create secure 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. access credentials for Unqork’s Creator Also known as Unqork users; anyone who is inside the Unqork platform. and Express APIs. Each credential set contains a unique client ID and secret, and authenticates with Unqork using the OAuth 2.0 Client Credentials Grant. Customers can use these credentials wherever they want to provide secure access to Unqork via external APIs.

Administrators can also use the API Access Management page to:

  • View credentials.

  • Revoke credentials.

  • Delete credentials.

  • Generate new Secrets should a user lose them.

Introducing Multi-Role Swimlanes in Workflow!

This new feature is a quick and easy way to configure collaborative end-user End-Users are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product. experiences in Workflow. Creators can now assign multiple roles to a swimlane in the Workflow Builder, enabling more precise and streamlined control of role access in Workflows.

Important notes regarding RBAC RBAC (Role-Based Access Control) is a method to control system access for authorized users. The role in RBAC refers to the levels of access employees have to a network. behavior:

  • If an end-user has multiple roles, all of their role permissions will be checked when accessing a swimlane that contains multiple roles.

  • In a multi-role swimlane, enabling Allow Access to Role Ancestors gives access to all roles listed in the swimlane, and their role ancestors.

  • A swimlane cannot be assigned multiple roles if it gives access to Anonymous Users. That’s because giving Anonymous Users access gives all roles access to the swimlane.

Administration

  • Certificate Management: Fixed an issue where expired certificates displayed an EXPIRES SOON badge. They now display the correct EXPIRED badge.

  • Creator (User) Administration: Fixed an issue where, under certain conditions, when a Creator Also known as Unqork users; anyone who is inside the Unqork platform. user's access is revoked, but the session is not immediately terminated. The session now ends immediately after a user's access is revoked.

  • Services Administration: Fixed an issue where secret fields in service details were not deleting as expected.

Components

  • Address Search component: Fixed an issue where address results from certain regions (like the UK) did not include a city value due to differences in the response from the Google Places API. Now, city fields populate from locality and defer to sublocality_level_1 (and postal_town as needed).

  • Advanced DataGrid component: Fixed an issue when end-users End-Users are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product. interacting with a Date Input component inside an Advanced Datagrid component caused an error. In certain timezones (like Mumbai), and with Store Date Only set to Toggle On Icon (ON), the date selected by the end-user displayed as the date prior to the one selected.

  • Data Workflow component: Fixed an issue where formulas in the Create Field operator returned the most-recent valid value from a previous row if the current row (that is being evaluated) does not have the fields referenced in the formula.

  • Date Input component: Fixed an issue where cutting out a date value (Cmd+X or Ctrl+X), instead of deleting it, won’t automatically validate the component. Now, any configured validations (like Required*) automatically fire regardless of how the value is removed.

  • Dynamic Grid component: Fixed an issue where filtering on Text Field, Single-select Dropdown, or Multi-select Dropdown columns were case sensitive. This resulted in values like Hello and hello appearing twice in the filter option list. Now, filtering on these columns is not case sensitive and consolidates filter options of this kind.

    NOTE  This change results in a known third-party library limitation where the Blanks filter option is non-functional. Please contact your Customer Success representative for more information.

  • Dynamic Refresh: Fixed an edge case when a module's Enable Stagger Load is set to Toggle On Icon (ON), dynamic refresh operations would stall and never complete when refreshing components that are hidden in that module.

  • Feature Flag Icon FEATURE FLAG Intl Phone Number component: Fixed an issue where end-users typing a value in Express View that matched a country code were automatically deleted.

  • Feature Flag Icon FEATURE FLAG Number component: Fixed an issue where a value that included only a decimal character (".") was automatically trimmed from the component after a few seconds, or when unfocusing the component. Now, a value of only a decimal (".") displays and shows an Invalid Number validation error.

    NOTE  After successful testing, this fix will become the default behavior in platform versions v6.82.0 and above.

  • ViewGrid component: Fixed an issue where server-side pagination elements (for example: page numbers) would disappear when dynamically refreshing a ViewGrid component.

Workflow Builder

  • Workflow Submissions API: Fixed an issue where the /system/getSubmissions API response was missing the workflow attribute. Now the API response includes both workflow and workflowId for backwards compatibility purposes.