Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

The Package Workflow 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 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.

Minimum time for which package can be active

Minimum number of days after which a 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.

Maximum time for which package can be active

Maximum number of days after which a 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.

Active (clean) packages expiration

Default number of days after which a clean package is deleted. 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.

Active (quarantined) packages expiration

The number of days, after which a quarantined package is deleted.

Deleted (clean) packages expiration

The number of days, after which a clean deleted package is moved to archive or its contents is finally deleted (depends on whether the archive functionality is enabled).

Deleted (quarantined) packages expiration

The number of days, after which a quarantined deleted package is moved to archive or its contents is finally deleted (depends on whether the archive functionality is enabled).

Archived (clean) packages expiration

The number of days, after which a clean archived package is finally deleted, its contents is irrevocably lost and the space is freed on the data store.

Archived (quarantined) packages expiration

The number of days, after which a quarantined archived package is finally deleted, its contents is irrevocably lost and the space is freed on the data store.

Maximum time for which package can be waiting for scan result

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 quarantined clean packages, depending on the Detection settings.

The whole Package Workflow settings screen looks like this:

  • No labels