Looking for opinions - Is there any reason that we could not test for a transaction being in process using the idlehandler to catch poor coding.
I am thinking about something like
Get_Attribute DF_TRAN_COUNT to iRetval
If iRetval - then raise an error that this situation should not happen and indicates a code error/somethings broken.
Since the DF doc says you should not have user input (UI activity) in a transaction this may be something that should be added to the runtime?