Customizing input and output forms

Business Process Choreographer Explorer is a Web client for working on business processes and human tasks. The Web client provides default input and output forms for displaying and entering business data. You can use JSP documents to customize these default input and output forms.

Why and when to perform this task

To include user-defined JavaServer Pages (JSP) documents in the Web client, you must specify them when you model a human task in WebSphere Integration Developer. For example, you can provide JSP documents for a specific task and its input and output messages, and for a specific user role or all user roles. At runtime, the user-defined JSP documents are included in the user interface to display output data and collect input data.

The customized forms are not self-contained Web pages; they are HTML fragments that Business Process Choreographer Explorer imbeds in an HTML form, for example, fragments for labels and input fields.

When a button is clicked on the page that contains the customized forms, the input is submitted and validated in Business Process Choreographer Explorer. The validation is based on the type of the properties provided and the locale used in the browser. If the input cannot be validated, the same page is shown again and information about the validation errors is provided in the messageValidationErrors request attribute.

To add customized forms to Business Process Choreographer Explorer, complete the following using WebSphere Integration Developer.

Steps for this task

  1. Create the customized forms.

    The user-defined JSP documents for the input and output forms used in the Web interface access message data. Use Java snippets or the JSP execution language to access the business data from the request context.

  2. Assign the JSP documents to a task.

    Open the human task in the human task editor. In the client settings, specify the location of the user-defined JSP documents and the role to which the customized form applies, for example, administrator. The client settings for Business Process Choreographer Explorer are stored in the task template. At runtime these settings are retrieved with the task template. For more information about adding JSP documents to human tasks, see the WebSphere Integration Developer information center.

  3. Package the user-defined JSP documents in a Web archive (WAR file).

    You can either include the WAR file in the enterprise archive with the module that contains the tasks or deploy the WAR file separately.

Result

The customized forms are rendered in Business Process Choreographer Explorer at runtime.


Terms of use | | Broken links

Last updated: Tue Dec 06 04:14:42 2005

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)