eva/3 Application BuilderDeveloping eva/3 ApplicationsUpdate Management of eva/3 Applications 

Application update

A application can fetch an update from an update database. The application needs a licence table additional to the update tables. In the licence table contains the licence number for which updates should be fetched..

An Update Daemon must be initialized before any update can be fetched by the application. The Update Daemon should be initialized at the beginning of the application. For this, the event AfterIntializeMacro of the MiddlePanel are recommended. The system command StartUpdateDaemon can be used for activating the Update Daemon.

The update process can be started with the system command CheckUpdate. If an update was found, a message dialog will be opened which informs about the update process (s. fig. 278 ).

Fig. 278: Update dialog
Fig. 278: Update dialog

The update dialog shows all available updates. The button Download downloads all available updates.

Fig. 279: Update download
Fig. 279: Update download

All downloaded updated can be individually selected and updated using the button Refresh (s. fig. 279 ). A dialog informs about the upcoming update (s. Fig. 64). Also all respective application instances will be informed about the update, too. Any of the updating applications can Veto this update using the upcoming information dialog.

Fig. 280: Starting update dialog
Fig. 280: Starting update dialog