Connector met delay van x (4 bijv) dagen na release van het pakketupdate
Doel hiervan is dat veel organisaties (met name gemeenten) niet versie "n" willen, maar "n + x" (dagen/maanden).
Zie het als de reeds ingediende automatische OTA tier upgrade, maar dan voor Setup Store applicatie packages.
| Product | Application Workspace |
Also maybe by a task scheduler/time or date based upgrade (pre-set the new package and on monday it would be live)
Users will have a better understanding that packages are still installing. Especially when uploading large files to the local system of the user a threshold would be handy.
This would be ideal that in case of a certain period of time when a package is in Test/Acceptation, and a new version is available, the current acceptation version can go to Production before the new version is applied.
We would like to automatically update the different stages of managed packages.
For example, we have a package from the Liquit setup store updated in development using a synchronize connector scheduled task. After x-time we would move the develop stage to test automatically. After some time this stage should be moved further to acceptance and eventually to production.
This cannot be accomplished by creating different connector update schedules for the different stages as you might get a different version in production as the version in the previous stages.
Also we would like to have some more scheduling options in Scheduled Tasks. At this time you can only define daily, weekly, monthly but you're unable to define some advanced scheduling like second Tuesday of the month for example.
Customers are asking for this
It would further automate our patch cycle for seldomly used titles, if we could define a threshold to promote a package to the next ring if it has been installed/launched successfully by x colleagues.
for adobe and chrome updates is this a real advantage to improve security