Disable X Button on SAP Forms
Not plannedHello,
There is an ongoing challenge that maybe a new feature will solve it.
Superuser can create validation that stops user from updating / adding data.
This option cannot be used if the user make a change on a form
and instead of pressing the ADD / UPDATE button $[$1.0.0] (that will activate the validation)
the user press the X (exit form) button that showing a question if the user wants to save the changes that he made.
If he presses yes - the changes are saved and he bypass the validation.

Is it possible to disable / cancel / add new type of item that solve this issue and it cannot be possible to press the X botton?
Thanks, Stas.
-
I dont think you can, because a new window also starts in ADD mode, so you would basically end up never able to close your screen.
-
Thank you for your request. It has been scheduled for review by the development team that will get back to you should there be questions.
(Please note that as we are user-driven we can't guarantee that your request will be met unless it gets many votes and/or fit the product vision)
Read more about the Feature Request process here
[Internal Id: 57923] -
@Ramon Duunk You are right - Which means it is not possible to be able 100% validate certain forms.
Maybe the solution is UI change or UI item disabling feature.
-
Hi Stas
SAP's SDK does unfortunately no event to catch the X button event :-( ...
What you instead need to do is instead of catching the Item Preseed on Item 1, You need to use the DataAdd or DataUpdate events in B1 Validation System... These will trigger no matter if something is added/update via the button or the X-button

-
Have you tried to use the validation in the ADD/UPDATE event instead of on the click of $[$1.0.0]?


-
Thanks every one for the quick response.
Unfortunately the Data add/Data Update option not triggered when I save the changes after pressing the X button, it's saving the changes although they not valid :(
-
Hi Stas... Your right... Seems SAP did something non-standard here (it should have fired the event but not the first place I see them not following their own rules) :-(
I'm afraid in this specific scenario there is nothing to be done (The SDK simply do not allow it)
-
Hey Rasmus,
Thank you for the answer.
Hope you guys will find a solution and we will see it on your next update release video 😏
Stas
-
Thank you for the fate in us :-)... But without SAP enhancing the SDK I'm afraid there is little we can do :-(
Please sign in to leave a comment.
Comments
9 comments