Support of submit buttons

Engines
1

Hi,

in [A12-10056]<INTERNAL_LINK> the following question was raised:

Is there any reason to continue to support submit buttons? […] I think they (the submit buttons) are obsolete.

Cheers

2

Hi,

here is the result of a conversation with Ansgar W. regarding this question:

For submit buttons, there already exist default handlers on client side which makes them easier to use.
Contrary to that, event buttons require customized handlers matching the corresponding event. These customized handlers need to be created and implemented by each project individually.
Thus, creating an event button with the event “submit” will require more effort on developer side than just using the submit button. Therefore, it is not planned to drop the support of submit buttons.

Cheers

3

Thanks for the clarification
An event with the name event_submit, among others is already supported by CRUD.
I would suggest to document which submit names shall not be used for custom(!) events . To me its seems that these are those mentioned in the CRUD documentation, or some more?
I propose that these shall be prohibited for custom events to avoid confusion and name clashes.
Note moreover, that in the BAP CRUD documentation the term of event -not submission- is used:
<INTERNAL_LINK>
Some clarification on that would help at least for novices. Thanks