Created on 2018-09-18.18:49:24 by ced, last changed 30 months ago by reviewbot.
> Why not issue a message that explains that nothing is to pay? We are not allowed to raise error message on on_change call. And more over it is bad for the workflow such interruption.
I would like to receive some feedback for this proposal.
Why not issue a message that explains that nothing is to pay?
Currently when the user select an invoice on a statement line that is already paid, the invoice field is unset directly. This can astonish the user because he may think its input was not taken. Instead of this behavior, I propose to behave like when a line overpay an invoice. This means split the line one with zero amount and link to the invoice and the other with the amount and no link. This way the user will understand that his input was taken and there is nothing to pay.
|2018-12-29 14:40:42||reviewbot||set||messages: + msg45593|
|2018-10-27 16:30:06||ced||set||messages: + msg44640|
|2018-10-27 13:32:18||ced||set||messages: + msg44630|
|2018-10-17 15:06:43||reviewbot||set||messages: + msg44442|
messages: + msg43963
|2018-09-18 19:55:48||reviewbot||set||messages: + msg43943|
messages: + msg43941
|2018-09-18 19:28:11||ced||set||superseder: + Add via on_change does not link to the group|
|2018-09-18 19:23:46||ced||set||status: in-progress -> testing|
keyword: + review
Showing 10 items. Show all history (warning: this could be VERY long)