Every month or every other month a new version of MiWorkplace is released. MiWorkplace itself does not have an update feature integrated. That means updates must be done manually. This sounds not very convenient but is rather painless.

A requirement for a painless update is that the workspace folder where MiWorkplace stores the state of the application and various other files it needs to function is not placed inside the application folder. By default if MiWorkplace is started with a double click in the file manager the workspace folder is created in application folder.

The place for the workspace folder can be specified with the parameter data on application start.

/opt/miworkplace/miworkplace -data /home/user/.local/share/miworkplace

UI Element not showing

During updates of MiWorkplace sometimes UI elements (like menu entries) will be added to or removed from the application.

As MiWorkplace is based on Eclipse e4 technology it also inherits its weak points. Updating the application is to some extent still a weak point. See “I modified my App.e4xmi/fragment.e4xmi but the changes aren't being loaded. Why?” at Eclipse4/RCP FAQ.

So to get the state of the application updated with the new elements from the update the persisted state of MiWorkplace needs to be cleared so that it can be rebuild again. This can be achieved by adding the parameter “-clearPersistedState”. So if you started the application like this

/opt/miworkplace/miworkplace -data /home/user/.local/share/miworkplace

you need to start the application like this

/opt/miworkplace/miworkplace -data /home/user/.local/share/miworkplace -clearPersistedState

Note: You need to start the application only once with the additional parameter -clearPersistedState. You can safely remove the parameter on the next start.