Action Handlers  

Purpose

This section describes the different Action Handlers and Actions supported by UWL. To perform an action on an item, two things are necessary:

...

       1.      Action name and its properties

       2.      Action handlers

Following action handlers are provided by UWL:

●      IViewLauncher

●      SAPAppLauncher 

●      SAPMiniAppLauncher

●      SAPIACLauncher

●      SAPWebDynproLauncher

●      SAPWebDynproABAPLauncher

●      SAPTransactionLauncher

●      SAPBSPLauncher

●      ObjectLinkLauncher

●      ObjectNavigationLauncher

●      UrlLauncher

●      XhandlerLauncher

●      TerminatingEventHandler

●      FunctionModuleActionHandler

●      UpdatingContainerHandler

●      UserDecisionHandler

 

Static and Dynamic Parameters

All action handlers come with a set of standard properties. 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}

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, substitutedFor, systemId, userId

For more information about the attributes see Standard Item Attributes.

●      ${webflowuser}

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

...

 

By default the target applications do not launch a new window. To launch them in a new window and to control the window parameters the following should be added to the attributes of  <Action> node:

<Action … launchInNewWindow =”yes” launchNewWindowName=”sub” launchNewWindowFeatures =” resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no, location=no,directories=no“……>

 

Or they can be added to the <Properties> of <Action> node:

<Action …>   <Properties>    …..    <Property name="openInNewWindow" value="yes"/>    <Property name="newWindowName" value="sub" />    <Property name="newWindowFeatures" value="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no, location=no,directories=no“/> </Properties>

 

To launch an action in a new window with the portal frame use the attribute launchInNewWindow=”portal”.