EFA#124 efaCloud: Manually changing current logbook / clubwork in efaCloud projects need restart of efa #252
Description
This affects efaCloud projects only.
In efa the admin can choose the active logbook freely between from several logbooks of the current project.
In local or efaRemote projects, this works perfectly.
In efaCloud projects, the local change of the current logbook/clubworkbook works as well.
But when changing records in the newly loaded logbook, the updates get pushed to efaCloud server.
But the efaCloud server denies receiving them because it is not informed about the change of the current logbook.
So, updates directly after changing the current logbook are not received on the server until efa gets restarted (usually at 4 o'clock in the morning).
This is not perfect in the scenario of the annual logbook change, where the admin sometimes has to make updates to the older logbook, and thus switches a lot between the former and the actual logbook
Suggested Solution(s)
- efa should recognize logbook / clubwork changes for efaCloud projects and suggest a restart of efa directly after changing the logbook.
- alternatively, efa could inform the server after a logbook change that the client changed its logbook