6.30 Platform Release Notes

Data Workflow tooltips are now available!

The Data Workflow component is a powerful tool, but also a source of confusion for many Creators. So, we've added tooltips to every single operator in the Data Workflow component. Now, Creators can get an overview of what each operator does and how to use it right from inside the component. And don't forget, you can click the Go To Help Page link to bring up our In-Product Help. There, you can access over 75 Data Workflow-related articles, with new content added regularly!

• Data Workflow Component: Set Do Not Sanitize Formula to be checked by default in applicable operators. This change enables following best practices by default.

• Button Component: Added helper text for each Action Type, to help Creators understand when to use each option.

• Browser Storage Component: Adjusted structure of cached data to more closely resemble submission data. Now includes metadata and is returned in sorted order.

• Plug-In Component: Renamed the Pre Trigger setting to Concurrent Trigger. This change more closely reflects the actual execution sequencing behavior.

• Data Workflow Component: Resolved case-sensitivity requirement when assigning sort order to the Sort operator. Sort operator supports "Asc/Desc" as well as "asc/desc".

• ViewGrid Component: Resolved an issue that caused an infinite loop when applying filters on page 2 or later of a paginated ViewGrid.

• Number Component: Resolved an issue where using a rule to clear or show values in the Number component was not working.

• Plaid Component: Investigated and updated documentation for Plaid Token permissioning behavior.

• Field Validation: Added a Workflow validation rule that ensures any values persisted under the form field resemble a Mongo ObjectId. This helps check that the form value is a module ID.

• New Workflow Setting Added: The Workflow Settings page now includes the Only Keep Persisted Data Upon Navigation setting. When enabled, navigating will clear non-persisted data. This lets Creators optionally design their app to clear out non-persisted data on navigation.

• Workflow Node Translations: Resolved an issue where English translations for workflow nodes were not being saved.

• End Node: Resolved an issue where the Use an Existing Module setting still showed after disabling the setting. This behavior occurred after the end-user selected an existing module, then disabled the setting.

• Message Node: Resolved an issue where email notifications about Message node failures were not being delivered to the workflow owner. Occurred when the workflow owner field did not contain a valid email address. Now a detailed error report with the workflow path, node ID, and full error message and stack are logged to the request object.

• Deleting Local Applications: Resolved an issue where Creators could not delete local applications that had WORM storage enabled.

• Workflow Duplication Error: Resolved an issue where some Creators would see an error when attempting to duplicate an existing workflow app. The error occurred only on the first duplication attempt.

• Promotions Error: Resolved an issue where Creators would not get a notification that promotions had failed. Occurred when getHost failed but the promotion remained stuck in an In Progress state.

• Submission Error: Resolved an issue that resulted in a 404 error on saving a submission. The error occurred when saving an existing submission in a non-entrypoint module using /app/:appPath.

• Promotions Target Document: Added a test to ensure the promotions object in the target document correctly updates upon promotion. Fix ensures the promotion history (promotions.out field) in the document is not overwritten.

• Fetching Error: Resolved an issue where a 500 error showed when fetching sorted lists from shared modules.

• Promoting Translations: Resolved an issue where translations promotions were missing from the promotions service.