UWL Navigation

[Cooper, John M]

Hi Jocelyn,
 
I found the help ok, and I used a TREX search as well, just in case
there was something hidden off in another section of the help where I
didn't think to look.
 
The documentation is good for adding new item types, but it does not
address eliminating something defined in the standard xml files.
Customizing only seems to work to override existing standard itemtypes,
views, etc., or to add new ones. =20
 
I spent a week in Palo Alto talking with the UWL and Ad Hoc Workflow
product managers and developers last March, and am probably one of the
reasons that note 738398 was written.  (I added the New Ad Hoc Request
button back to our systems in February during our EP6 ramp-up project.)
My experience with the developers is that their heads are in the design
and development process for versions we won't see for quite some time,
and it is quite difficult for them to remember back to existing
production releases.  A lot of water has gone under the bridge since
they worked on those releases, so it takes a while to get answers, even
when you can go direct.  However, your guidance in posing OSS queries is
brilliant, most appreciated, and I will follow it!=20
 
I understand the hierarchy of both the XML files and the ItemType names,
and I have some PowerPoint presentations on ItemType creation and Task
Launch Customization topics which used to be available on SAP Service
Marketplace, although I cannot find them again on the current EP-based
version.
 
Best regards,
John
 
-----Original Message-----
=46rom: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Dart, Jocelyn
Sent: Wednesday, July 14, 2004 3:16 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: UWL Navigation
 
 
Hi John,
Make sure you have the latest patch available and have checked the OSS
notes under component EP-BC-UWL.
 
Did you find the help=3F Path is:
help.sap.com
SAP NetWeaver
Release 04
People Integration
Portal
Admin Guide
Super Admin
Standard Portal Content
Default Iviews
The Universal Worklist (includes a link to the Universal Worklist end
user guide, and authorization requirements)
Configuring the Universal Worklist / Ad hoc workflow Administration /
Task Launch Customization
 
You'll probably find Configuring the Universal Worklist (which deals
with registering Item Types) and  Task Launch Customization the most
useful for what you are trying to do.
 
It does give XML examples and hints such as:
"Choose the appropriate configuration that is to be customized. If it is
intended that this customization should affect all Business Workflow
related Configurations, choose "uwl.webflow" as the configuration.
Otherwise choose the configuration specific to the system for which
ItemTypes are customized."
 
You are correct in deducing that all of the XML files need to start with
uwl.  What comes after that indicates whether the uwl file applies to
all work items or only to work items from a particular system.  Make
sure you conform to the UWL DTD of course.
 
There's also an example of working with UWL actions in OSS note 738398
that you may find interesting.
 
There is some more help documentation to come with SP3 - but the best
place to look for the latest doco is still help.sap.com.
 
Your changes won't be visible immediately.  You need to clear the cache
via the Universal Worklist Cache Admin and  start a new browser session
to see the changes as well as logging out and back in. If that still
doesn't work, try restarting the portal itself.
 
If you are on a WAS system you can also use transaction SWFVISU to make
some changes, but the XML allows greater control.
 
EP6.0 SP3 gives wider control over custom attributes and the UWL display
generally.
 
And of course if you really can't find out how to do something in the
documentation or your customized file doesn't seem to be being used
despite following the documentation query it via OSS/service.sap.com,
i.e. don't frame it like a consulting question, frame it as "current
documentation in .... doesn't tell me how to... please point me to the
doco/values to use when I want to ... business reason we want to do this
is...".   Business reason is important - developers love to understand
how people want to use the applications they have created, and this
=66eeds into future support packs/releases.
 
Remember a lot of this is still relatively new - so use
Oss/service.sap.com to talk to the developers and get their input on
what you are trying to do and how you are trying to do it.
Regards,
Jocelyn
 
 
 
-----Original Message-----
=46rom: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Cooper, John M
Sent: Wednesday,14 July 2004 7:34 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: UWL Navigation
 
 
I've spent most of my day reviewing the copious detail that explains
everything in the Netweaver '04 documentation on help.sap.com, and
trying various approaches that are implied in the doco.  I cannot find
any references to changing the standard tabs available in the UWL.
 
