UWL Universal Worklist use User Role Negate Filter

Hi, SDN Expert.
In my UWL configuration, I am trying to exclude to display my task items to one user role.
I know that the "User Role" parameter can help me to restricts/allows who can get work items via the user role. I can also have multiple user roles separated by semi-colon to cover all the roles to receive the task.
BUT in my case, I only want few roles NOT to receive the task items, and all other roles to receive them.
My question is can I use the "NEGATE SIGN" , "!" (means Not Equal To) to exclude the particular user role to receive the task item, says I want to exclude the role name: "mydemorole", I just enter this "!mydemorole" in the "Use Role" parameter of the UWL configuration.
If NOT, what is the right way I should use to achieve this purpose?
Thanks for advise,
KC

Michael, you can do this in the UWL but only with a 6.40 backend (ex. ECC 5) with a specific patch level (can not remember that patch level).
Before this you need to set these substituion in the R/3 inbox.
This being said it is only for workflow task routing. If I read your message correctly you want a manager to assign his authorizations (roles in R/3 or the portal) to a secretary. This is not supported in any standard SAP (or portal) scenario as far as I am aware.
Cheers,
D.

Similar Messages

Query Result Filtered using User Roles SCSM 2012 R2 RU2

Hi,
I have a Query Result setup in a Request Offering that shows the list of Printers using the Printer CI. We have different sites with printers that start with the site location like MTL. There are no filters in the Query Result. What i did is create a Group
for each site that has the rule "start with" MTL (other groups have other 3 letter prefix). Then i created a user role for each group and only selected the Printer group for the site and i associated the User Role with our AD Site group called MTL-User.
i did this for each site. Now when i checked the Request Offering at first, with a user that is part of MTL-User group, it showed only the list of printers that started with MTL. Now today i came to check again and the same user is seeing all the printers
and not just the ones that start with MTL.
The User Role i made was based on the Read-Only Operator. I just dont know what the problem is

Thanks for that link. I had thought of something like that but i found it came to the same thing as just using the filter field that is already available when using a Query Result. I retried using User Roles and figured out that the problem is that my test
user is only part of the MTL-USER group so when i logged in with him into the portal (cireson Portal btw) i would see the proper result. If i logged in with a actual user that is also part of other groups besides MTL-Users, they see all the printers no matter
which AD group i define in the User Role.
So what i figured was that my group is not getting applied as the filter to the query Result and that the Member section in the User role is only to say who can see the Query result list. But then i have my test user for which this setup works...so im confused
on what exactly is overriding the results.

Universal worklist using guided procedure

Hi ,
Can any one send me the simple example which will demonstarte the use of universal worklist using guided procedure.
Thanks.

Hi,
Please go through the link below:
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/6b66d7ea-0c01-0010-14af-b3ee523210b5&overridelayout=true
The below link gives all the info required for GP.
SAP Composite Application Framework - CAF Tutorial Center
Hope this helps.
Cheers-
Pramod

UWL/Universal Worklist/Substitution - Removing the "Rule Activation" column

Hi SDNers,
From the Universal Worklist, it is possible to access the "Manage Substitution Rules" screen, in which one can manager substitutions over its colleagues.
I would like to remove a column in the standard "My Substitution Rules" table : the "Rule Activation" column.
Is there a way to do it ?
Regards

Michael, you can do this in the UWL but only with a 6.40 backend (ex. ECC 5) with a specific patch level (can not remember that patch level).
Before this you need to set these substituion in the R/3 inbox.
This being said it is only for workflow task routing. If I read your message correctly you want a manager to assign his authorizations (roles in R/3 or the portal) to a secretary. This is not supported in any standard SAP (or portal) scenario as far as I am aware.
Cheers,
D.

¿How to use user-roles in Ironport WSA (7.6) using ACS 4.1?

Hello,
I want to give a client access to a S370 WSA quarantine and I am using an ACS 4.1 for external authentication; that would be used for administrators and for the client access (non-administration access).
I have created a user-role in the WSA that has access to the quarantine I want, but I need the user to be in the ACS. I created the user in ACS but my question is, what should I configure or change in the ACS in order for the WSA to recognize the user with the specific role I created and not like an administrator role.
Thanks for your help!
Sergio

