...
This release includes SQL server database updates to improve performance and page loads.
SkySync 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.
SkySync supports version deletes for SharePoint.
External permissions are now supported by the Egnyte connector.
SkySync 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, SkySync will use the following logic to determine how it handles transferring the versions:
If the file doesn’t exist on destination, SkySync 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, SkySync 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. SkySync 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.
...