If a Taskset lies within the context of an Application object, the Scense runtime system will consider two additional RunModes.
Installed.
The application turns out to be completely installed on the workstation.
In such a case the application is normally just started.
Not Installed.
It turns out the application is not yet (completely) installed on the workstation.
If this condition is detected in the Application Mode, the Install Mode will be called for automatically.
When using the Extended Install method or with Windows Installer- and Virtual Layer applications), the Install Mode is first executed by the OnDemand service. When this is finished, the de Install Mode is executed another time, under the user’s account.
After executing the Install Mode Scense returns to the Application Mode where the RunMode is re-defined.
Normally the RunMode will be ‘Installed’ after installation, but it could happen the installation (or part of it) went wrong. In such a case the RunMode again is set to ‘Not Installed’ and the application is usually not started. In this case you may want to send a message to the user to inform him/her about the failed installation, including the advice to contact the administrator.
Runtime behavior
Taskset type.
When a Taskset is located within an Application object, the Taskset type will have been changed from ‘Normal’ to ‘Application’ as well.
An ‘Application Taskset’ supports the Install methods and will adapt itself to the Application object the instant a change of status occurs.(Test, Approval, Final).
Migrations.
During execution of a migration the Application Taskset is set to ‘Disabled’, to prevent users from installing the application at the exact moment of migration.