Background documentation 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.

The connectors that are configured by default with UWL are:

  AdHocWorkflowConnector

  ActionInboxConnector

Both connectors are configured by default, so both Collaboration Tasks and KM Recent Notifications show up in the UWL by default. Removing the connectors will remove the corresponding items from the UWL.

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

AdHocWorkflowConnector

Note

This connector relates to Collaboration Task.

The AdHocWorkflowConnector connects Java Workflow and provides Collaboration Tasks into the UWL. Collaboration Tasks are created in the UWL using New Task, or within Collaboration in the My Tasks or Room Tasks lists.

By default the AdHocWorkflow connector is enabled. If it is not, then make sure that while linking connectors to the system names, the system alias AdHocSystem must map to AdHocWorkflowConnector.

Caution

You must enter the correct system alias to the corresponding connector. Errors occur if any other system (other than AdHocSystem) is mapped to this connector.

ActionInboxConnector

Note

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

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

By default the Action Inbox Connector for UWL is enabled.

For more information, see Action Inbox section in the KM Administration Guide.

AlertConnector

Note

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.

For more information, see Alert Management documentation .

GenericABAPConnector

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

The provider in ABAP should implement the interface IF_UWL_ITEM_PROVIDER.

Caution

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

Note

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

Note

This connector relates to Guided Procedures. 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.

Note

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

Was this page helpful to you?