Action Handlers

Use

Universal Worklist action handlers enable you to customize how a SAP Business Workflow work item is launched. They provide actions that can happen for a particular work item.

To perform an action on an item, two things are necessary:

  1. Action name and its properties

  2. Action handler implementation that takes care of the action

This section describes the different action handlers and actions supported by UWL. UWL ships with a bunch of predefined actions and action Handlers.

Following action handlers are shipped with UWL:

Static and Dynamic Parameters

Additional custom defined parameters are also supported. They can be static and dynamic, that is, substituted with an actual value during the run time.

Example of a static parameter:

               <Action …>
   <Properties>
      …
                        <Property name="fruit" value="apple"/>
   </Properties>
</Action>

This will append &fruit=apple to the constructed URL.

Dynamic property values should start with "${". These values could come from either the Item or some common values like user.

  • ${item.attributeName}

  • ${webflowUser}

    A back-end user ID corresponding to the logged in portal user if the provider system is an R3 system

AttributeName is case sensitive, and must be either a custom attribute for the item, or one of the following already defined attributes:

appContext , attachmentCount , completedDate , connectorId , createdDate , creatorId , description , dueDate , escalatedBy , executionUrl , expiryDate , externalId , externalObjectId , externalType , forwardedBy , forwardedDate , internalId , isEscalated , itemType , memoCount , parentItemId , priority , processDueDate , processor , status , subject , subprocessId , s ubstitutedFor , systemId , userId