Event on close Browser to unlock Data

Question

Hi experts,
I have an OVP Floorplan and the problem is, that by closing the Browser, all Data Locks remain in SM12.
Is there an Event or Method called before closing the browser or how can I Unlock the Data?
I've red, that the Method WDDOINIT of the Application Component Controller is called, but how can I access this Method.
I have Feeder-Klasses for the UIBBs and an Assistance Class for the Application Component Contoller, but there is no Method WDDOINIT in this Assistance Class!
Thanks and regards,
Sebastian

Answer 1

Hello Sebastian,
I solved the browser close problem enhancing the class CL_FPM, to release locks/resources (since the exit event is not propagated from WD to FPM). To do this our own methods have to be called somehow before framework is releasing resources in method DELETE of class CL_FPM.
The steps required to reach this:
Create an enhancement of class CL_FPM
Add a new member table attribute f.e. mt_zzcallbacks table to class CL_FPM
Add a new public instance method f.e. zzregister_callback to class CL_FPM, to put any class instance and method to the table above, from your own classes.(Methods added should not contain any obligatory parameter and has to be of type instance public also)
Create a pre-exit of method delete of class CL_FPM and loop over the callback table calling the methods dynamically (catch the following exceptions: ABAP Keyword Documentation).
Put your code to release the locks/resources into the registered callback methods (it will be called exiting the application )
This works when user closes the browser/tab improperly.
Of course you can provide a possibility to close the application using a button, where you can do additional checks etc, data loss notification etc.
So if you use a Close button with event FPM_CLOSE (doing checks etc. ) and releasing your locks also handling the event  FPM_CLOSE, then you can create a new method in class CL_FPM to deregister the method from the callback table, since you did free already and not necessary to do it again using the callback.
Kind regards
Attila