You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After initialising GAPS on Central Server, I noticed the 'Edit' button did not appear for my Remote Site after synchronising. It only appeared after closing the app and logging out and in again.
Expected behaviour 馃
The button should appear for Remote Sites straight after synchronisation, not after logging out and in again.
How to Reproduce 馃敤
Steps to reproduce the behaviour:
Have your Central Server set up and a Remote Site to test
Initialise GAPS on Central Server
Go to your Remote Site -> make sure you are logged in prior to testing -> synchronise
See the issue - the 'Edit' button does not appear
Log out and in again
See the 'Edit' button appear now
Your environment 馃尡
Open mSupply Version: V2.1.0-RC3
Legacy mSupply Central Server Version: V7.15.05
Platform: Desktop App on Windows (Central Server) & Galaxy A8 Tablet app (Remote Site)
Database type: SQLite3
The text was updated successfully, but these errors were encountered:
Going to close this one - its similar to the discussion in #3696, but I think even more edge case...
When remote syncs, we don't invalidate any data (though we are working towards this design eventually) - so the footer doesn't immediately know to update.
However, you don't even need to log out and in again, just navigating to another page seems to do it for me. Given it's a one time set up, I don't see this being an issue, and may be resolved in future with some kind of post-sync invalidation step
What went wrong? 馃槻
After initialising GAPS on Central Server, I noticed the 'Edit' button did not appear for my Remote Site after synchronising. It only appeared after closing the app and logging out and in again.
Expected behaviour 馃
The button should appear for Remote Sites straight after synchronisation, not after logging out and in again.
How to Reproduce 馃敤
Steps to reproduce the behaviour:
Your environment 馃尡
The text was updated successfully, but these errors were encountered: