UWL Connectors 

Purpose

The UWL interacts with (task) item providers through specific connector. The connectors perform basic mapping of attribute values and determine the work item type and execution method. Connectors also help in connection to object and attachment repositories to retrieve additional custom attributes or attachments.

The UWL comes with standard provider connectors and it is possible to configure their detailed behavior based on work item types.

Connectors that are configured by default with UWL are:

●      ActionInboxConnector

●      BPEMUWLConnector (in local case)

Both connectors are configured by default, so both KM Recent Notifications and tasks from SAP NetWeaver Business Process Management (BPM) processes show up in the UWL by default. Removing the connector will remove the corresponding items from the UWL.

The following are the examples of UWL used (by default or configured) connectors:

ActionInboxConnector

This connector relates to the Notifications received by UWL from Knowledge Management (KM).

The ActionInboxConnector provides KM Recent Notifications into the UWL under Notifications, which include document feedback, subscription items, subscription administration, and document approval notifications; in addition documents for approval appear under Tasks.

By default the Action Inbox Connector for UWL is enabled.

BPEMUWLConnector

This connector relates to tasks received by UWL from BPM processes.

The BPEMUWLConnectorprovides the local case and the remote case. In the local case the consumer pulls tasks from the provider, which runs on the same engine. In this case the BPEMUWLConnector is automatically configured if a running process server (BPM runtime services) is detected during the deployment of UWLJWF.SCA.

In the remote case the consumer pulls tasks from a remote provider. You need to perform some configuration steps if you run the UWL in a federated portal.

For more information, see Configuring the UWL for BPM Tasks.

AlertConnector

This connector relates to Alerts.

For systems with this connector, you must define a new system. There is a centralized unique system in most SAP landscapes, which generates and provides Alerts. Register its item types with the UWL service through the Universal Worklist Administration  → Universal Worklist Systems.

GenericABAPConnector

UWL implements a connector GenericAbapConnector that connects to the SAP system and invokes a preconfigured ABAP class.

The provider in ABAP should implement the interface IF_UWL_ITEM_PROVIDER.

Bypassing a workflow engine and directly creating tasks for the users is not ideally suited for items that need to be tracked, or which need workflow services like forward, substitution, and attachments. It is strongly recommended to use either Business Workflow or Collaboration Task for dealing with workflow process. Usage of GenericAbapConnector should be the last option for the application under exceptional circumstances.

WebFlowConnector

This connector relates to SAP Business Workflow.

For systems with this connector, you must define a new system and register its item types with the UWL service through the Universal Worklist Administration  →Universal Worklist Systems.

GuidedProceduresConnector

This connector relates to Guided Procedures (GP). Select this connector type if you use the built-in GP processing engine.

For systems with this connector, you must define a new system and register its item types with the UWL service through the Universal Worklist Administration  →Universal Worklist Systems.

If you use the Business Process Management (BPM) runtime as the processing engine for Guided Procedures, select the WebFlowConnector type.

More information: Configuring Guided Procedures with the Universal Worklist