...
The configuration needed to accommodate the changes made to improve portal mass upload performance was delivered as the default configuration in the 2022.2 release. So there is nothing special to do. It is fully compatible with an older version of the portal, so there is normally nothing special to do to get an older version of the portal working. The detail of the configuration is explained here (See properties tagged
| Status | ||
|---|---|---|
|
In this release, the validation is no longer done directly by the portal but by the server at its request, asynchronously. This does not allow the portal to delete jobs on demand (they may still be in the process of validation). As a consequence, we deactivate the job instead of deleting it. And it is a purge task that takes care of deleting the deactivated jobs, but also jobs and items that are unusable (orphaned items or jobs, empty jobs, etc). The configuration of this purge is detailed here.
...