Show TOC

Assigning a User Interface to a TaskLocate this document in the navigation structure

This dialog helps you to select an online or offline technology specific wizard to search and assign a UI component to the task. You can also view the input/output details of selected UI component context. The wizard also allows you to select a complete event from the UI component that will act as task complete event. Optionally, you can select error events that can be used as human activity boundary event.

Prerequisites

  • If you want to assign a WDJ UI task that is not created with the UI Task Template (see Generating Tasks and UI Components with UI Task Generation Template ), you first need to prepare the WDJ development component (DC) to be used by the process composer DC that contains your project with the process. For more information, see Preparing Web Dynpro for Java DC to be used in BPM .

  • You have configured the necessary development environment in the SAP NetWeaver Developer Studio .

  • Relevant in case you want to assign a WDA CHIP: You have configured the necessary connection to the back-end system from which you want the consume the WDA CHIP. The SAP NetWeaver Application Server for ABAP you connect to has to be of release 7.0 Enhancement Package 2 or higher. For more information about configuring R/3 destinations, see Creating RFC Destinations .

    Note

    The connection name you specify is used later to determine the remote system at runtime and must match the system alias you define in the portal.

    You can also see SAP Note 1442668 Information published on SAP site about the minimal required versions of your systems.

  • Relevant if you want to use WDA FPM: If you want to integrate WebDynpro ABAP Floorplan Manager (WDA FPM) user interfaces in SAP BPM, you need to use CHIP-enabled floorplans, specifically UCW. For more information, see FPM CHIP Integration.

  • You have created a task to which you want to assign the UI.

Context

In the process, 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 user interface (UI). The UI assigned to a task allows the user to access and execute that task.

This procedure shows how you assign a UI to a task. You can assign UIs of different technologies:

You can search for UI components in the WDJ and VC projects available in your workspace. When you assign a UI component to a task, a dependency between the Process Composer DC and the DC containing the UI component is automatically set.

If you want to assign a WDA CHIP, you search for it in the back-end system.

Procedure

  1. In the Developer Studio, choose Start of the navigation path Window Next navigation step Open Perspective Next navigation step Other... Next navigation step Process Development End of the navigation path and choose the OK pushbutton.
  2. Expand your project in the Project Explorer view.
  3. Expand Process Modeling , then expand Tasks.
  4. In the context menu of a task, choose Open.

    The task editor opens.

  5. Choose the Choose... pushbutton under User Interface on the Overview tab page.
  6. In the dialog that appears, select Online Technologies (Web Dynpro Java, Web Dynpro ABAP, Visual Composer) and then choose the OK pushbutton.
  7. Select the UI technology of the UI that you want to assign and then choose the Search pushbutton.

    To search for WD ABAP CHIP, select the system from which you want to search in the dropdown menu. The dropdown menu contains the R/3 destinations you have configured.

  8. In the Choose UI Component area, you can display only the supported UI components which you can use in your process, or all available UI components of the selected UI technology. When you switch the display option, the display is automatically refreshed.
  9. In the list of UI components, select the UI component you want to assign and then choose the Next pushbutton.
    Note

    You can have a closer look at the input and output data of the UI by expanding the UI component and selecting the input or output. The details of the selected input or output are displayed in the Input/Output Details area on the right-hand side.

  10. Select the event that completes the task from the Complete Event dropdown menu. In addition, you can select error events and assign boundary events for error handling to them. If the error event occurs during runtime, the task is set to an error state and is not completed.
  11. Choose the Finish pushbutton.

    The UI is assigned to the task.

    Note

    If you have assigned a WD ABAP CHIP to a task, you need to perform additional configuration steps at runtime to specify the remote system from which the UI is loaded. To do that, you specify the necessary system and system alias in the portal. The system alias you define in the portal must match the connection name you configured on the R/3 destinations preferences page.

    For more information about configuring systems in the portal, see Defining the System Landscape .

    In addition, you need to specify in the portal the following properties of the remote system:

    Property Name

    Value

    ICM host name

    <host name>:<port>

    ICM protocol

    http or https, depending on the ABAP back-end system

    Property Name

    Value

    Authentication Ticket Type

    <empty>

    Logon Method

    UIDPW

    User Mapping Type

    admin,user

    You also need to specify the user mapping for the remote system access. To do that in the portal, open the User Administration tab page. Find the user you are logged with in the portal and open the User Mapping for System Access tab page. Choose the Modify pushbutton and select your remote system. Specify the mapped user name and password and save your changes.

    Recommendation

    Use SSO instead of user mapping in a productive environment.

    For more information about configuring SSO and user mapping in the portal, see Single Sign-On to Back-End ABAP Systems .

  12. (Optional) If you have assigned a WDA CHIP to a task, you can change the system alias, derived by default from your configuration of R/3 destination with a new one if, for example, the system alias on the portal has changed.

    In this case, you do not need to reimport the WDA CHIP. You change the system alias in the System Alias field, which appears under User Interface after you assign the WDA CHIP.

    Note that the system alias can contain the following characters only: letters A-Z and a-z, numerals 0-9, period (.), underscore (_), percent sign (%), tilde (~), hyphen (-), and parentheses((...)).