UWL Connectors
Use
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 connector that is configured by default with UWL is the BPEMUWLConnector (in local case).
The connector is configured by default, so tasks from SAP 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:
BPMUWLConnector
The BPEMUWLConnector provides 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 .
ActionInboxConnector
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 the Knowledge Management documentation.
WsActionInboxConnector
The WsActionInboxConnector of the consumer system connects to the ActionInboxConnector of the provider system and provides KM Recent Notifications in the UWL Notification tab, checked-out documents under Tracking , and documents for approval under Tasks . The notifications, tracking and tasks are taken from the provider system.
The WsActionInboxConnector is not enabled by default and needs a specific configuration.
For the connector to function properly, you have to use the fully qualified domain name in the URL when logging on to the portal.
For more information, see the Knowledge Management documentation.
AlertConnector
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 .
WebFlowConnector
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
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.
For more information, see Configuring Guided Procedures with the Universal Worklist in the Guided Procedures documentation.
SomProviderConnector
With this connector, mails that are sent from Business Workplace are displayed in a separate tab in the UWL, the SAP Office Mail tab. The users can display, forward and delete these mails in the UWL and can display the mails' attachments.