Dialog and CONFIRM messages about alappextensions HOT 4 CLOSED

Somewhat related: You hit the same problem with WebServices (it least I am not aware of a workaround). To solve that we built a "framework" which identifies the CONFIRM and asks the caller to make a decision by calling the same method again with a default. Quite ugly and of course dependent on knowing the implementation, so it would be very much appreciated if you could come up with a solution for that as well

from alappextensions.

Thank you for your suggestion! It will require a bigger, coordinated effort, where we locate every place where such construct exists. Also, as a CONFIRM dialog presents a choice and a resulting code path, we would have to define the default behavior of the system. If you currently are blocked by a specific behavior, please create a new issue addressing the exact requested change and we can look at a more isolated fix. I have added the total effort to our backlog to be prioritized against other workload. Thank you again for your suggestion!

from alappextensions.

from alappextensions.

Also somewhat related: STRMENU

I think all occurrences of CONFIRM, STRMENU, ... should be minimized as much as possible or replaced by defined actions and functions. i.e:

• All CONFIRMS asking thinks like "...do You want to continue..." should default to YES if there is no GUI
• All STRMENU should be dropped in favour of actions (Post... to then ask me next if I want to ship, invoice, ship + invoice... -> Better add actions to Ship, Invoice, ...)

from alappextensions.