Dynamic Parameter to be passed in SWFVISU

[former_member193724]

Hi Experts

Need help on passing dynamic parameter in SWFVISU to configure a standard task TS00500003 ( Review and Completion of Initial Record) related to EHSM Incident Mgmnt.

The work item is coming in SAP inbox in portal , on clicking the required WD application is opened without any data .

Reason is the value of KEY is not getting passed into WDA, maybe due to worng parameter set in DYNPARAM in SWFVISU.

Currently it is set to KEY=${INC_ROOT_KEY} , INC_ROOT_KEY has the value of Incident KEY as seen in WF task manager log.

Need help as what exact parameter needs to be passed to DYNPARAM so that data is displayed in the WDA screen.

Thanks

[former_member193724]

Hello All,

Issue solved by making few changes in the SystemId in the uwl.xml file.

Thanks

Lohit

[Jocelyn_Dart]

Hi Iohit,

Are you using the UWL then?  It's not enough to put in your Dynamic Parameter... you will need to use the UWL XML Configuration to explain to the UWL that it needs to read INC_ROOT_KEY from the webflow container, as it is possible to read the parameter from the container or a BOR object, for example.

If this is a standard task and a standard parameter then their should be a matching UWL XML Configuration file in the Portal Business Package for that task and it should be visible in the UWL Administration iview if it has been loaded up to your portal.

Rgds,

Jocelyn

[former_member193724]

hi Jocelyn

we are re registering the task evrytime we make change in SWFVISU , will that update the UWL xml file automatically or do we need to manually do it .

thanks

[Jocelyn_Dart]

Hi Iohit,

You couldn't find the business portal package????

If you are doing it by hand....

You'll need to adjust your SWFVISU entry a little.  More correctly the dynamic parameter value  in SWFVISU should be referenced as ${item.INC_ROOT_KEY}

Re-registering will bring what you have configured in SWFVISU into the UWL.XML file for that system alias.  But that still is not enough to achieve what you want.  However it will help you...

If you look for the relevant TS id in the generated uwl.xml file for that system alias, you can copy the whole <ItemType> tag into your own custom uwl xml file, and add the CustomAttributes and CustomAttributeSource tags that you need into the ItemType tag to complete the ItemType definition so that the UWL knows what your INC_ROOT_KEY means.  You then upload your custom uwl xml file as "medium" (or "high" but medium should be enough) priority so that it overrides the generated file for that task.

You want to add something like this into your ItemType tag. 

        <CustomAttributeSource id="WEBFLOW_CONTAINER" objectIdHolder="externalId" objectType="WebflowContainer" cacheValidity="final">

          <Attribute name="INC_ROOT_KEY" type="string" displayName="Incident Root Key"/>

        </CustomAttributeSource>

      </CustomAttributes>

Reference the DTD definition downloadable from the UWL Administration iview for the correct tag sequence. Don't forget to clear the UWL cache afterwards. And remember the settings will apply to any new work items that you send to the UWL - so generate some new work items to test it.

Good luck

Jocelyn

[former_member193724]

Thanks for your inputs Jocelyn.

After changing the dynamic parameter in SWFVISU to  ${item.INC_ROOT_KEY} , the value of KEY as checked in url generated is coming as "null" . But when checked in the workflow log container it has the value.

Also I wanted to know is there any other way other than editing the xml with CustomAttributes , as this approach is not accepted by the client.

Thanks

Lohit

[Jocelyn_Dart]

Hi Lohit,

If you want a custom attribute that uses your own key then you need to use the UWL XML to assign the appropriate value.  Naturally it will be null until the CustomAttributes etc. tags are used to tell the UWL where to read your INC_ROOT_KEY value. 

If you want to avoid changing the UWL XML you need to:

* Include the default parameter _WI_ID (yes you need to include the leading underscore) that passes the work item id to the UWL in the application that you call in your task

* Read the value of _WI_ID into your application and use it to read the workflow container e.g. using SAP_WAPI_READ_CONTAINER and retrieve your INC_ROOT_KEY value then assign it to wherever it needs to go in your application

OR... as suggested earlier if this is a standard Task that in standard is intended to be executed via the portal there should be a standard portal business package that includes a standard UWL XML file that should have been loaded to the portal business package.

Rgds,

Jocelyn

[former_member193724]

Hi Joyceln

As you suggested there is a standard xml file present for this task as attached below.

And also the config from SWFVISU was removed for this task, later checked by clicking the workitem in Portal inbox on which we got below error.

Since its a standard task and there is standard uwl.xml file present too , is there any more setting required to link the standard xml file.

On observation we also found the systemId="SAP_ECC_EnvironmentHealthSafety" is present in xml which is not there in our portal system. Our system id = SAP_ECC_Financials. Can this be one of the issue why the standard xml file is not reached on clicking the workitem and throwing the above error.

Waiting for your response.

Thanks

Lohit