Hi,
This can be done by configuring the Radius Class attribute on the ACS and mapping it with the user roles on the WSA.
"To map RADIUS users to different Web Security appliance user role types, you assign a role type, such
as Administrator and Operator, to a RADIUS CLASS attribute. Mapping different role types lets you
specify the authorization level for each RADIUS user."
Please go to Page 26-12 of the WSA user guide http://www.cisco.com/c/dam/en/us/td/docs/security/wsa/wsa7-5/user_guide/WSA_7-5-0_UserGuide.pdf for more information under the section "Using External Authentication".
Regards,
Kush

Universe prompt using User:[0,-1] not parsing in XI 3.1 ?

Hi all,
We're using @PROMPTs setup in the universe as filters so as to allow prompts in reports.
An example of what we have is
(@Select(AllValues\Entity In List) IN @Prompt('Select Entity', 'a','AllValues\Entity In List',multi,Constrained,Not_Persistent,,User:-1))
When I press the [Parse] button in the Edit Properties window we get an error
Parse failed: Invalid definition (UNV0023). Error parsing default values parameter (7th parameter).
I spoke to some colleagues and they were told that the 'User:n' was no longer supported in XI 3.1 and so I removed it and can then parse the WHERE clause now.
This, of course, means that I need to do this 'fix' for all prompts we have setup like this.
My questions are
1. Is User:n not supported in XI 3.1 ?
2. Is the User: parameter even a supported feature? Some colleagues seem to think it was some sort of black-art tip.
3. Do you know of any other way of implementing this in a universe?
I'd really welcome your input/coments on this.
Regards
Gary

The "user" parameter was not supported because it was in the universe, not a report. In a report there was a facility to move prompts up or down. In a universe, there is no document, so the concept of prompt order is out of scope. Previous versions of Designer might have allowed the object to parse, simply because it was ignored.
Have you tried using the object in a report to see if it works? Sometimes an object will fail to parse in Designer but will work in Web Intelligence.

Configuration problem Universal Worklist (UWL)

Hi,
I'm trying to do the configure the Universal Worklist using the
<a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fa21a890-0201-0010-708b-d0cfc117e7cd">How to Configure the Universal Worklist.pdf</a>.
Problem is that I can't find the 'Registration for Item Types of Universal Worklist Webflow' in System Administration -> System Configuration -> Universal Worklist.
Does anyone know where it went or how I can make it visible again.
Thanks in Advance,
Jeschael

Hi Jeschael,
I have the similar kind of issue with my UWL.
Could you please help in Configuring UWL.
I will be grateful if you can share any docs or any sought of assistance will be appreciated.
Screenshot for your reference:
Thanks in advance.
Srikanth Naidu. Akula

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

Universal Worklist iView not visible///

Hi All,
We have installed EP & I have done the required configuration from SAP HCM module side & everything is working on fine except that I'm not able to see the My Organizer iView (Universal Worklist iView) in the ESS. I can see the other iViews like Employee Search, Working Time, Travel & Expenses etc. My workflows are also working properly just that the iView is not appearing on ESS. Please suggest what configuration is missing & how to do this config.
System Details:
EP version: 7.0
BP ESS/MSS: 11
EHR & SAP HCM package level: 24
Regards,
VJ

have you assigned the standard roles ie for portal and ess role
check in UWL administration
Does the same issue occur when you go to Content Administration and
preview the iview with the following PCD address (Standard UWL iview
provided by SAP)?
Portal Content/Content Provided by SAP/End User Content/Standard
Portal Users/iViews/com.sap.netweaver.bc.uwl.iviews/Universal
Worklist
check the roles and permission assigned to this user again
Please see the UWL Wiki @
http://wiki.sdn.sap.com/wiki/display/BPX/UWL%20FAQ *

VL10 User Role Tracking

VL10 User Role Tracking
Hi Gurus,
In VL10 t-code we have 6 tab pages in the initial screen.
Last one is "User Role". in this we will have several roles.
Assume that we used user role 1 and created deliveries. How to track those deliveries in LIKP or LIPS tables. Where in sap tables i can find the role used to create respective deliveries.
Actually i am planning to customize one user role and add it to VL10, so i need to track in the code, if user role = 2 then only make changes....
else come out of the changes;
kindly suggest me the table and field names to track deliveries based on user roles of VL10 t-code.
Please help me on this as it is very urgent;
thanks in advance
Sunil

