Universal Worklist : launch workitems ?

Hi Gurus,
First of all, Im new in UWL and I have a question about it.
I have an existing Workflow in SAP Business Workplace which contains tasks which are calling ABAP programs with Screen Painter through BDC :
Workflows -> Tasks -> ABAP Programs
My customer use now the UWL and wants to know if its possible to launch the entire Workflow which was in SAP Business Workplace directly in the portal.
I heard about SAP GUI for HTML but he wants to execute each screen of the Workflow (in Screen Painter, Select option ) in the SAP EP like a BSP or WebDynpro iview without coding (maybe a way to convert ABAP screens in iview ??).
I mean lauching ABAP Workitem in Portal.
Today, the UWL is configured to see workitems in it but I cant execute the workitems.
Thanks

Thanks for your fast answer Karri.
So, as you said, I can lauch in UWL a SAP transaction (eg ME23N or something else) ?
Because I read in the following document :
http://help.sap.com/bp_epv260/EP_JA/documentation/How-to_Guides/KM/UWL.pdf
"Item Launch Configuration
For specific task types, the default task launch as defined in the backend is overridden by iViews,
WebDynpro applications or any URL, which represent the task completion transaction."
To summary, I want to do the same thing in page 3 (or page 9/65) of the above pdf document.
Thanks

Similar Messages

Customizing of Universal Worklist (UWL) Preview

Hello,
i have to customize the UWL preview, that is shown in the portal for every work item below the list view.
The customization shall be done only for the current project, so there are only a few worksteps involved that should use the customized preview.
I already read the UWV configuration documentation, but i hav absolutely no clue how i can do the customization if it is possible at all.
What i have to achieve:
- remove Buttons from the workitem preview (e.g. forward)
- remove attributes from the workitem preview (e.g. priority)
- the configuration shall only be done for specific work items because other projects want to see the preview.
Can you please help or point me to some documentation/ guide?

have a look at these weblogs
Customizing Default actions of items in UWL
Customizing Default actions of items in UWL
Launching WebDynpro from Universal Worklist
Launching WebDynpro from Universal Worklist
ALERTS
Integrating Alerts into UWL - it's no problem!
Integrating Alerts into UWL - it's no problem!
Support for secondary methods in UWL!
Support for secondary methods in UWL!
Innovative ways to use alerts
Innovative ways to use alerts
Universal Worklist - when you only need a single tab
Universal Worklist - when you only need a single tab
Swathi
Do offer points:-)

Launch URL/BSP from attachments link in workitem in Universal Worklist

Background info:
We have a custom business object. Default method on object in SWO1 is a custom display method. This display method returns a URL to a BSP.
When I open my workitem in SBWP and click the attachments link, it properly launches the URL which opens the BSP.
However, when I open same workitem in Universal worklist and click the attachments link, it does not properly open the BSP. It looks like it's trying to open a SAP GUI version of the object but nothing is displayed. When our developer puts a breakpoint in the ABAP code and we click the workitem link in UWL, the URL/BSP opens fine. So, UWL config must be doing something extra (added code? redirect?) that clobbers the URL/BSP launch. Anyone have any ideas/suggestions?
Thanks,
Matt
*Reminder, We are not trying to launch the BSP when you click the workitem link in the UWL list. This is the attachments link inside the workitem itself.

G'Day Matthew,
The reason this works from SBWP and not from UWL is because you have an ABAP session in between. You don't mention the type of attachment, but usually what gets executed is the default method of the object. Thus the UWL has to initiate an ITS/WebGUI session to execute the default object method - this method may contain code to launch a BSP but it still needs to get to the code to start with.
You need to find alternatives, see if Karri's suggestion does what you're after.
Cheers,
Mike

PO Approval Items Workitems are not removed from the Universal Worklist UWL

Hi,
Certain of our purchase orders require approval, they are sent to the relevant approver via workflow to their SAP inbox (SBWP) and universal worklist.
When the user executes the workitem (Approve or Reject) The workitem should be removed from the universal worklist and SBWP when refreshed.
The problem we experiencing is that the Workitems are not removed from the UWL after they have been executed. The SBWP is behaving correctly and the items are removed.
It is not all the workitems that have this problem, only certain ones - but there is no pattern.
Thanks for the help.

Hi,
The user B approved the PR accessing the transaction SBWP or via PR transaction directly?
If via PR transaction directly, then your workflow needs a Wait Event step.
Regards,
Kleber

