The Package Workflow This configuration screen allows to set expiration times triggering automatic transition of packages between states (workflow). The overview of the states and possible transitions between them is described in Processing of a package and possible package states (workflow). It The configuration is split into several sections and it is possible to set the following:
Package requests expiration
Number of days after which a request for a package, for which the upload of files never started, is deleted.
Expiration of packages, which are being uploaded
Number of hours after which a package with unfinished upload of files is irrevocably deleted.
...
Active packages
Minimum expiration time
Minimum number of days after which an active clean package is deleted. The package expiration time can be set by the user during the package creation, but it cannot by lower then this setting.
(0-10000, default: 1)
Maximum expiration time
...
Maximum number of days after which an active clean package is deleted. The package expiration time can be set by the user during the package creation, but it cannot by higher then this setting.
...
(0-10000, default: 360)
Default packages expiration
Default number of days after which a an active clean package is deleted and cannot be downloaded anymore. The package expiration time can be set by the user during the package creation, but if not specified, it will be this value. Must be between the minimum and maximum times set above.
...
.
When changing the value, it can be selected, whether to apply the change even to existing packages. Otherwise only new ones will be affected.
(0-10000, default: 30)
Default expiration for packages in a briefcase
The default number of days for which the expiration of a package in a briefcase is set. After expiration, the package is deleted and users cannot see or download it anymore. Administrators can still see or restore the package.
When changing the value, it can be selected, whether to apply the change even to existing packages. Otherwise only new ones will be affected.
(0-10000, default: 30)
Quarantined packages expiration
The number of days, after which an active quarantined package is deleted.
When changing the value, it can be selected, whether to apply the change even to existing packages. Otherwise only new ones will be affected.
...
(0-10000, default: 30)
Deleted packages
Deleted packages expiration
The number of days, after which a deleted clean package is moved into archive or shredded (depends on whether the archive functionality is enabled).
When changing the value, it can be selected, whether to apply the change even to existing packages. Otherwise only new ones will be affected.
(0-10000, default: 90)
Deleted quarantined packages expiration
The number of days, after which a deleted quarantined package is moved into archive or shredded (depends on whether the archive functionality is enabled).
When changing the value, it can be selected, whether to apply the change even to existing packages. Otherwise only new ones will be affected.
...
(0-10000, default: 90)
Archived packages
Archive enabled
Enables or disables the archive functionality. If the archive is enabled, deleted packages are moved to the archive after expiration. If disabled, the package contents is erased. See Workflow.
(default: enabled)
Archived packages expiration
The number of days, after which a clean package from the archive is shredded, its contents is irrevocably lost and the space is freed on the data store.
When changing the value, it can be selected, whether to apply the change even to existing packages. Otherwise only new ones will be affected.
(0-10000, default: 360)
Archived quarantined packages expiration
The number of days, after which a quarantined package from the archive is shredded, its contents is irrevocably lost and the space is freed on the data store.
When changing the value, it can be selected, whether to apply the change even to existing packages. Otherwise only new ones will be affected.
(0-10000, default: 360)
Other packages
Package requests expiration
Number of days after which a request for a package, for which the upload of files never started, is deleted.
When changing the value, it can be selected, whether to apply the change even to existing packages. Otherwise only new ones will be affected.
(0-10000, default: 30)
Expiration of packages, which are being uploaded
Number of hours after which a package with unfinished upload of files is irrevocably deleted.
When changing the value, it can be selected, whether to apply the change even to existing packages. Otherwise only new ones will be affected.
(0-1000, default: 24)
Maximum time for which a package can be waiting for
...
the check results
The number of minutes, for which to wait for the results of all package file checks. The checks that are not finished within this limit are terminated and if this happens the package is moved to active clean or active quarantined packages, depending on the Detection settings.
When changing the value, it can be selected, whether to apply the change even to existing packages. Otherwise only new ones will be affected.
(0-10000, default: 60)
Shredded packages
Automatically delete metadata about shredded packages
If this feature is enabled, records with information about shredded packages will be deleted after a specified period of time.
(default: enabled)
Expiration of shredded packages' metadata
Specifies the number of days after which records of shredded packages will be deleted. The package data (files) of shredded packages had already been deleted when the packages were shredded. This concerns only the remaining metadata about those packages. Days are counted since the shredding, not since the package creation.
(0-10000000, default: 1100)