Client Update Notification tag instead of the yellow banner
complete
C
Corey
The current client update notification is the yellow banner across the top of the screen. When the client is viewing the app in full screen, the notification banner pushes the screen down and causes a scroll bar to appear on the right.
Is there any way to make the client update notification a bindable tag or something so I could create my own indicator that alerts the users an update is available (and remove the yellow banner). This way I could add an indicator to my menu bar and not have the banner or scroll bar visible all the time on nodes that are not always manned, but are visible to clients and guests.
I guess this would also require a function to "get" the update on some user action.
Log In
P
Paul Griffith
complete
This feature will be available in 8.1.24:
P
Paul Griffith
planned
s
stefano.tagliapietra
It's a lot of time this request is under review, so I propose my solution, hoping this helps speed up the solution (and go to the planned status)...
I propose to create a system tag, "Client/System/UpdateAvailable", that is true if an update is available from the gateway. Then I would add a script function: system.util.updateProject() that executes the update.
For the yellow banner, I would remove it completely. Otherwise it would be possible to create a project parameter to decide to use it or not.
With this changes everything is open to the integrator. Just some examples:
- update when the user changes page
- update using the inactivity timeout
- update on user action (notify and update with a custom button)
- do not update until the client restarts (ignore the availability of the update)
Hope this request will be accepted, because with version 8 there is no staging project and every save of the project is published, so this becomes very annoying to the end user. This solution at least alleviates the problem.
Thanks
S
Simon Williams
This would be really useful. It would allow the implementation of cleverer schemes, such as automatically updating at certain "safe" points (like switching main window, or after committing a transaction) but not interrupting the user if they are in the middle of a task (i.e. data entry). Or allowing the user to update, but automatically updating if they haven't done so after 5 minutes or something.
I was going to add a request for separate update modes for staging vs published, but this suggestion is even better. When developing we want it set to "notify", but when publishing we want to "push". At the moment we have to remember to change the setting before updating. I haven't found any workaround yet. If there was a tag and an update function I could implement this easily.
l
lionel MAZEYRAT
Could be usefull in case of 2 or more client on the same computer with multiple monitor, and a way to sync the client notification. Accept update on one client triggering accept on all other client