-
Notifications
You must be signed in to change notification settings - Fork 686
Description
Why do you need this change?
For one of our customer, we need to apply different dimensions in entries created by a transfer order. Dimensions are different between "Transfer-from Code" and "Transfer-to Code". We have to fluidify the process and skip confirmation dialog for their automated process.
Describe the request
In the procedure below, we would like to have an event before the confirmation dialog with a "IsHandled" parameter to be able to skip this confirmation dialog.
/// <summary>
/// Confirms the change of dimensions for an already shipped transfer line.
/// </summary>
/// <returns>Returns true if the change is confirmed, otherwise false.</returns>
procedure ConfirmShippedDimChange(): Boolean
begin
--------> START OF THE MODIFICATION
isHandled := false;
OnBeforeConfirmShippedDimChange(Rec, isHandled);
if isHandled then
exit(true);
--------> END OF THE MODIFICATION
if not Confirm(Text012, false, TableCaption) then
Error(Text013);
exit(true);
end;
Alternatives Evaluated
I tried to test to update directly dimensions on transfer header, but it didn't work as I wanted. The only way to perform what we want to do is to use this path of code.
Performance Considerations
Our customer is using this kind of transfer a lot of times per day (it could be between 30-50 times).
Data Sensitivity Review
This event is just asked to skip a dialog window, it will not expose sensitive data.
Multi-Extension Interaction
The only risk is to reactivate the dialog window when it should be deactivated for an automatic process. I suggest keeping the isHandled property set to true if it has already been set to true once.
Thank you
Internal work item: AB#616638