Hi Sunil,
Wondering if you ever found a solution for this problem. Becos, I am also in a similar situation and your experience would be of great help if you share it.
Advance Thanks,
Anand.

User role

Hi
I have a 11g ADF application and a 10g Weblogic server. The ADF application was setup to use users/role within Weblogic using lpad having it's own login screen.
We've recently implemented SSO and removed all previous security within ADF, only setting the security attributes to Authentication.
I am now extracting the username with the following solution highlighted in the blog below
http://adfbugs.blogspot.co.uk/2010/05/user-principal-is-not-propagated-to.html
Is there anyway I can extract the role in a similar method? The user role is extracted from the database when the user logs in.
Thanks

I have a 11g ADF application and a 10g Weblogic serverCan you be explicit with your version numbers, please - Weblogic 10.3.x is version 11g.
11g and 10g are just marketing names, what are the exact version numbers (in other words, are you sure you have the right version of WLS/ADR for your ADF app).
Plus - remember a user can have more than one role. If it's something custom retrieved from the DB, then you can write the appropriate code to get it for you.

User, user roles and previllages

I have made all the tables under one user for my oracle forms, is it a good approach or should i use multiple users for this and how can i use user roles and villages for oracle forms?
Thanks
Hina

In our organization, we usually has an application owner and another schema with limited privilege to connect to from application (in this case forms). For example we have application owner say DBO which owns all the objects in the application and another user IA_APP is there to connect to database from application. Privileges such as SELECT, INSERT, UPDATE, DELETE is given to IA_APP user. Object access is provided through public synonym. You can do analogy to this in your application and database.
Regards,
Virendra

User roles property, when system alias is configured in universal worklist

Hi,
I am configuring system alias in Universal Worklist Configuration. I have keyed in system alias and connector type and saved the system alias and its working fine.
Apart from system alias and connector type, there are other properties like "User Roles, Delta Pull Channel Refresh Period(in seconds) and Delta Pull Channel Snapshot Refresh Period(in minutes). Can you any let me know what is the use of these properties.
I heard that "Delta Pull Channel Refresh Period(in seconds)" is the time period to refresh the UWL is it correct.
Thanks & Regards,
H.K.Hayath Basha.

Try searching the http://help.sap.com SAP NetWeaver pages for delta pull!

"You can also" link in UWL work item when using user decision step in workflow

Hi,
Just want to check if anybody has tried adding links to this section in the UWL when using user decision step? I need to pass some custom links which will be calling some webdynpro applications and backend transactions. I have read somewhere that Ineed to modify the XML file but don' t know how the next steps once I have defined (i.e. how to handle those links).
Thanks in advance.
Rammel

Hi Rammel
I hope you are keeping well and many thanks for using the SAP Discussion Forums .
Based upon your scenario you mentioned that:
You want to add links to the "You Can Also" section in the UWL with user decision steps
In an effort to pass custom links (calling web dynpro) applications.
You wish to know how to modify the XML
Ok now based upon the scenario there are two key points regarding XML files and efforts to change them.
Remember that XML in terms of the UWL follow the notion of precedence. Now that means that once you make a change to an XML file you need to re-upload it to realize changes. To re-upload an XML file and realized changes you need to do so with a "High" or "Very High" priority and also ensure that the UWL Cache has been cleared of the UWL Service restarted so changes can be realized.
The second key point is to ensure that you backup all current XML files before making any changes so you can easily revert those changes if required.
Now reverting back to your query, the XML files and the "You Can Also" section. Kindly see the documentation outlined below as here you are going to make changes to the I-View configuration:
Configuring the UWL
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a3461636-0301-0010-3787-978f5ac8bd45?overridelayout=t…
UWL Content Configuration
UWL Content Configuration - Configuring the Universal Worklist - SAP Library
Kindly update me as per your findings.
Kind Regards & All The Best
Troy - Enterprise Portal Support Engineer

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

UWL Universal Worklist use User Role Negate Filter

Similar Messages

Maybe you are looking for