Workitem in universal worklist not refreshed after processing the workitem

Hi,
We are using EP 7.0, we are having a problem in refreshing workitem in universal worklist. When a workitem in universal worklist is clicked a ABAP webdynpro application is opened in new window, this window has approve and reject button. Clicking on the approve or reject button completes the business process and workitem should be removed from the UWL. But in our case the workitem is still shown in the UWL and the user can again click on the same workitem and open.
Has anyone has encountered this problem? Could someone let me know how to resolve this issue.
Thanks & Regards,
H.K.Hayath Basha.

Hi,
Just check the status of the workitem whether its approved or rejected before opening the application. If its already approved
or rejected dont open the application.We also faced the similar problem and avoid opening the work item instead of refreshing
uwl.
Because by configuration it is possible to reduce till one minute and frequent refresh of uwl will result in poor performance.
You can give a try with writing code to refresh uwl once the workitem got approved or rejected.
http://help.sap.com/javadocs/NW04S/current/uw/com/sap/netweaver/bc/uwl/admin/IUWLAdmin.html
Try using clear cache.
Best Wishes
Idhaya R

Workitem not getting accessed in universal worklist

Hi all
i have configured a customized workflow and its working nice in GUI,now the problem is that when a workitem is send to the person ,it is getting displayed in the person's universal worklist but it can not be accessed
like in SWEFVISU i have maintained both the task and object' visual parameters settings
like
task ---the task id used in workflow
visualization parameter for task--
object
object's visualisation parameters
i mean these 4 settings are there
from my understanding i have set every entry but its not working
can any one please advise what settings i have to maintain pertaining to SWEFVISU
so that i can access my workitem in the persons universal worklist
any help will be highly appreciated
best regards
ashish

done

Launching WebDynpro from Universal Worklist

Hello All,
am trying to launch a Web Dynpro Application from the UWL but was not able to open the application.
We are following the Launching WebDynpro from Universal Worklist blog. But we are not able to open. Can any one help on this?
Thanks
Gopal

Hi ,
check the defaultAction assigned to launchWebdynpro or not?
<ItemType name="uwl.task.webflow.TS91000129.UWL" connector="WebFlowConnector"
defaultView="Test" executionMode="default" defaultAction="launchWebdynpro">
after modifying did you upload with previous name of xml file? If you give different name to xml file , set highest priority such that uwl will consider this xml file
Koti Reddy

Link to Object (Lead) from workitem in Universal worklist

Hello. We have a workflow that sends workitems (dialog tasks) to a users inbox in SAP portal. If I open the workitem from Universal worklist and then click the link inside the workitem to take me to the object (CRM Lead or Business Activity), I get "page not found". However, if I click this same link after opening the workitem in business workplace (SBWP), I'm taken to the object fine as I expect. Anyone know why the object link from UWL does not work? Or where it's configured?
Note, if I click an object link in UWL for an item that was generated from ECC (say for Document, Material Master, etc), I'm taken to the object just fine. Our issue seems narrowed to the combination of CRM and Universal worklist.
Thanks.

Hi,
Did u check under
Content Admin -> Webdynpro , the component ess~lea and the application LeaveRequestApprover are in status green.
Also check the correspinding JCO connections tab.
I presume that you have installed the ESS, MSS and PCUI GP patches.
Regards
Jayesh
Edited by: Jayesh Ghodge on Dec 21, 2007 4:28 PM

Context menu in the Universal Worklist

Hello all,
I'm migrating from Portal 7.0 to 7.3, and right now, I'm trying to migrate the UWL configuration.
I created the Universal Worklist Systems, I uploaded all the .xml configurations, I re-registered the system, I configurated the UWL iView... everything was done like in the Portal 7.0... BUT it doesn't works like before. I'm having problems with the "context menu" of each workitem.
In Portal 7.0, when all the "List of UWL Actions to exclude" are typed, the context menu of each workitem dissapears, and I can do a "click" over the workitem and a webdynpro app. is launched.
In Portal 7.3, when all the "List of UWL Actions to exclude" are typed, the context menu of the selected row dissapears, but still remains in the other unselected lines; and the most important thing, when a workitem row is selected, I can't do a "click" over it, it doesn't do anything... If I leave "launchWenDynPro" value into "List of UWL Actions to exclude", I can do a "click" over the workitems, and the webdynpro app. is launched, but the context menu appears...
How can I do to make dissapear the context menu?
I read the following link, but my Portal 7.3 doesn't works like this...
http://wiki.sdn.sap.com/wiki/display/BPX/ContextMenuBehaviourhaschangedinrelease7.10andhigheroftheUniversal+Worklist
Thanks!
Miguel.

Hi Miguel,
Thanks for your post. It would be great if you can let me know the complete version of the UWLJWF component from NWA. To get this please do the following:
To get this, please do the following:
Open NWA -> Configuration management -> System info ->
press Components info tab, and for software components
Search for UWLJWF and you will find the component information. Could you please post it here? Is it possible that you can provide a link to some screenshots of what you are seeing as well?
Along with this, have you checked the standard iview from the PCD - if so is this giving the same result?
Regards,
Beth
EP - Senior Support Consultant II
SAP Active Global Support
Global Support Centre Ireland
**SDN Forum Moderator:
http://forums.sdn.sap.com/forum.jspa?forumID=495&start=0
**SDN Universal Worklist Wiki:
http://wiki.sdn.sap.com/wiki/x/ehU

Universal Worklist items open in new window instead of existing frame

After our recent upgrade we noticed that workitems in Universal Worklist open in new window instead of existing frame. Do you know if there is a system or universal setting to make all the workitems open in existing frame? I know we can change the settings for parameters launchInNewWindow and openInNewWindow to "no" in XML files to fix this.   However, my concern is that I would need to do this for each and every task we use. (still doable but wondering if there is simpler solution)
Example:
    <ItemType name="uwl.task.webflow.TS12300097.SAP_R3_CUSTOM_DEV" connector="WebFlowConnector" defaultView="DefaultView" defaultAction="launchWebDynPro" executionMode="default">
      <ItemTypeCriteria systemId="SAP_R3_CUSTOM_DEV" externalType="TS12300097" connector="WebFlowConnector"/>
      <Actions>
        <Action name="launchWebDynPro" groupAction="" handler="SAPWebDynproLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
          <Properties>
            <Property name="WebDynproApplication" value="LeaveRequestApprover"/>
            <Property name="WebDynproDeployableObject" value="sap.com/ess~lea"/>
            <Property name="newWindowFeatures" value="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no"/>
            <Property name="openInNewWindow" value="yes"/>
            <Property name="display_order_priority" value="5"/>
          </Properties>
          <Descriptions default=""/>
        </Action>
      </Actions>
    </ItemType>

We downloaded uwl.standard.xml from UWL admin. Made a copy and renamed file. Changed all "launchInNewWindow" from "yes" to "no". Uploaded new file in UWL admin. Re-registered systems, cleared cache. Not sure what exact line changed the behavior but the workitems no longer open in new window.
We are still experimenting with file in our sandbox environment.

SRM Integration in Universal Worklist (UWL)

Hi SRM freaks,
I've one question concerning SRM integration in Universal Worklist (UWL). Currently we have integrated our SAP SRM4.0(SRM_SERVER 500) solution in the SAP Enterprise Portal6.0, and after installation from an additional Business Package the system is working perfectly.
But we have one concern about UWL integration, the workitems which are send over eMail to the endusers are still containing ITS_DEST link which is defined in PPOMA. The following web link is pointing directly to SRM-EBP ITS link and not to the portal. Our idea would be to include a web link which is pointing to portal in order to access SRM-EBP content from there.
Can somebody help us on that topic !?
Thanks for your support.
Rafi

Rafi,
Hi. We are using SRM 5.5 and are intending on changing the ITS_DEST to run SRM through the portal.
That way any email links sent to the users always contain a link back to the Portal (which has our UWL configured).
I'm not too sure of the consequences of changing this attribute on release 500. Our system has an internal ITS - does yours?
Cheers
Rob

SAP Press book on Universal Worklist

Hi all,
I have just started writing a book for SAP Press on the Universal Worklist, to pass along some of what I have learned when working with the portal these past 5 years or so (anyone else remember EP 4.5?)
I've put up a blog entry at
<a href="http://www.fortybeans.com/">http://www.fortybeans.com/</a> and if you click the <a href="http://fortybeans.wishconsultants.co.uk/item/2007/2/6/universal-worklist-book-for-sap-press">Read more</a> link you can see the proposed chapters and sections I will be writing.
I'd really appreciate any feedback any of you can give me - I want to make this the best possible book of its kind, and the only way to do that is to find out what people want from the book and then to give it to them. Maybe this could be the first book from SAP Press with "Powered by SDN" on the cover?
Let me know what you think,
Darren

First off....EP4.5?....yep...when it was a Top Tier product. I was working on Workplace 3.0 (bootcamp) at the time....one week later, SAP and Top Tier announce the joint formation of the company "SAP Enterprise Portals" with their flagship product EP 5.0. Ahhh those were the days. I really want to meet the person who came up with calling it "portal-S" because I spent countless time explaining why the product was "Enterprise Portal" and not "Enterprise Portals". That was only compounded once SAP bought Top Tier outright, brought EP5.0 back into SAP proper and folded the "SAP Enterprise Portals" company. Ugg....anyways...
The book sounds great. I too have fought in the trenches and wrestled with the UWL. It is great when it is used strictly as intended and with the limitations it might have. Past that....let the fun begin!
I read your rough outline. Some chapters/content I would really like to see....
- some basic coverage on Workflow (what it is, how it works, etc).
- some explaination of "webflow", how it got started and where it is today
- how workflow correlates to what the user sees in the UWL
- limitations of the UWL based on support package level ( this is a big one!!! trying to use attachments now...nope...can't until the next SP level unless we backport our own custom webdynpro...that's not fun to find out 2 months in! haha)
- really good examples of customizing items to launch one way in the portal versus another way within the backend inbox (ie. uwl xml config vs. config in the backend) and show ways to launch various SAP apps (dialog in SAP GUI, ITS service, webdynpro, etc). from UWL items.
- same as above but show how to launch NON-SAP apps (we have a situation now where we have a UWL item that launches a Flex application and passes an order number to it)
- similar to the above two, what's possible to pass across from the UWL to whatever through the portal (like UWL to an iView and on to the underlying application)...figuring out how "DynamicParameters" works is new to lots of people who might not have web dev background and/or understand the construction/structure of a URL query string
- some information along the lines of "UWL launched an item/action out to some app, but how does the workflow status get updated to that fact?" ie. what makes the round trip complete?
- a really good BIG, real world example showing multi-system (CRM-to-ECC-to-APO-to-SRM-to- etc) workflow and how the UWL makes it all much easier and fluid (in theory...haha)
That's just a few off the top of my head that seem to always be sooo much fun with the UWL.
Good luck on the book! Looking forward to it already!

Calling a BSP application from universal worklist

Hi All,
I want to call a BSP application, when a workitem is clicked in Universal Worklist(Enterprise Portal)
I have configured the Task Type in SWFVISU transaction, with Visualization type BSP standard & in visualization parameter i entered,
APPLICATION = zgelrbsp0001
PAGE_ID = leso.htm
When I click on the workitem my test BSP application is called. Buy my requirement is not call a static dynamic application, when the workflow is called the workflow container has a URL
http://dev01.abc.gov.sg:8000/sap/bc/bsp/sap/hap_document/document_port_wf.htm/
this URL will change. But I don't know how to configure to call the URL in container. Please let me know how to achieve this.
Regards,
H.K.Hayath Basha.

Hi Raja,
Thanks for the reply.
I said wrongly in my earlier mai, my URL is static, but the parameter appl_id will have different value.
http://dev01.abc.gov.sg:8000/sap/bc/bsp/sap/hap_document/document_port_wf.htm/?appl_id=1234
What I have done is similar to the one which you have said, copied the standard BSP and modified, I pass WORKITEM ID to the BSP application, BSP application reads the workflow container for appl_id and sets that value to the BSP application attribute.
There should be a better way to do this.
Regards,
H.K.Hayath Basha.

Universal Worklist Configuration

Hey guys
Please can someone tell me where I can find a universal wordlist config guide for EP7.0?
Many thanks in advance
Jo-lize

Hi
This are the steps need to be followed.please do give full points
The Universal Worklist (UWL) gives users unified and centralized way to access their work and the relevant information in the Enterprise Portal. It collects tasks and notifications from multiple provider systems SAP Business Workflow, Collaboration Task, Alert Framework and Knowledge Management Recent Notifications - in one list for one-stop access.
Administration and configuration for the Universal Worklist (UWL) is described.
General Prerequisites
1.     As an administrator, you have full administration rights for the Portal and the required business workflow rights in back end system (reference roles such as SAP_BC_BMT_WFM_UWL_ADMIN and SAP_BC_UWL_ADMIN_USER). Refer to SAP note 941589.
Summary
Symptom
UWL administrative and/or end users are not allowed to perform or look up business workflow functions or data in the backend system.
Reason and Prerequisites
Corresponding adminsitrative and end users in the backend systems are created from scratch and have zero initial authorization.
These roles are provided as an option to enable UWL administrative and end user authorization to readily utitlize the APIs of the SAP Business Workflow and relevant basis components remotely.
(Note: Usually these roles are not needed as backend user is already assigned with roles that have sufficient authorization.)
Also refer to BWF note 938717 for the corresponding roles required by business workflow.
SAP_BC_UWL_ADMIN_USER
For UWL administrative user who mainly deals with business workflow system registration.
SAP_BC_UWL_END_USER
For UWL end user to carry out all business workflow actions currently supported in UWL.
Solution
The roles can only be imported with a support package
Header Data
Release Status:     Released for Customer
Released on:     25.04.2006 04:57:52
Priority:     Recommendations/additional info
Category:     Advance development
Primary Component:     EP-BC-UWL Universal Worklist
Releases
SoftwareComponent     Release     FromRelease     ToRelease     AndsubsequentSAP_BASIS     60     640     640      SAP_BASIS     70     700     700
Highest Implemented Support Package
SupportPackages     Release     PackageNameSAP_BASIS     640     SAPKB64017SAP_BASIS     640     SAPKB64019SAP_BASIS     700     SAPKB70008SAP_BASIS
Summary
Symptom
This note delivers two roles (PFCG) with the authorizations required to display and edit Business Workflow work items in the universal worklist.
SAP_BC_BMT_WFM_UWL_ADMIN
This role has the workflow authorizations required to perform the configuration for the Business Workflow connection in the universal worklist. These are authorizations for Business Workflow interfaces on the back-end system. The role does not have any authorizations for the portal or other interfaces used by the universal worklist.
SAP_BC_BMT_WFM_UWL_END_USER
This role has all workflow authorizations required by end users to be able to edit Business Workflow work items with the universal worklist. The role does not have any authorizations for the portal or other interfaces used by the universal worklist.
You can either use the two roles directly or as templates for your own roles.
Note 941589 contains more information about roles with authorizations for the universal worklist.
Other terms
Universal worklist
Solution
The roles can only be imported with the relevant Support Package.
Header Data
Release Status:     Released for Customer
Released on:     20.04.2006 07:43:26
Priority:     Recommendations/additional info
Category:     Advance development
Primary Component:     BC-BMT-WFM Business Workflow
Secondary Components:     EP-BC-UWL Universal Worklist
Releases
SoftwareComponent     Release     FromRelease     ToRelease     AndsubsequentSAP_BASIS     60     640     640      SAP_BASIS     70     700     700
Highest Implemented Support Package
SupportPackages     Release     PackageNameSAP_BASIS     640     SAPKB64017SAP_BASIS     700     SAPKB70008
Related Notes
941589 - UWL: administrative and end user roles
Attributes
1.     Make sure that each user is known to all connected SAP systems as per role requirement (make sure that there is one-to-one mapping between the portal user and the backend user)
If an iView is based on a system object defined in your system landscape, you must assign user permission for the relevant user, group, or role to the system object, as well. User permissions assigned to a system permits the iView to retrieve data from the respective back end application through the system object at runtime.
2.      Each connected SAP system for back end system (below release 7.0, WP-PI plug-in 6.0) has the connection to its respective SAP Internet Transaction Server (ITS)
Authorizations needed for working with Business Workflow
Normally, when the corresponding back end system user already has the correct authorization to work on the Business Workflow directly, no additional setup is required when working in UWL. However, manual configuration to assign RFC access authorization to the following function groups may be needed (Note: this is not common):
1.     ●      Function group and transaction SWK1 (for back end systems using WP-PI plug-in)
2.     ●      Function group SWN_UWL_WL (for back end system on release 6.40 and above, without the need of WP-PI plug-in)
3.     ●      Function group SWRC, SSCV (for all cases)
4.     ●      Authorization rights for SDTX
User Mapping:
1.      Navigate to User Administration ®identity Managementà User Mapping.
       2.      There are three scenarios:
○     Portal user ID is different than the back end SAP user ID and back end SAP user IDs are different in all back end SAP systems connected to the portal (UIDPW)
1.      Maintain the user mapping for each portal user corresponding to all the respective back end systems
2.      Portal user ID is different than the back end SAP user ID and backend SAP user ids are the same in all back end SAP systems connected to the portal (logon ticket)
Maintain the user mapping for each portal user to the reference system
3.     Portal user ID is the same as the back end SAP user and back end SAP user IDs are the same in all back end SAP systems connected to the portal (logon ticket)
1.       No user mapping is necessary
User Permissions
According to the prerequisites, if an iView is based on a system object defined in your system landscape, you must assign user permission for the relevant user, group, or role to the system object, as well.
User permissions assigned to a system permits the iView to retrieve data from the respective back end application through the system object at runtime.
     Procedure
       1.      Navigate to System Administration ® System Configuration ® Portal Content. Open the folder where the existing systems were created.
       2.      From the available system list, click with the secondary mouse button on the system name and choose Open ® Permissions.
       3.      Assign permissions. Make sure that under the Administrator column you assign Read permissions for the assigned role (for example for role eu_role). Also mark the check box End User.
       4.      Choose Save.
     Registering the Provider Systems
Each UWL iView can retrieve work items from multiple Business Workflow back end systems. Register each back-end connection to be used with the following procedure:
On the port...
       1.      On the portal, choose System Administration ® System Configuration ® Universal Worklist and Workflow ® Universal Worklist Administration.
The Universal Worklist Systems list appears. Here you can define connectors and systems as item providers for the Universal Worklist.
       2.      To add a new entry, choose New. To edit existing information, select (highlight) the row and choose Edit.
       3.      To save the current system registration, choose Ok.
       4.      Multiple system connections are defined by repeating the above steps 1 to 3.
Table describing the parameters
Parameter     Description and Use
Connector     This is the identifier with which the connector is registered. It indicates the type of items retrieved through the connection. For example: WebFlowConnector.For connector types WebFlowConnector or Alert Connector item types have to be registered with the UWL service after defining a new system connection.
Configuration Groups     Leave this blank, when working with the default UWL iView. You can add a number of configuration groups separated by commas but only one configuration group per iView. first installed, one UWL iView is defined. The System Configuration Group property for that iView is empty (blank). This means that no System Configuration Group is named, but in effect there is only a single group. The default behavior for the blank setting is this: when any user logs onto the UWL iView, UWL tries to log that user onto all registered back end systems. There is a limitation with the blank setting. When a large number of systems are accessed during log on, the overall portal load is increased. Also, the user receives error messages from those back end systems that have no user account for the particular UWL user. For large system landscapes do the following:...       1.      Partition back end systems into groups. This is accomplished by creating additional UWL iView instances, each of which refers to a specific group of backend systems. The group is defined, using the System Configuration Group iView property.       2.      Then use the value of the System Configuration Group property when registering back end systems by placing it in parameter Configuration Group, when you register the SAP system.
System alias     The name of the alias for the back end system, as defined in the system landscape. The length cannot exceed 25 characters.If Web Dynpro applications are configured on a SAP NetWeaver Application Server which is different from the SAP NetWeaver Application Server of the system alias, then specify that system alias as a Web Dynpro system
Web Dynpro Launch System     Enter the Web Dynpro system name if the SAP NetWeaver Application Server for the system is not the same as that running the Web Dynpro.Leave empty otherwise
User Roles     Restricts who can get work items via the user role. For example, you can assign a portal role here, such as buyer. Only users with the role buyer will see items from the provider system in UWL.You can have multiple user roles separated by semi-colon. By specifying user roles for the portal users, it can be restricted as to who gets the work items in UWL. For example, you can assign a portal role to a user, such as buyer. Only users with the role buyer will see items from a system, for example, B7QCLNT000 in UWL.
Pull Channel Delta Refresh Period (in Seconds)     Delta Pull mechanism of UWL enables new items to be fetched from the back end SAP systems every minute by default every 60 seconds, and every 30 seconds for alerts. However, this can be configured. The user does not need to use the refresh function to update the inbox. Once items are retrieved, timestamps are updated for the users whose items are successfully retrieved. These retrieved items are updated in the UWL cache. Setup necessary from Business Workflow to enable Delta Pull MechanismSome configuration settings are required if you use the UWL and the Extended Notifications for SAP Business Workflow. Define the following two batch jobs:...●      Background job (for example UWL_DELTA_PULL_1), consisting of a single step of ABAP report RSWNUWLSEL in FULL mode, using a report variant.Run the job once a day.1.     ●      A background job (for example UWL_DELTA_PULL_2), consisting of a single step of ABAP report RSWNUWLSEL in DELTA mode (default mode is delta, so report variant is optional).Run the job every one to three minutes (depending on the performance of the back end SAP system).Setup necessary from UWL to enable Delta Pull Mechanism The UWL service user in portal, with user id uwl_service, has to be granted access to the corresponding back end systems. This is a predefined service user provided by UWL. When the back end system is configured in the UWL administration page, an automated process is triggered to create a corresponding UWL service user in the back end system.Check role assignments and profiles status of this automated generated UWL service user and perform user comparison if necessary.●      If SAPLogon ticket is used (without using user mapping), you first create the system entry. A message about uwl_service user appears. Then in the back-end system give the uwl_service user an initial password. Now edit the system entry.●      If user mapping is used, you can first configure the back end system in the UWL administration page. Then access the respective back end system to initialize the password for the user uwl_service. Then, do user mapping in the portal as usual for service user uwl_service.In case uwl_service fails to be created in the back end and does not exist, you can manually create a back end user with the id uwl_service and assign the role SAP_BC_UWL_SERVICE and the rights as other end users.ORMap uwl_service to an existing back end user. Make sure that there is no multiple user mapping (there must not be two portal users mapped to the same back end user). This back end user must have the role SAP_BC_UWL_SERVICE.
Snapshot Refresh Period (in minutes)     All items at the current time are fetched from the backend (for example from the SAP Business Workflow). The cache is synchronized thereafter. New / modified / deleted / updated items are fetched every session (every log on) if you leave the field value empty or enter a negative number.To specify a particular time frame for which the refresh occurs, enter the number of minutes
The above registration procedure is usually sufficient to use a UWL iView. Item type retrieval and registration requires a connection to the systems and may take a couple of minutes.
For each system, they are generated as the configuration named uwl.webflow..
In Manager Self-Service (MSS), the Universal Worklist groups together in Workset: Work
Overview the various workflow tasks and alerts that are relevant for a manager.
The standard MSS delivery includes the configuration file com.sap.pct.erp.mss.001.xml for the universal worklist.
1. In the portal, choose System Administration →System Configuration →Universal
Worklist and Workflow →Universal Worklist →UWL Systems Configuration.
2. Create the following system connections:
If you have already registered a suitable connector to the system connected to
the system alias, the existing connector is sufficient and you do not have to
register an additional one.
○ System alias: SAP_ECC_Financials
Connection types:
■ WebFlowConnector
■ AlertConnector
○ System alias: SAP_ECC_HumanResources
Connection type WebFlowConnector
○ System alias: SAP_SRM
Connection type WebFlowConnector
Leave the Web Dynpro Launch System field blank for all system connections.
With regards
subrato kundu

Customising Universal Worklist

Hello All,
I am attempting to customize the Universal Worklist for MSS. There are various buttons such as 'Launch Web Dynpro' , 'Resubmit', 'Forward' and 'Assign to me' that appears for the manager when authorizing a leave request.
Any Ideas on how I remove these buttons?
Many Thanks,
Nick

hi,
If you want to customise the UWL then, first you have to make a copy of the UWL iviews from Content Administration >Portal Content > Content Provided by SAP >End User Content >
Standard Portal Users >iViews > Universal Worklist.
From there you have select the iviews, copy it to your own folder , say 'Custom'. Apply the changes over there. Now Create an workset, set the entry points of the ivews and workset to true. Now create a role. Assign the workset to the role. Add the role to the user. Hence you can personalise your universal worklist.The below given link will explain all in detail:
[http://help.sap.com/saphelp_nw70/helpdata/en/57/c223be82104792a15c2df11377b9ed/frameset.htm]
However to customise, you have to make the changes in the folder Content Provided by SAP itself, and then apply it. However this is not desired, since all the users added to the Enduser and Standard user role will be affected. For further information look into the file:
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/904ca240-63bc-2a10-1c98-de81b6a045bf]

Universal Worklist : launch workitems ?

Similar Messages

Maybe you are looking for