Tutorial: Building a Worklist Application

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Tutorial: Overview

Java Process Definition (JPD) functionality available with BEA WebLogic Integration enables integration of diverse systems, applications, and human participants. WebLogic Integration Worklist enables people to collaborate as part of higher level business processes.

The Worklist subsystem enables human interaction with business processes. Worklist provides the capability to assign tasks to human users. Based on the assigned task, human users can perform actions on the tasks, which can trigger new task assignments to other users or system events. This process flow depends on the higher level business processes.

Some of the Worklist subsystem features include:

This chapter provides an overview of the tutorial and explains the business scenario on which this tutorial is based. It includes the following sections:


Tutorial Overview

This tutorial provides you step-by-step instructions to create a loan approval tracking system for a fictitious financial institution, Acme Financial System (AFS), using human interaction and system integration functionality available with Worklist.

Figure 1-1 illustrates the loan approval tracking system scenario that you will create during the course of this tutorial.

Figure 1-1 Loan Approval Tracking System Process Flow

Loan Approval Tracking System Process Flow

Following is the sequence of events illustrated in the preceding figure:

  1. A customer submits a loan request for an amount of $10,000 with AFS. Based on the process flow, the system routes this loan application to be reviewed by Loan Officers.
  2. The Worklist creates the loan task for this loan application. This task appears in the Inbox of all users who belong to the Loan Officers group.
  3. One of the Loan Officers (John) logs into the system, reviews the loan request, and claims it as his task.
  4. John assesses the loan request and decides to route to the group of Loan Managers for approval.
  5. Loan Manager Mary logs in and claims the loan task.
  6. Mary has the choice to approve or reject the loan. If she approves the loan, Worklist flags the task as complete and triggers an event, which is sent to the loan request system.
  7. If Mary rejects the loan, Worklist aborts the task and rejects the loan request.


Steps in This Tutorial

This tutorial provides you with detailed instructions to:

In the tutorial, these tasks have been structured and categorized into six steps. These are:

Step 1: Setting Up the Environment

The section details the steps required to set up the Worklist Design-Time environment (for modeling the target task plan), and the Worklist run-time environment (for running the application.) In addition, you will need to set up the users, groups, and business calendars.

Step 2: Modeling and Deploying the Loan Processing Task Plan

This section discusses how the loan processing task plan can be modeled to implement the business scenario and then be deployed on the WebLogic Integration server.

Step 3: Testing the Task Plan Using Worklist User Portal

The Worklist User Portal is provided out of the box to allow different human users to work on the task instances. A loan processing task can be created and worked on to completion by many users through the Worklist User Portal.

Step 4: Managing Task Instances Using Worklist Console

In this section, the administrator uses the Worklist Console to look at the overall statistics of the loan processing task instances. In addition, the administrator reassigns some task instances because the assigned employee has left the company.

Step 5: Using JPDs with Worklist

In this section, the loan processing requests come from an online system that triggers a JPD business process, which creates the task instance.



This section describes the conventions used in the text and code examples of this tutorial. Table 1-1 lists the meaning and examples for different text and code conventions.

Table 1-1
Bold typeface indicates terms on which users perform actions.
Click Next to proceed with the Configuration Wizard.
Italic typeface indicates names of processes.
Because the task instance, Car loan for Maggie May, is assigned to the loanOfficers group, it will show up on the Assigned Tasks portlet of John's Inbox.
Code typeface indicates names of files, directories, steps, and group names.
Specify the Web project name as Loan_Web in the Web Project Name box.
Worklist Tutorial Conventions
  Back to Top       Previous  Next