Version: 4.19.0.2518
Release Date: February 2, 2021
Platform version 4.19 was available on February 2, 2021. This release focused on connector updates and improvements. The release contains several beneficial new features and enhancements. Learn more about the release below. For detailed information about individual items, refer to the Platform Documentation Center.
DryvIQ added built-in support for Box Notes. When creating the job, users will now have the option to choose to have Box Notes transferred to the destination platform as .docx file. Learn more about using the Box Notes rendition here.
The Dropbox for Business Teams Folders connector now supports team spaces. Learn more about the Dropbox for Business Teams connector here.
There is a known issue with permission disinheritance when Dropbox for Business Teams Folders is the source platform. When migrating content to a destination platform that supports permission disinheritance, the disinheritance may not be correctly applied. This will be addressed in a future release. Please reach out to DryvIQ Customer Support or your DryvIQ Customer Success representative if you have questions regarding this issue. |
DryvIQ’s G Suite connector has been rebranded to follow Google’s rebranding of G Suite to Google Workspace. Learn more about the Google Workspace connector here.
DryvIQ has upgraded its Microsoft Office 365, OneDrive for Business, and Teams connectors to use the Microsoft Graph API. This ensures jobs using any of these Microsoft connectors are using the latest API available from Microsoft. Existing jobs will not be upgraded to use the Graph API and will continue to run as the usually do. New connectors created after the 4.19 release will automatically use the Graph API.
For the Microsoft Office 365, OneDrive for Business, and Teams connectors, the Domain field on the Create Connection modal has been renamed URL to better identify the information required in the field.
All new Microsoft Office 365, OneDrive for Business, and Teams connections use OAuth 2.0 authorization. Non-OAuth 2.0 Microsoft connections can no longer be created in the application. This will not affect existing connections that do not use OAuth 2.0 authorization.
The Server Name field on the Create Connection modal has been renamed UNC Path to better identify the information required in the field. Learn more about the NFS connector here.
DryvIQ now supports Node.js version 14. Node.js version 12 is the lowest version DryvIQ now supports.
When filtering the job list using the “Failed” status, users will receive an additional filter list to select if the list should show only jobs that failed, only jobs that failed to start, or show both. Learn more about job status filters here.
The jobs list when manually selecting jobs for reports now displays the parent job name under the child job name to help users differentiate between jobs.
The default delete_propagation value will be set to ignore_both if no selection is made in the user interface when creating a job. When the API returns the policies for a job, the default value will be returned when it is being used.
The default conflict_resolution value will be set to conflict_copy if no selection is made in the user interface when creating a job. When the API returns the policies for a job, the default value will be returned when it is being used.
DryvIQ now prevents any entity from being saved with just a space in the name. If a name field contains only a space, DryvIQ will apply a default name or present validation so a proper name can be assigned.
Group permission preservation now works when passthrough is enabled for jobs between two NFS connections.
Lower case restricted segments are properly sanitized in Microsoft Office 365 and OneDrive.
Folders uploaded to Office 365 or OneDrive for Business with AMR enabled will no longer have a status of “None.”
Text on the Reports creation pages was edited to correct display issues.
Convention jobs with permissions will now correctly export the reports for child jobs.