difference between url iveiw and BSP iveiw

[Former Member]

hi,

What are the parameters we need for BSP iveiw and URL iveiw. What is the difference between these.

[Former Member · Accepted solution]

hi,

IViewLauncher

IViewLaucher can be used to launch any IView or Portal Component or a Page in the portal. Portal Component launching is supported only in NW04.

Provider specific Information

IViewLauncher is Provider agnostic. Items may belong to any connector.

Supported Actions

Action name can be anything.

Properties

IViewLauncher expects one of the following two mandatory properties:

iview - iView id or Portal Component name to be launched

page - page id of the page to be launched

All other properties will be passed as name=URL encoded value to the target iView. The dynamic properties can also be passed to an iView via the following property (since NW04 SPS18, NW04s SPS09, NY AP7):

iviewDynamicParameter - optional; name/value pairs of dynamic parameters to be passed to the iView/page. The expected format is name1=value1&name2=value2 etc.

Example

Following is the definition of an action that launches an IView with id ROLES://portal_content/com.sap.pct/every_user/general/iViews/myDemoIView.

<Action name="launchIView" handler="IViewLauncher">

<Properties>

<Property name="iview" value="ROLES://portal_content/com.sap.pct/every_user/general/iViews/myDemoIView"/>

</Properties>

</Action>

Example on how to configure an action to launch a Portal Component com.sap.netweaver.bc.uwl.ui.DemoIView:

<Action name="launchIView" handler="IViewLauncher">

<Properties>

<Property name="iview" value="com.sap.netweaver.bc.uwl.ui.DemoIView"/>

</Properties>

</Action>

Example on how to configure an action to launch a Portal Page with id ROLES://portal_content/com.sap.pct/every_user/general/Pages/com.sap.km.MyInfoDiscussions:

<Action name="launchIView" handler="IViewLauncher">

<Properties>

<Property name="page" value="ROLES://portal_content/com.sap.pct/every_user/general/Pages/com.sap.km.MyInfoDiscussions"/>

</Properties>

</Action>

Description

The following parameters are optionally passed on to the iView, WHEN no parameters are explicitly defined.

wi_id - work item id in the provider system

destination - system alias in the Portal system landscape of the provider system

item_id - internal UWL item id

task - provider task item type

uname - backend user id for webflow connector, alert connector and generic ABAP connector, otherwise Portal user id

langu - user language in upper case ISO language code

Additional custom defined parameters are also supported. They can be static and dynamic, i.e., 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}

$ - a backend 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 substitutedFor systemId userId (see description).

An example of using dynamic properies:

<Action ...>

<Properties>

...

<Property name="workitemId" value="${item.externalId}"/>

<Property name="system" value="${item.systemId}"/>

</Properties>

</Action>

This will result in passing workitemId and system parameters to the target page/iView. This is the same as specifying iviewDynamicParameter property:

<Action ...>

<Properties>

...

<Property name="iviewDynamicParameter" value="workitemId=${item.externalId}&amp;system=${item.systemId}"/>

</Properties>

</Action>

Note. For webflow connector iViewLauncher can be configured on the backend using SWFVISU transaction. The table below summarizes the mapping between the launcher parameters and the visualization parameters.

Launcher parameter Visualization Type Visualization Parameter

page Portal Page ID

iview iView ID

iviewDynamicParameter iView/Portal Page DYNPARAM

UrlLauncher

UrlLauncher can be used to launch any url.

Provider specific Information

UrlLauncher is Provider agnostic. Items may belong to any connector.

Supported Actions

Action name can be anything.

Properties

UrlLauncher expects the following property:

url mandatory; url to be launched.

All other properties will be passed as name=URL encoded value to the target url.

Example

Following is the definition of an action that launches a url my.web.com and passes to it the parameter workitem_id, which is filled with the work item id during run time:

<Action name="launchUrl" handler="UrlLauncher">

<Properties>

<Property name="url" value="http://my.web.com"/>

<Property name="workitem_id" value="${item.externalId}"/>

</Properties>

</Action>

[Former Member]

hi

good

go through this link

http://www.sappro.com/downloads/SPJ_Dixon_MarApr05.pdf

reward point if helpful.

thanks

mrutyun^