A user has to return to the UWL for each step. How can they be executed together like in the SAPGUI?
The feature by which a user can execute multiple work items one after another without returning to the inbox is referred to as synchronous dialog chains and can be controlled by the “Advance With Dialog” checkbox in the workflow builder. As described in the note on limitations (see previous question), this is unfortunately a technological limitation: A user session cannot be maintained when different technologies are used for subsequent steps. A common example, is a decision step followed by an input box requesting a reason for rejection. The desision might be a Java-based iview, followed by a WinGUI step. A workarounds would be to ensure that all ‘chained’ steps are WinGUI-based (i.e. SAP Transactions or ABAP dialog modules). This is not always possible, particularly with ESS/MSS and similar applications which have pure web-based components.
Related Questions
- What are the checks that the SAP authorization tool performs when a TCODE is executed in order to ensure authorization of that user?
- A user has to return to the UWL for each step. How can they be executed together like in the SAPGUI?
- How does the user know that a particular block of code is being executed on a coprocessor?
