In SAP NetWeaver Business Process Management, you can consume and integrate different user interfaces (UI) in your processes as human activities. The human activity illustrates an activity that triggers a task. This task is executed by a human. The interaction between a human and the process is enabled through a UI. The UI assigned to a task allows the user to access and execute that task.
A UI serves a process like a Web service. Input data that is used, for example, for simple prefilling, is provided from the process to the user interface and after a human interaction, output data is returned to the process. For process development this is similar to an automated activity consuming a Web service or an RFC.
In a BPM process, you can consume UIs of the following technologies:
Web Dynpro for Java (WDJ) (see Developing Java Web Dynpro Applications , Preparing Web Dynpro for Java DC to be used in BPM )
Web Dynpro for ABAP (WDA) (see Creating CHIPs on SAP Help Portal under)
Visual Composer (VC) (see Modeling Composite Views with Visual Composer )
You can import an existing UI component or easily generate a UI component that matches the process context.
Importing an Existing User Interface
In the process composer, the SAP NetWeaver BPM design time, you can browse or search user interface components.
In the Process Development perspective, you can assign a UI to a task. The UI Import Wizard guides you through the UI consumption process. For more information, see Assigning a User Interface to a Task .
Instead of assigning a Web Dynpro or Visual Composer UI, which are called online technologies, you can also assign an offline form to a task. For more information, see Using Adobe Offline Forms and Assigning an Offline Form to a Task .
Generating a User Interface
When you are modeling a process including human activities, the corresponding UI components are not necessarily available. To be able to continue with modeling the process and afterwards to test the process model, you can automatically generate UI components that match the process context. To do this, you use the WDJ or VC technology. The necessary dependencies from the DC containing your process and the DC containing the generated UI components are automatically configured. In case of interface definition changes, all BPM artifacts are checked against their dependencies at build time. For more information about UI generation while modeling, see Generating a UI Component for a Single Task .
You can also generate tasks and UI components for your process with the UI Task Generation template. For more information, see Generating Tasks and UI Components with UI Task Generation Template .