6.36 Platform Release Notes

The new Advanced Settings panel helps you find your most-used settings faster                                                

We've added a new settings panel to the component configuration window, called Advanced Settings. The Advanced Settings panel, found at the bottom of the configuration window, now groups together less frequently used settings. This change reduces visual clutter and makes it easier for creators to identify the component's most-used settings. Together, this change means easier onboarding and faster configuration!

Build, customize, and brand your password reset flow                                                

You can now build and customize your own password reset flow. As a creator, you now have full control over the password reset flow experience, including aligning it to your brand's styles.

Check platform availability on our new status page                                                

Unqork's new status page provides real-time information on platform availability. Now you can get live updates on resolution timings for major issues. You can also sign up to receive notifications when a major platform issue is impacting your work, using the Subscribe to Updates button. Visit https://status.unqork.com/ to see the new status page.

• Logic Tooltip: Added a tooltip to the Logic field of the Gateway Output Link's Inspector Panel. The tooltip helps creators understand how Logic affects the Gateway Link and what to enter in the field.

• Improved Logging: Enhanced logging in the Timer Start Node to help creators debug automated workflows and quickly identify the source of automated workflow issues.

• Close Button: Resolved an issue where creators needed to click the Close button of an Inspector Panel twice before the Panel would close.

• Submission Getters: Resolved an issue where submission getters didn't add to a workflow submission on initial load.

• Persisting Data: Resolved an issue where some fields set to Store Data in Database didn't persist through the workflow. This error occurred when Initializers triggered a save event before data fields could save to the database.

• Sort Order: Resolved an issue where older modules (using different date formats) did not respect the Created By sort order in certain views.