The Worklist Web Services Facility

Using Worklist Web services, a customer can create their own custom client program to interface with CA Workflow. When you want to replace/complement human actors with software that shares work with them, the Worklist Web services can provide an alternative to using the Worklist Client UI.

For example, a fax actor could be an application most of the time but, when the fax server is not running, the workitems could be done by an individual.

The Worklist Web service operations are identical to the RPC calls used by the Worklist Client application.

This section contains the following topics:

Using the Worklist Web Services Facility

Worklist Web Services Operations

Complex Types - Worklist Web Services

Using the Worklist Web Services Facility

To use the Worklist Web services facility, use the WSDL located at http://<servername>:CA Portal/wl/services/wlService?wsdl with third-party tools to generate stub classes. These classes can then be interfaced with an application written in the appropriate language.

Worklist Web Services Operations

The server exposes its Worklist interface as a Web service for interaction with third-party components. The Web service exposes functions for detailed management of activities and workitems.

An important change from CA Workflow r1 is that logInToken(String token, String wlurl) and logIn(String username, String password, String wlurl) have been deprecated. The operations have been replaced with logInWL(String username, String password) and logInTokenWL(String token), which log the user into the local worklist. The old methods will not work correctly when passing in a remote worklist URL.

To log in to a remote worklist

Change the port address of your Web services client to that servers WLService address.

Summary of operations

A complete list of operations follows.