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
{{ message }}
This repository has been archived by the owner on Dec 13, 2020. It is now read-only.
Atm frontend reacts to websocket events which are about stale tabs.
It was implemented in #795.
In that message, now we introduced another property called "stale" (boolean).
If that property is set and it's true, the fontend shall refresh that document (only the header and not the included tabs, if that's not mentioned in the event).
So, the JSON which is sent via websocket might look something like:
Fill the request (see screenshot, those highlight are important)
When the request is saved (it should be already) an websocket event will be send to refresh the bpartner.
After refreshing the BPartner, you will remark that the date you filled in request is now in BPartner:
Type of issue
Feature request
Current behavior / Expected behavior
Atm frontend reacts to websocket events which are about stale tabs.
It was implemented in #795.
In that message, now we introduced another property called "stale" (boolean).
If that property is set and it's true, the fontend shall refresh that document (only the header and not the included tabs, if that's not mentioned in the event).
So, the JSON which is sent via websocket might look something like:
Steps to reproduce
login with user "it" (important)
open following "Businesspartner B2C": https://w101.metasfresh.com:8443/window/540354/2156732
Actions -> Create request:
Fill the request (see screenshot, those highlight are important)
When the request is saved (it should be already) an websocket event will be send to refresh the bpartner.
After refreshing the BPartner, you will remark that the date you filled in request is now in BPartner:
required for metasfresh/metasfresh#2066
The text was updated successfully, but these errors were encountered: