Check deployable packages at startup is unchecked | The deployment behavior is not modified. |
Check deployable packages at startup is checked and no other package has previously been deployed | When the session starts, the system queries the database for packages linked to your credentials.- If no app is available, no message is displayed.
- If an app set to “Auto deploy” is available, it is automatically deployed (the APP_CACHE is created if necessary, requiring a session restart). The end user is notified of the deployed Configuration (and if a restart is needed).
- If more than one app set as “Auto deploy” is found, or if any of the retrieved app is set to auto-deployed, the standard Deployment tab opens automatically, asking the end user to select an app to deploy.
|
Check deployable packages at startup is checked and another package has previously been deployed | When the session starts, the system retrieves the deployed app (based on the Manifest file located in the APP_CACHE) and queries the database for apps available in your project. - If the deployed app has been updated on the server (i.e the expert user has explicitly incremented the version of this app), and the app is set as “Auto-deploy”, a deployment is performed and you get an information message. If the app is not set to Auto-deploy, a message informs the end user that the app version he is using is not the latest one.
- If the app version has not changed, nothing particular occurs.
- If the app is not retrieved from your collaborative space or the database, your APP_CACHE is cleaned out and the local installations of the deleted app are removed).
|