You can define an activity workstep (in a BPM process) with presentation type as GUI to complete the activity using a GUI for .NET desktop application. As the activity runs a GUI for .NET desktop application, you must develop a OpenEdge GUI for .NET application. Then, you must map the GUI for .NET application name (ABL class .cls filename) to the activity workstep (in a BPM process) to access the activity.
Note: For more information on developing OpenEdge GUI for .NET applications, see the OpenEdge Getting Started: Introducing the Progress Developer Studio for OpenEdge Visual Designer guide.
To define a GUI for .NET presentation for a workstep:
1. Select an activity workstep in a BPM process for which you want to define the presentation type as GUI.
2. From the Properties view, click the General tab to view the Presentation section.
3. Click Add to open the Presentation Types dialog box.
4. Select GUI from the Type drop-down list.
5. Specify an ABL class (.cls) file in the Name field. For example, SampleApp.cls.
Alternatively, you can map workstep with GUI presentation format to CHARACTER dataslot to dynamically associate the workstep with an ABL .cls filename. You need to set the initial value of the CHARACTER dataslot to a valid ABL .cls filename.
a. Click the ellipsis button beside the Name text field.
b. Select Use a dataslot to open the Add Dataslots dialog box.
c. Select the CHARACTER dataslot from the Add Dataslots dialog box.
d. Click OK to add the dataslot and then close the Add Dataslots dialog box.
6. Click OK to add the Mobile presentation format for the activity workstep.
Note: You cannot add the same presentation type twice to one activity workstep. If you do, an error message appears stating that the Presentation Type already exists. Do you want to override?. Click OK to override the presentation type.
The GUI presentation format is mapped to the selected activity workstep. The defined GUI presentation type is displayed in the Presentation section.
Note: You can add multiple presentation types such as Portal, Mobile, GUI, and Tablet to a single activity workstep. This enables you to complete an activity from a browser, a Mobile device, a GUI for .NET application, or a Tablet device.
