Maintaining Plug-Ins and Opening a Structure: Workflow 
Prerequisites
You have created a form with Visual Basic.
You have either defined a single-step task to be executed as a form and copied this task to your workflow definition or have defined a single or multistep task that is to be started by a form.
You have launched the
SAPforms Designer as a Visual Basic add-in and are in the main window. The form controls are shown in the table displayed in the bottom control.
The procedure described below is the same if you are using the
Procedure
Maintain Plug-Ins
The Options dialog box of the SAPforms Designer is then displayed.
Enter
SAPforms Data Plug-In for Workflow in the Active Plug-In field in the SAP Forms Data Plug-In box.
The value in the SAPforms Plug-In box is set by default according to the form development environment you are using. If you are using the stand-alone version of the SAPforms Designer, you must also maintain this plug-in.
Communication Plug-Ins |
| SAPforms Transmit Plug-In for RFC |
| SAPforms Transmit Plug-In for MAPI |
| SAPforms Transmit Plug-In for SMTP via WinSock |
Once it has been processed, the work item can communicate with the R/3 System either synchronously via RFC or asynchronously via mail. The same applies to starting a task. The decision is made by choosing the appropriate communication plug-in.
Note that certain default settings must be defined so that you can exchange data via mail. For more information, see
SAPforms Administration.The Workflow Task Description entry has been added to the File menu in the main window of the SAPforms Designer
Opening a Structure
The SAPforms RFC Logon - System Selection dialog box is then displayed.
You can find out which R/3 Systems you are already logged on to on the tab page Recent. You can also select an existing logon.
The Select (Workflow) Task dialog box appears.
You can search for a workflow in R/3 by using the pushbutton Search in the Search area. Enter the task code in the field Search Key.
Result
The container definition for this task is exported from R/3 and displayed as a tree in the top control of the main SAPforms Designer window. You can now
define the binding.