Skip to content
This repository has been archived by the owner on Dec 13, 2020. It is now read-only.

Handle websocket document stale event #1084

Closed
teosarca opened this issue Jul 26, 2017 · 3 comments
Closed

Handle websocket document stale event #1084

teosarca opened this issue Jul 26, 2017 · 3 comments

Comments

@teosarca
Copy link
Member

teosarca commented Jul 26, 2017

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:

{
	"windowId":540354
	"id":2156425
	"stale":true
}

Steps to reproduce

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:
image


required for metasfresh/metasfresh#2066

@teosarca teosarca added this to the Backlog milestone Jul 26, 2017
@Dunkat
Copy link
Contributor

Dunkat commented Jul 27, 2017

@teosarca could you provide password fot user "it"? Needed for

login with user "it" (important)

@teosarca
Copy link
Member Author

@Dunkat provided privately

teosarca added a commit that referenced this issue Jul 28, 2017
Handle websocket document stale event #1084
metas-ts added a commit to metasfresh/metasfresh that referenced this issue Jul 31, 2017
[#1052](metasfresh/metasfresh-webui-frontend-legacy#1052) Breadcrumb of "Sales Opportunities" board is incorrectly
[#1078](metasfresh/metasfresh-webui-frontend-legacy#1078) Wrong quickActions call when opening HU editor
[#1094](metasfresh/metasfresh-webui-frontend-legacy#1094) Error on document websocket event
[#1084](metasfresh/metasfresh-webui-frontend-legacy#1084) Handle websocket document stale event

me-45
@metas-lc
Copy link

IT

  1. Businesspartner B2C -> actions -> create request
  2. set summary and date, ok
    => bpartner was directly updated with that date (didn't have to refresh) OK

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants