Skip to Content
0

How to open UI5 screen from portal universal work list (UWL) ?

Jan 09 at 11:29 AM

181

avatar image
Former Member

Hi Experts,

Please help regarding below scenario :

I want to open the UI5 application from UWL and need to get the workitem id into the UI5.

What all XML configuration / back end i need to do to achieve this?

Any help would be greate.

Thank you.

Regards,

Ashutosh

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

avatar image
Former Member Jan 10 at 12:48 PM
0

This depends in concrete on what exactly you are working, XML UWL settings resp appropriate backend config are task specific. For my self, I never ran into corresponding SAP documentation, I would dare to say there is no. Buy and read this:

https://www.amazon.com/Universal-Worklist-SAP-NetWeaver-Portal-ebook/dp/B00K9UYBLK/ref=sr_1_1?ie=UTF8&qid=1515588438&sr=8-1&keywords=sap+portal+uwl

cheers

Share
10 |10000 characters needed characters left characters exceeded
Ivan Mirisola
Jan 10 at 04:27 PM
0

Hi Ashuntosh,

You should replace your UWL application with a modern inbox application called My Inbox. If you are already using Portal with Fiori applications deployed on it, why not use My Inbox (which has a nicer look and feel and will integrate other TS types as well).

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps('F0862')/W16

Back in the old days of UWL, you would need to register an application via WSVISU transaction, open the UWL XML configuration and adapt it to your needs. It was very hard indeed to find info on UWL configuration, but if you read the UWL XML you will understand how it does open determined tasks based on the task ID. Here are the docs to understand the task launching in UWL.

I have no idea how to configure WSVISU to open UI5 apps. Perhaps via Object Based Navigation. So you could assign an iView linked to your UI5 app and assign an action to an Object on the PCD (take a look at this blog I've done on OBN back in my Portal days). I believe this still would work. But I have never tested it.

Regards,
Ivan

Show 3 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Ivan,

You should replace your UWL application with a modern inbox application called My Inbox<br>

speaking in generally on this topic: to be able to do this, we need a proper migration strategy and tools. Currently it seems we are not aware of such: https://answers.sap.com/questions/375378/best-approach-for-lift-and-shift-of-sap-ep-uwl-to.html?childToView=394683#answer-394683

My own impression is: as long as this is the case we will furthermore protect the investions of our customers and go with UWL, even its dead. So suggesting to go with UI5 without offering a profound migration strategy is difficult imho

cheers

1

Hi Lawrence,

I agree with you. UWL is the option for customers that have implemented Enterprise Portal in the past and are still unable to use/integrate UI5 applications deployed on to their landscape.

However, this question is about integration of UI5 applications onto UWL. It is clear to me that deployment of My Inbox app is not a road-blocker in this case. Thus, it doesn't make much sense to continue using UWL if you are ready for Fiori Apps. That's the reason why I made that suggestion.

IMHO, as long as you have NW-GW on your landscape you could integrate any Workflow tasks on Fiori MyInbox while still protecting your current investment on EP.

Its all a matter of replacing a Portal feature with a Fiori application - so the only investment is in deployment of this particular app (which is way much faster then configuring UWL). You could even call it on a Portal Page so users aren't confused about how to perform their approvals. Let's face it: UWL is not as intuitive as My Inbox. Back in my days of EP I had loads of complaints about UWL (mainly about missing tasks, performance and connectivity issues) - so many even I started to dislike it. O the other hand I have implemented My Inbox app at customers in less than a week and users didn't even require training for it. I don't think it would be a disruptive approach that could mean a huge implementation investment. You could face approval situations where you would need to develop ABAP code that is specific to your needs (i.e.: changing document statuses directly on ERP instead of approving the WI and let WF deal with it). On such cases, you would need to consider additional investment. But even then the ABAP code could be simple and adapted from the WF you've implemented. I haven't seen such cases, but I know some bad WF implementations out there (specifically the ones that don't use BC-WF as engine). Other then that I think it is safe to consider it a change-management matter rather than any real investment protection issue. Nevertheless, if you are still up to an UWL challenge (good one), than the links I provided will give you hints on how to achieve what is needed. Configuring UWL has never been an easy task and surely isn't for operations to troubleshoot and fix issues related to it.

Anyway, it is up to you to decide which way to move forward - meaning the "migration strategy" it yours.

Regards,
Ivan

1
Former Member

Hi Ivan,

thank you for your support on this topic. Please dont get me wrong, Im absolutely not a fan of UWL, but

Its all a matter of replacing a Portal feature with a Fiori application - so the only investment is in deployment of this particular app 

I could miss something, but due my current knowledge stand this is wrong. Besides of the time amount you need for necessary configuration and paying attention to affected documents (https://wiki.scn.sap.com/wiki/display/Fiori/SAP+Fiori+-+My+Inbox), cause the https://launchpad.support.sap.com/#/notes/2538184 resp attached migration guide is far away from being an entire and real-world applicable document imho, I will still stick to it: there will be no advices to my customers or colleagues to go with My Inbox instead UWL. Thank you nevertheless for the promotion ;)

cheers

0
Antonette Venter Jan 15 at 12:14 PM
0

Hi Ashutosh

We achieved this by passing the GW app link as an attachment in the workflow item. The link is created dynamically in ECC with a bit of ABAP and added as an attachemnt. The id is made part of the url as a parameter in the gw app link. When you click on the inbox item attachement, the GW link opens <normal gw url to app>&workitem_id=1234. We then consume the paramater in the GW app by using: var parameter = jQuery.sap.getUriParameters().get("workitem_id");

Hope this is what you were refering to?

Regards

Antonette

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Antonette,

no idea where Ashutosh is exactly hanging on, but if you dont mind I would like to know for the (very theoretic and unlikely :)) case I would advise people to migrate to MyInbox:

I have currently a swiss customer, who has maintained a huge amount of undocumented customizing within UWL XML descriptors. He will switch to FLP, but due our advise stay with UWL within it. But just in case: what tools did you use to identify what exactly has been done and to transfer those changes (ideally) automatically to MyInbox?

thanks,

cheers

0