Show TOC

ObjectLinkLauncherLocate this document in the navigation structure

Use

You can use ObjectLinkLauncher to evaluate and navigate to the BSP blueprint display of the underlying object of the item.

Provider specific Information

Current scope is supported by the CRM context service which mainly covers the CRM object type.

Items can be from any connector as long as it can provide the required parameters.

Supported Actions

Action name can be anything.

Properties

ObjectLinkLauncher expects the following properties:

  • ObjectType (mandatory)

    UWL exception is thrown if empty. CRM object type is expected. Provider should provide mapping (for example, for business workflow item, BOR object type is mapped to the corresponding CRM object type).

  • ObjectMethod (optional)

    Default method of the CRM object type is called for business workflow item.

  • ObjectKey (optional)

    Can use dynamic property values starting with ${item.externalObjectId} . If not provided, the launcher will do a lookup for the object id (if any), otherwise, call the CRM context service to generate the link with an empty key.

  • TargetSystem (optional)

    System that generates the object link. Default is the system where the item is generated (system alias defined in the portal system landscape).

  • FallbackAction (optional, but highly recommended in case an alternative should be provided when the object link generation fails, or an exception will be thrown)

    The value is the action name of another configured action tag.

  • SpecialConfirm (optional)

    This is only for business workflow item and for the (old) launched applications that do not support callback to the provider to complete the item. Flagging the parameter allows the launcher to complete the item for the launched applications, for example,

    <Property name="SpecialConfirm" value="X"/>. Default is no confirmation.

Other additional parameters can be defined as well and will be appended included in the generated link.

Example

Item type for such item can be configured through a XML configuration file.

Example of configuring webflow task TS00000001 in XML configuration, associated with the object type PRODUCT and method DEFAULT :

ItemType name="uwl.task.webflow.TS00000001" connector="WebFlowConnector" ..........>
 <Actions>
  <Action name="launchObjectLink" handler="ObjectLinkLauncher">
   <Properties>
    <Property name="ObjectType" value="PRODUCT"/>
    <Property name="ObjectMethod" value="DEFAULT"/>
    <Property name="ObjectKey" value="${item.externalObjectId}"/>
    <Property name="FallbackAction" value="launchSAPAction"/>
    <Property name="_sapwiid" value="${item.externalId}"/>
    <Property name="anotherParam" value="anotherValue"/>
   </Properties>
  </Action>
 </Actions>
</ItemType>

For business workflow item, configuration can also be done via back-end visualization transaction SWFVISU for visualization type BSP BluePrint. The table below summarizes the mapping between the launcher parameters and the visualization parameters.

Launcher Parameter

Visualization Parameter

ObjectType

CRM_OTYPE

ObjectMethod

CRM_METHOD

SpecialConfirm

CONFIRM