I did find a reference to something in the iView configuration called a
sap_uwl_namespace, with an explanation that it provides a way to "Change
the default name space which is used in conjunction with the view name
above."  That sounds like it might be usable, if one could copy the
uwl.standard.xml and get it to upload to a new namespace, then change
the iView to default to the new namespace.
 
Unfortunately, the UWL Administration iView doco does not go into any
detail about how namespaces should be named, and various attempts at
coming up with new namespaces result in helpful error messages being
displayed such as "Duplicate Item type names. Name already registered".
Hmmm.  I guess ItemTypes have to be globally unique, not just within the
namespace.
 
Changing all the ItemType names in the xml file, changing the
SupportedItemTypes for each View to refer to the new ItemType names, and
changing the viewNamespace parameters in the NavigationNode section of
the xml to reference a new namespace results in the error message "Item
type name should start with but it has".  Hmmm.  I wonder if ItemType
names all have to start with "uwl."=3F
 
Changing all the ItemType names again to have "uwl." as the first part
of the name, and rippling that change through results in a successful
upload.  Updating the UWL iView parameter (sap_uwl_namespace) to
reference the new namespace, clearing the item cache, logging out and
back in and checking the UWL results in .... absolutely no changes to
anything.  Hmmmm.  Sure glad all of this is explained in the doco!
 
Serge, the Add to navigation buttons don't show up in our system either.
I suspect it was something from early on in the UWL design.
 
John
 
 
-----Original Message-----
=46rom: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Dart, Jocelyn
Sent: Monday, July 12, 2004 9:14 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: UWL Navigation
 
 
Serge/John,
The documentation for how to change the UWL configuration is under the
Netweaver 04 doco in help.sap.com.
Everything is explained there in copious detail. So try that first.
Jocelyn
 
-----Original Message-----
=46rom: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Serge Boulay
Sent: Tuesday,13 July 2004 6:06 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: UWL Navigation
 
 
Thanks John,
 
If i found something, which i doubt, i'll let you know... By the way do
you
see on your UWL the button for removing and adding from the Navigation=3F
If
you look at the XML, there should be there but they are not.
 
Thanks
 
Serge
 
 
-----Message d'origine-----
De : SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] De la part de
Cooper, John M
Envoyi : 12 juillet 2004 13:43
@ : SAP-WUG at MITVMA.MIT.EDU
Objet : Re: UWL Navigation
 
Hi Serge,
 
I was trying to do the same thing, without success.  It seems that if
you are removing sections (e.g. ItemType, View, NavigationNode) from
your customized version it reverts to the definition in the original
uwl.standard.xml file.  I think that in order to get rid of
Notifications altogether you would actually have to replace the standard
version of uwl.standard.xml.
 
In earlier versions of EP6 (we are on SP2 Hotfix 4) I was able to do
this, but in our current version it protects the standard version of the
=66ile (so why is there an option for it=3F!).
 
Best regards,
John
 
-----Original Message-----
=46rom: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Serge Boulay
Sent: Monday, July 12, 2004 1:47 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: UWL Navigation
 
 
Hi All,
 
 
 
I am looking at the Universal Worklist in EP6. Is there a way of
removing
some of the tabs (ex: Notification)=3F I am trying with the XML file and
the
navigation tags but it does not work=3F!=3F!=3F!
 
 
 
Thanks.
 
 
 
Serge Boulay
 
HR/Payroll & Workflow Consultant
 
 
------------------------------------------------------------------------
----
--
This e-mail is intended for the use of the addressee(s) only and may
contain
privileged, confidential, or proprietary information that is exempt from
disclosure under law.  If you have received this message in error,
please
inform us promptly by reply e-mail, then delete the e-mail and destroy
any
printed copy.   Thank you.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=3D
=3D=3D
 
 
------------------------------------------------------------------------
------
This e-mail is intended for the use of the addressee(s) only and may
contain privileged, confidential, or proprietary information that is
exempt from disclosure under law.  If you have received this message in
error, please inform us promptly by reply e-mail, then delete the e-mail
and destroy any printed copy.   Thank you.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=3D=3D=3D
 
 
------------------------------------------------------------------------------
This e-mail is intended for the use of the addressee(s) only and may contain =
privileged, confidential, or proprietary information that is exempt from =
disclosure under law.  If you have received this message in error, please =
inform us promptly by reply e-mail, then delete the e-mail and destroy any =
printed copy.   Thank you.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D