Using the Integrated Task List

This chapter provides overviews of the Integrated Task List configuration requirements and integration setup.

Understanding Integrated Task List Configuration Requirements

To enable your Integrated Task List feature to work as designed, ensure that your configuration meets the following requirements:

Ensure that the Tasks page uses the PAPP_NO_NAV_HTML template, or any Hypertext Markup Language (HTML) template, for registration so that the proxy is automatic.
Ensure that the Task Details page uses the PAPP_NO_NAV_FRAME, or any frame template, for registration. This enables the File Attachment feature.
Ensure that the Personalize Tasks page uses the PORTAL_HOMEPAGE_DESIGNER template, or any HTML template, to enable the Return to Home link.
Ensure that the WORKLIST and WORKLIST_DETAIL components are registered in an HTML template.
Ensure that you activated public or permission list security for all registered content references.

Understanding Integrated Task List Integration Setup

The Integrated Task List leverages PeopleSoft Integration Broker and XML technology to enable you to integrate tasks from any system in your implementation. This is also useful to aggregate worklists across PeopleSoft applications.

To use the Integrated Task List integration features, your must include the following set up in your configuration:

Schedule the Worklist Replicate process according to how frequently near-real-time updates are sent to and from the portal database.
Set PeopleSoft Integration Broker for standard operator and user security.
Specify a file storage location for file attachment functions using the URL Maintenance page in the portal database (select PeopleTools, Utilities, Administration, URLs). File attachments can be stored either on a File Transfer Protocol (FTP) server or in a database table. The URL identifier TASKS is reserved for the Integrated Task List feature. This identifier is used throughout the task PeopleCode.

The WORKLIST_MSG should be run using the PeopleTools Worklist Replicate Application Engine process (WL_REPLICATE ). To set up and run the Worklist Replicate process, you need to configure the message node locations, activate the worklist message, and test for cross-node publication and subscription.