metasfresh / metasfresh-webui-api-legacy

metasfresh webui API server
GNU General Public License v3.0
30 stars 32 forks source link

Window Browse via viewID reload/ refresh #23

Open metas-mk opened 8 years ago

metas-mk commented 8 years ago

Imagine you open a window in Grid view (via navigation). You get a result of 100 rows distributed on 4 pages a 25 rows. Leave that window open like it is. Now create another row via the explicit window, so that a new refresh/ reload of that window in Grid view would respond 101 rows.

--> The already opened window should get the infomration that there is a new row and allow the user to load the new data. What i understood from REACT only the changed/ new data will be injected and presented and there is no need to reload the whole data.

Same "live data" functionality shall be used in dashboard. If relying data changes then the chart/ graph/ dashboard shall be updated, but only for the changed/ new data.

teosarca commented 8 years ago

This one relates to https://github.com/metasfresh/metasfresh-webui/issues/19

metas-lc commented 6 years ago

got to this task while testing https://github.com/metasfresh/metasfresh-webui-api/issues/19

  1. dashboard is fine, since it refreshes every few seconds OK
  2. grid view doesn't refresh on new entry: i opened product window in 1 tab window/140 (grid view) in another tab i opened product window again and created a new product - saved (as a name i chose one starting with "A" to get on first page) went back to first tab => my new product was not there NOK (it appears after you requery)

please fix in this task

metas-lc commented 6 years ago

another similar case:

  1. open bpartner window in a tab ( window 123)
  2. and open bpartner b2c window in another tab (window 540354)
  3. in both tabs, open same bpartner
  4. in b2c 540354 also open document subtab
  5. in bpartner window 123 add new attachments (you can also remove ones)
  6. go to b2c tab => subtab document is not updated NOK (you have to refresh)

note: it works if you make changes in 540354 window. So it's an 123 <-> 540354 window problem