<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16830" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2>Hi Steffen, </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2>What is entered in SWFVISU is used to adjust the generated
uwl.webflow.<systemalias> file and also some behind the scenes
stuff.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2>The object visualization changes don't show directly in the
XML from what I can tell. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2>Your custom XML is ALWAYS applied on top of generated files
- i.e. custom files are always of at least MEDIUM priority (generated files are
always LOW). There's no problem with maintaining it twice - I would usually
recommend it anyway as the generated file forms a reasonableness check for code
in your own custom XML and if for any reason your custom XML file is missing in
one of your portals at least you don't lose all of your desired beaviours.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2>The label of your object attachment comes
from:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2>The name of the object type or ABAP class followed by the
default attribute value (this part of the label can be overridden using
BI_OBJECT~DEFAULT_ATTRIBUTE_VALUE). </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2>Probably you need to fix the name of your ABAP Class.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2>Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2>Jocelyn </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=566201923-14052009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Steffen
Schloenvoigt<BR><B>Sent:</B> Wednesday, 13 May 2009 12:38 AM<BR><B>To:</B>
SAP-WUG@mit.edu<BR><B>Subject:</B> [LIKELY JUNK]Hiding the Process object in the
UWL<BR></FONT><BR></DIV>
<DIV></DIV>Hi list,<BR><BR>In my UWL-workitems, the Process Object (an ABAP OO
Object) is shown as an attachment but I don't want to have it there.<BR><BR>I
know, that I can hide it using Transaction SWFVISU and setting the
"Visualization Type" there to "Object Not Represented".<BR><BR>I just wonder, if
there isn't a way to do this in the XML-Configuration too, since I thought that
everything set in SWFVISU will be reflectable in the XML and I don't want to
maintain two different configurations if it's avoidable.<BR><BR>Then to the
second point:<BR>If the object is displayed, how can I change the label of it -
I thought it should work by implementing the BI_OBJECT~DEFAULT_ATTRIBUTE_VALUE
but it doesn't.<BR><BR>Kind regards,<BR>Steffen Schloenvoigt<BR><BR
clear=all><BR></BODY></HTML>