Zoltan_Gyimesi
Legendary Poster
Hi JDEList/Forum,
I copied P4114 appl to a custom one, to prepare it for automated upload.
My main screen call W4114A Inventory adjustment through the Add button of the W4114B Work With form, to call the Headerles/Detail form in ADD_MODE.
I load the fields on the Header(less part of the Form and load the grid with some record. After I done, I press the OK button from Event Rule.
The problem is that the ER of OK does not started at all.
When I build the debug info in OW debugger and started the debugger before to call my APPL, then it works fine.
I already tried everything, eg.:
- removed all asynch executions
- marked the form to "End form on add"
- I call the OK two times to skip Warnings
- I repeat the ER logic of Cancel events on the end of Post OK (marking the BSFN call to Include transaction)
- I place my logic into several place together and splited too
- I move all Async event logic onto the end of In-Line events
- created a work table inserting record for all events which will be run (separately for rows) when I insert grid buffer. I also insert record into WF in In-Line event. I delete the appropriate record at the and of the event. Tried to check the table several modes, inside the form, in a called outer form, etc. (all WF manipulation are encapsulated into a single BSFN)
- I added Wait x Seconds before and after check the WF
- I created a form in a separate APPL which "Find" the WF whilel it is not empty and returns when empty
- counting down the events and tried to check the counter
- marking the last inserted row and check when the event of it ends
...and tried several other
unfortunately without success.
If I do not run the debugger:
A.) then the OK does not started
B.) Or the APPL hangs up on a dead-lock loop.
I have to call this copied APPL and some more copied Inventory APPL in a loop and do not pass the control to the user while Error does not occur or the process ends.
Building debug info and run the debugger before starting the APPL is not an end-user friendly solution and it is not really an appreciatable solution. However starting the debugger is automated in the current state.
Any idea, tip will be highly appreciated.
Regards,
Zoltán
I copied P4114 appl to a custom one, to prepare it for automated upload.
My main screen call W4114A Inventory adjustment through the Add button of the W4114B Work With form, to call the Headerles/Detail form in ADD_MODE.
I load the fields on the Header(less part of the Form and load the grid with some record. After I done, I press the OK button from Event Rule.
The problem is that the ER of OK does not started at all.
When I build the debug info in OW debugger and started the debugger before to call my APPL, then it works fine.
I already tried everything, eg.:
- removed all asynch executions
- marked the form to "End form on add"
- I call the OK two times to skip Warnings
- I repeat the ER logic of Cancel events on the end of Post OK (marking the BSFN call to Include transaction)
- I place my logic into several place together and splited too
- I move all Async event logic onto the end of In-Line events
- created a work table inserting record for all events which will be run (separately for rows) when I insert grid buffer. I also insert record into WF in In-Line event. I delete the appropriate record at the and of the event. Tried to check the table several modes, inside the form, in a called outer form, etc. (all WF manipulation are encapsulated into a single BSFN)
- I added Wait x Seconds before and after check the WF
- I created a form in a separate APPL which "Find" the WF whilel it is not empty and returns when empty
- counting down the events and tried to check the counter
- marking the last inserted row and check when the event of it ends
...and tried several other
unfortunately without success.
If I do not run the debugger:
A.) then the OK does not started
B.) Or the APPL hangs up on a dead-lock loop.
I have to call this copied APPL and some more copied Inventory APPL in a loop and do not pass the control to the user while Error does not occur or the process ends.
Building debug info and run the debugger before starting the APPL is not an end-user friendly solution and it is not really an appreciatable solution. However starting the debugger is automated in the current state.
Any idea, tip will be highly appreciated.
Regards,
Zoltán