Dashboard View: Rework concept for freshing data in the frontend after triggering partner update

[Clemens-L-Schwarz]

As a PURIS FOSS User ,
I want to have the data updated after hitting the refresh button ,
so that I can see the latest data retrieved without any further ado.

Hints / Details

• Currently after the refresh button the data does not get updated in the frontend
• It only triggers the update
• A user has to go back and forth in the application, e.g. switch roles from customer to supplier to get the data refreshed in the frontend
• that is unsuitable from a UX perspective

Outcome / Acceptance Criteria

Outcome

• triggering a data update will lead to updated data in the frontend
• the customer is aware that new data is getting fetched
• no further clicks required for the user to see the updated data

Acceptance Criteria

• using the refresh data button triggers and data update
• there is a mechanic that lets the user now that data is currently getting fetched, e. g. loading spinner
• concept for what will happen when the data fertching takes very long / time out criteria
• concept for what the user can see in the meantime, e.g. old data or skeleton load
• concept for what happens when data fetching fails or times out: How to proceed? Message to user and show last available data?

Out of Scope

• ...