The Human Task Management widgets use query tables to list
BPEL processes and human tasks. A set of default query tables is provided.
These query tables do not include filter criteria or solution-specific
business data, but you can create and deploy your own query tables
to include filters and solution-specific business data.
Before you begin
To create query tables, you need the Query Table Builder.
This Eclipse plug-in is available as SupportPac PA 71 from the WebSphere Business
Process Management SupportPacs site. Before you begin this task, ensure
that you download and install the Query Table Builder.
Procedure
- In the Query Table Builder, right-click your project, and
then click . Follow the wizard instructions to create a query table definition.
The new query table definition consists of the predefined properties. You
can add more properties to the query table definition. For example,
you can add query table properties for custom properties of human
tasks and BPEL processes, or query properties for BPEL process variables
that contain your solution-specific business data.
Important: The
names you give the properties in the Query Table Builder are used
as the names for the properties in the widgets. If you need to use
the query table in federated environments, ensure that the names comply
with the naming considerations for federated lists. If the widgets
are made available to your users in different languages, you can also
specify the translations of the property names in the Query Table
Builder.
- Deploy the query table definition file on a
process server.
- Configure the widgets in a Heritage Process Portal space
to use the query table definitions. For example, if you
deployed a query table definition file for the Tasks widget,
perform the following steps to configure the widget.
- Open the widget menu, select Edit Settings,
and then the Content tab.
- Click Add to open the Add
Lists window. The query table definition that
you deployed in step 2 should be available in this list
for selection.
- Save your changes to the widget configuration.
If the query table definition is not available, go back to the
Query Table Builder and check whether the definition file was correctly
defined and deployed.