New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

view attributes shall be refreshed when the current selected row is refreshed #1367

Closed
teosarca opened this Issue Nov 21, 2017 · 1 comment

Comments

Projects
None yet
4 participants
@teosarca
Member

teosarca commented Nov 21, 2017

Is this a bug or feature request?

bug
issue required for metasfresh/metasfresh-webui-api#696

What is the current behavior?

Which are the steps to reproduce?

  • go to material receipt candidates: https://w101.metasfresh.com:8443/window/540196
  • click on default receive action (e.g. 24 IFCO 6410 x 10 Stk)
  • the HU modal is opened
  • remark that first row is selected and the attributes on the right side are editable => OK
  • call the "Create material receipt" action
  • the HU is processed and turns to gray (not editable) => OK
  • but the attributes are still editable => NOK => they shall be refreshed (see below)

image
image
image

What is the expected or desired behavior?

Whenever:

  1. the whole view is refreshed because of a websocket event (but not necessary) and there is a row selected and that row has attributes => refresh the attributes too
  2. if some rows are refreshed because of websocket event or not and one of those rows is actually the current selected row which has attributes => refresh the attributes too

When developing this, please also consider #1357

wiadev added a commit that referenced this issue Nov 30, 2017

teosarca added a commit that referenced this issue Nov 30, 2017

Merge pull request #1395 from metasfresh/dev-1367
Reload selectedAttribute upon the message of WS #1367

metas-ts added a commit to metasfresh/metasfresh that referenced this issue Dec 1, 2017

update releasenotes.md
[#2177](#2177) New Window
for Attribute Search in WebUI
[#3117](#3117) Disable
MStorage.add
[#1357](metasfresh/metasfresh-webui-frontend#1357)
Don't use the legacy view attributes API
[#1367](metasfresh/metasfresh-webui-frontend#1367)
view attributes shall be refreshed when the current selected row is
refreshed
[#3041](#3041) Forecast
Window copy Field content from header to lines when creation
[#3040](#3040) Implement
Clone/ Copy for Forecast Window WebUI
[#1360](metasfresh/metasfresh-webui-frontend#1360)
View field editor: override viewEditorRenderMode on row level
[#2868](#2868) Make
BOMValidate process to work correctly in webui
[#2956](#2956) drop
allowconsolidateinvoice from database
[#3073](#3073) Error:
Could not find or load main class ${argLine}
[#3072](#3072)
de_metas_purchasecandidate schema containing some diagnosis views
[#705](metasfresh/metasfresh-webui-api#705)
Backend Logic for new Date Filter Widget
[#3064](#3064) Multiple
PP Order generation for a materialdispo line
[#3088](#3088) Transform
in material receipt left destroyed HU behind
[#3086](#3086) HU planned
after Purchase Order, destroyed after material receipt
[#3089](#3089) Not able
to start report service with ReportServiceMain.launch
[#3042](#3042)
C_Bpartner: new Additional fields
[#3060](#3060)
TypedSqlQuery Bugs because aggregateList method ignores order
[#3054](#3054) purchase
candidates: document references

me-45
@metas-dh

This comment has been minimized.

Show comment
Hide comment
@metas-dh

metas-dh Dec 4, 2017

Member

Results of IT1
tested in mf15

attributes are correctly refreshed

  • attribute is correctly updated in TU when set for the LU: OK
  • attributes are read-only after the material receipt was created (HU is read-only): OK
Member

metas-dh commented Dec 4, 2017

Results of IT1
tested in mf15

attributes are correctly refreshed

  • attribute is correctly updated in TU when set for the LU: OK
  • attributes are read-only after the material receipt was created (HU is read-only): OK

@metas-dh metas-dh closed this Dec 4, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment