Defining user interfaces for a human task

IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing business processes > Building human tasks > Set up a user interface for your human task
Defining user interfaces for a human task

In the Human Task editor, you can select the type of client, and configure properties such as inputs and outputs for the client.
You can specify existing configurations, or define new ones. You can then generate a client.

Procedure
Open your human task in the editor.
Under User interface settings, choose the type of client.
In the Properties page, configure the client as follows:
Option Description
HTML-Dojo client for Process Portal spaces
Use the Context root and HTML File fields to specify the location of the HTML file that contains the visualization of the user interface. These fields are used to compose the URL from which your HTML file is uploaded using the following format:
http://localhost/ contextroot/ pathAndFile
If no HTML file exists, you can click New to create one. In the New HTML file window, you can choose an existing web project for the new HTML file, or click New Web Project to create one.
Tip: Modify the HTML file by using a text or HTML editor.
IBM Forms client (deprecated for IBM Integration Designer in IBM BPM V8.0.1)
Select whether to store your IBM forms as part of the current module or in a web project. The default behavior is to save the form as part of the module. If you want to use a form that exists outside the module, or you want to create an IBM Form for use outside the module then select web project.
Specify the input and output IBM Forms for your client. If your input and output data is identical, the input and output forms must also be the same.
If no input or output forms are specified in this page, the client generator uses the service interface data to create the forms.
If you want to edit a form, install Lotus Forms Designer. See IBM Forms Viewer.
Select whether to save the form automatically whenever the human task is saved or completed. This setting applies only to IBM Forms clients. If you deploy your IBM Form to Process Portal, the form cannot be persisted.
WebSphere Portal client
Every human task must be identified by a unique name when it runs as a portlet on the WebSphere Portal Server. Later create a page in the Portal Server of the same name as this unique name and place this generated portlet into it.
In the Properties details page, proceed as follows:

Provide a value for Unique Name. If you leave this field empty IBM Integration Designer generates a unique name when the portlet is created.
Select the type Page or Page definition.
Click Create Portlet to generate a portlet for this task. In the Portlet Generator Settings page, specify the project and select WebSphere Portal 6.0 stub as the target run time. If the WebSphere Portal target run time is not available in this window, the required Portal Toolkit is not installed. See Installing WebSphere Portal Version 6.0.
Create Portlet generates a portlet for this human task. If you want to generate a portlet for multiple human tasks, use the client generator.

Business Process Choreographer Explorer With this option, the task is delivered to the staff member via an HTML-based web page. In the JSP definition table, specify the input and output JSPs.

Click Add.

On the JSP definition page, select the JSP type. In the Apply to field, select the role that sees the JSP. You can then create a JSP, or browse to an existing one, and use the Context root field to define the runtime path to the JSP.
If you have WSDL faults defined in your interface, you can select a Fault message JSP as the JSP type, and then select the fault that triggers it.

If no JSPs are specified, the standard client is used.
The JSF custom client is not included in this list because the client generator does not require any properties to be configured in order to generate the client.
If you are using Business Process Choreographer Explorer, you do not need to generate a client, as a standard client is provided for it.
What to do next
Generate your client.

Set up a user interface for your human task

Related concepts:
Before you begin: Client types and prerequisites

Related tasks:
Generate HTML-Dojo pages or IBM Forms for Process Portal spaces
Integrating JavaScript in HTML-Dojo pages
Generate IBM Forms clients (deprecated)
Generate WebSphere Portal portlets
Generate JSF clients for your human tasks
Prepare to extend generated JSF code
Customize clients
Deploying a generated client to an external runtime environment
Adjusting the Unique Name for the Task Page

Related reference:
Design considerations for user interface generation

Option	Description
HTML-Dojo client for Process Portal spaces	Use the Context root and HTML File fields to specify the location of the HTML file that contains the visualization of the user interface. These fields are used to compose the URL from which your HTML file is uploaded using the following format: http://localhost/ contextroot/ pathAndFile If no HTML file exists, you can click New to create one. In the New HTML file window, you can choose an existing web project for the new HTML file, or click New Web Project to create one. Tip: Modify the HTML file by using a text or HTML editor.
IBM Forms client (deprecated for IBM Integration Designer in IBM BPM V8.0.1)	Select whether to store your IBM forms as part of the current module or in a web project. The default behavior is to save the form as part of the module. If you want to use a form that exists outside the module, or you want to create an IBM Form for use outside the module then select web project. Specify the input and output IBM Forms for your client. If your input and output data is identical, the input and output forms must also be the same. If no input or output forms are specified in this page, the client generator uses the service interface data to create the forms. If you want to edit a form, install Lotus Forms Designer. See IBM Forms Viewer. Select whether to save the form automatically whenever the human task is saved or completed. This setting applies only to IBM Forms clients. If you deploy your IBM Form to Process Portal, the form cannot be persisted.
WebSphere Portal client	Every human task must be identified by a unique name when it runs as a portlet on the WebSphere Portal Server. Later create a page in the Portal Server of the same name as this unique name and place this generated portlet into it. In the Properties details page, proceed as follows: Provide a value for Unique Name. If you leave this field empty IBM Integration Designer generates a unique name when the portlet is created. Select the type Page or Page definition. Click Create Portlet to generate a portlet for this task. In the Portlet Generator Settings page, specify the project and select WebSphere Portal 6.0 stub as the target run time. If the WebSphere Portal target run time is not available in this window, the required Portal Toolkit is not installed. See Installing WebSphere Portal Version 6.0. Create Portlet generates a portlet for this human task. If you want to generate a portlet for multiple human tasks, use the client generator.
Business Process Choreographer Explorer	With this option, the task is delivered to the staff member via an HTML-based web page. In the JSP definition table, specify the input and output JSPs. Click Add. On the JSP definition page, select the JSP type. In the Apply to field, select the role that sees the JSP. You can then create a JSP, or browse to an existing one, and use the Context root field to define the runtime path to the JSP. If you have WSDL faults defined in your interface, you can select a Fault message JSP as the JSP type, and then select the fault that triggers it. If no JSPs are specified, the standard client is used.