<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
Mike,<BR>
I couldn't agree more, and the more complex the workflow the worse the problem.<BR>
<BR>
BTW it seems like I saw something previously on the WUG that told how to switch to the old log. Yes?<BR>
<BR>
Ed Diehl<BR><BR>> Date: Fri, 7 Mar 2008 11:34:32 +0000<BR>> Subject: ECC Log format (warning: rant)<BR>> From: wug@workflowconnections.com<BR>> To: sap-wug@mit.edu<BR>> <BR>> Hello wuggers,<BR>> <BR>> Am I the only one who gets the same feeling from the new ECC workflow log<BR>> as sitting in a traffic jam?<BR>> <BR>> <rant><BR>> I've tried to get used to it for over a year and I think at one point I<BR>> actually managed to discover a useful feature somewhere (though I've<BR>> forgotten what it was), but for most part it's just stupid. Yes, stupid.<BR>> I'm sorry if this upsets some people who have invested significant time<BR>> into this as it's a fairly complex tool and looks very pretty, but it just<BR>> doesn't cut it in the real world.<BR>> <BR>> Let's take looking at a container element for a step in the WF as an example:<BR>> <BR>> Old style:<BR>> 1. Click log icon to display workflow log.<BR>> 2. Click on container icon next to step in question.<BR>> 3. See container element of interest.<BR>> 4. Feel a sense of calm and wellbeing.<BR>> <BR>> <BR>> ECC log:<BR>> 1. Click log icon to display workflow log<BR>> <BR>> 2. Click to expand first fork.<BR>> <BR>> 3. See 'Branch 1' 'Branch 2', click on one at random.<BR>> <BR>> 4. Resist urge to use foul language in front of client because it's the<BR>> wrong one.<BR>> <BR>> 5. Click to expand other one, realize you need a SECOND click to expand<BR>> branch itself (what's the point of the 'Branch n' tree level?).<BR>> <BR>> 6. Click twice to switch to Chronological view when you realize there are<BR>> more forks further down.<BR>> <BR>> 7. Think how nice it would be to sit in a traffic jam on a Friday afternoon.<BR>> <BR>> 8. Click to select step of interest.<BR>> <BR>> 9. Click on Container tab.<BR>> <BR>> 10. Attempt to throw mouse out of window because scroll wheel doesn't work<BR>> in container tab sub-window, which is horizontal and and thus far too<BR>> small, and all the system elements are of course at the top, blocking out<BR>> the ones you're interested in. Luckily mouse is attached by a cable (at<BR>> least mine is) and can easily be retrieved.<BR>> <BR>> 11. Click several times to scroll down the container list to find the one<BR>> you want.<BR>> (If it's a mulitline element then clicking it causes it to expand and<BR>> cover the entire container in a way that is also really annoying, but<BR>> that's a whole different topic.)<BR>> <BR>> <BR>> Ummm... "New and improved"? Surely someone's been overdoing the happy<BR>> pills a little?<BR>> </rant><BR>> <BR>> <BR>> So, back to my original question: what are our options of pressuring SAP<BR>> to re-design it or at least in the meantime give us our old log back as a<BR>> *default* option?<BR>> <BR>> I can't help thinking one or two development requests are not going to cut<BR>> it, and even if they respond via that route then the thought of waiting<BR>> two years to see the result in ECC7 is just a bit much.<BR>> <BR>> Any opinions?<BR>> Cheers,<BR>> Mike<BR>> <BR>> <BR>> <BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR><BR><br /><hr />Helping your favorite cause is as easy as instant messaging. You IM, we give. <a href='http://im.live.com/Messenger/IM/Home/?source=text_hotmail_join' target='_new'>Learn more.</a></body>
</html>