Thank you for your question above. Unfortunately Formativ 2.0 does not provide step debugging facilities you describe. Including step debugging facilities for Formativ (which runs inside the GroupWise process) is a non-trival task. Nonethess, we know this is an important feature and has been slated for a future release.
In the meantime, you can use other techniques to approximate step debugging. Perhaps the most useful is to include trace output commands in your Applet, then use any debug output viewer capable of intercepting calls to the Win32 OutputDebugString() function.
Through the use of strategically-placed trace commands, you can get a real-time picture of the execution of your Applet. Trace commands are created through the use of the Utilities.Trace() method. Utilities.Trace() takes a single string argument. The string value you supply is output to any attached debugger in real time as the Applet executes.
Utilities.Trace() ultimately uses the Win32 function OutputDebugString() to output the string value. This function sends a string to the debugger for display. If GroupWise has no debugger attached, the system debugger displays the string. If GroupWise has no debugger and the system debugger is not active, OutputDebugString() does nothing. If you use the SysInternals DebugView utility, you only need to run DebugView prior to starting GroupWise – you do not need to attach it to the GroupWise process.
We use and recommend the free DebugView utility from SysInternals: http://www.sysinternals.com/ntw2k/freeware/debugview.shtml
I hope this helps.