it has not been implemented yet.
The aim is to be aware of the increased prices, as the yellow hint box might be ignored.
Issue 368 is also about duplicating but that one is customer related with the category.

it has not been implemented yet. The aim is to be aware of the increased prices, as the yellow hint box might be ignored. Issue 368 is also about duplicating but that one is customer related with the category.

maxi commented

2022-11-26 11:04:10 +01:00

(Migrated from gitlab.weber-bodman.de)

..so your issue is that an active confirmation SHALL BE there (you don't issue that there already is such thing...).

...and by "process" you mean "order".

So exactly WHAT shall be confirmed actively?

..so your issue is that an active confirmation SHALL BE there (you don't issue that there already is such thing...). ...and by "process" you mean "order". So exactly WHAT shall be confirmed actively?

maxi commented

2022-11-26 11:07:36 +01:00

(Migrated from gitlab.weber-bodman.de)

Please just describe how you want it to have, e.g.:

When a user duplicates an outgoing order with outdated prices (supplier scenario) there should be an additional prompt to ensure that the user is fully aware of the worsened purchasing conditions and their implication (explicitly!).

Please just describe how you want it to have, e.g.: When a user duplicates an outgoing order with outdated prices (supplier scenario) there should be an additional prompt to ensure that the user is fully aware of the worsened purchasing conditions and their implication (explicitly!).