Version: 4.17.0.2270
Release Date: August 28, 2020
Platform version 4.17 was available on August 28, 2020. This release focused on continued connector improvements and SQL server database updates for improved performance. The release also contains other beneficial new features and enhancements. Learn more about the release below. For detailed information about individual items, refer to the Platform Documentation Center.
This update contains improvements for database performance. As a result of these improvements, the update may take longer to run than usual. Upgrade time is dependent on database size and will be roughly equivalent to the time it takes to backup and restore the database. As part of the database improvements, DryvIQ requires SQL Server 2016 SP1 (or higher) standard. If you are using an older installation of SQL server, it will not work, and you will need to upgrade. |
This release includes SQL server database updates to improve performance and page loads.
DryvIQ added the option to specify if you want to use a soft delete (move items to the trash/recycle bin) or hard delete (permanently remove) when deleting items. Soft delete is the default delete behavior; however, selecting to hard delete ensures the platform trash doesn’t fill up with unwanted files. This option will be available when creating new connectors in the user interface and through the REST API. For existing connectors, you can patch the connector to set the delete parameter. Refer to the individual connector documentation pages for more information. This parameter is available for the following connectors:
Box (through the REST API only at this time)
The maximum file size for SharePoint Online is now 100 GB.
DryvIQ supports version deletes for SharePoint.
External permissions are now supported by the Egnyte connector.
DryvIQ improved the way it handles transferring a specific number of versions for connectors that don’t support version deletes. When a specific transfer value is set and the destination platform doesn’t support version deletes, DryvIQ will use the following logic to determine how it handles transferring the versions:
If the file doesn’t exist on destination, DryvIQ will respect the version limit set and only transfer the set number of versions during the initial copy/migration.
If the file exists on destination, DryvIQ will migrate all new versions of the file from the source to the destination, even if it results in exceeding the file version limit set on version count. This ensures all new content is transferred. DryvIQ will log a warning to inform the user that the transfer took place and resulted in the transfer count being exceeded.
Additional permission details were added for FS/NFS.
The lists used to choose the source and destination platforms when creating a job have been redesigned to improve usability and to provide the option to search for a connection. Learn more here.
The modal used to create the job schedule has been redesigned to make it easier to create a job schedule. The Schedule settings and Stop Policy settings are now on separate tabs to help group related information. The Schedule tab is now divided into two sections that allow you to select to schedule the job to run on a time interval or to run at a specific time of the day. When you select one of the options, additional fields display so you can specify the information you want to use to customize the selected schedule option. Learn more here.
Job patching has been updated to allow job schedule values to be set to null to clear the setting. For fields that have a default value, clearing the value sets the field back to the default value. Learn more here.
Simulation is automatically enabled when you create a new job from the Simulation tab.
The jobs list pulled through CLI and REST API now returns the discriminator for child jobs so you can readily identify them. Learn more here.
Versions are properly respected for the Egnyte connector.
Group mapping is properly applied when using the Egnyte connector.
When applying permissions to FS/NFS, DryvIQ now sets Read Access using ReadAndExecute instead of Read to prevent losing access rights.
Using the "Select all" option on the jobs grid would not properly select all jobs if there were more than 100 jobs. Now, all jobs are properly selected and the corresponding action (run, cancel, delete, etc.) is applied.
Folder Mapping child jobs now properly inherit the stop policy on_execute setting from the parent job.
Updates were made to job patching to ensure the entire job schedule definition is used when creating the new quartz schedule.
The Sharing Insights were showing items that were only shared with groups as being shared with users.
Paths that exceeded platform limitations were not being reported in simulation mode.
The Learn More link for flagged items has been fixed to link out to the proper documentation page.
The job status “started” has been changed to “queued” to more clearly indicate that the job has been queued to run but isn’t currently running.
The Refresh link on Overview tab refreshes all data on the Sharing Insights on subsequent runs.
Child jobs no longer default to "warn" for duplicate name setting and use the parent job setting.
Scheduled jobs no longer go into a canceled state.
When a new folder was created and an existing folder was moved into it after an initial job run, the content was being duplicated in both places after the next job is run. This issue has been resolved.
The root folder is now tracked in the audit log.
Metadata property values now populate when using the UI scripting function.
The parent job field now populates when generating a report for a child job.
The Export Full Permission Report includes just the permissions for the jobs in the selected categories.
Group sharing shows when added after the job runs after a permission or full reset.