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

M_ReceiptSchedule.QtyToMove not properly updated on reopen #315

Closed
metas-ts opened this Issue Aug 22, 2016 · 0 comments

Comments

Projects
None yet
2 participants
@metas-ts
Member

metas-ts commented Aug 22, 2016

No description provided.

@metas-ts metas-ts self-assigned this Aug 22, 2016

metas-ts added a commit that referenced this issue Aug 22, 2016

metas-ts added a commit that referenced this issue Aug 24, 2016

Merge pull request #317 from metasfresh/FRESH-608-gh315
FRESH-608 #315 extend model interceptor to make the update at the right time

metas-ts added a commit that referenced this issue Aug 24, 2016

metas-ts added a commit that referenced this issue Aug 31, 2016

FRESH-608 #315 ReceiptSchedule.QtyToMove not properly updated on reopen
* fix ifColumnschanged of C_OrderLine_ReceiptSchedule MI.
* fix saving of the receipt schedule during close and reopen.
* add a bunch of comments and javadocs.
* rename IReceiptScheduleQtysHandler to IReceiptScheduleQtysBL, because 
when it sais "handler", i generally think "SPI" (hoping not to confuse 
others with this rename).
* do minor stuff like fixing typos and removing obsolete prepareIt() 
implementation.

metas-ts added a commit that referenced this issue Sep 1, 2016

Merge pull request #345 from metasfresh/FRESH-608-gh315
FRESH-608 #315 ReceiptSchedule.QtyToMove not properly updated on reopen

metas-ts added a commit that referenced this issue Sep 1, 2016

@metas-lc metas-lc closed this Sep 6, 2016

metas-mk added a commit that referenced this issue Feb 20, 2017

Update ReleaseNotes.md
Add Issue #315 Quick action button layout is broken on smaller resolution to our new upcoming release this week 4.57.56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment