<div>Hi Mike (& others)<br> </div>
<div>I have actually managed to go back to the old and well loved style in ECC6 itself! </div>
<div>If you don't know this then follow the steps below otherwise my apologies....</div>
<div>Go to Personal settings and select Classical in both</div>
<div>Then, everytime you display the log just go Alt+i+w+i OR Views->Other views->View with tech details OR Ctrl+Shift+F10, this is much better than waiting in the traffic.....I personally am used to blindly doing Alt+i+w+i...it works!</div>
<div> </div>
<div>Good Luck!</div>
<div> </div>
<div>Best Regards<br>Ravi Dixit <br> </div>
<div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Date: Fri, 7 Mar 2008 09:16:58 -0600<br>From: "Sample, Rick" <<a href="mailto:Rick.Sample@gbe.com">Rick.Sample@gbe.com</a>><br>
Subject: RE: ECC Log format (warning: rant)<br>To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>Message-ID:<br> <<a href="mailto:1897E92A96C47648A6574CB9A51C6407056B25DE@SEBEV1PW.graybar.com">1897E92A96C47648A6574CB9A51C6407056B25DE@SEBEV1PW.graybar.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br><br>Get the petition out, burn down the... Oops! wrong group! ;<br><br>I agree. Over kill with the useless graphics.<br><br>In the beginning... with ECC6, you could not view the container<br>
contents in the log. Dumb! Where was SAP QA dept?<br><br>But, I complained and they listened. So, if you want to actually see the<br>values<br>of container ops, be on support package 14 or greater, or get the oss<br>note note 1082156.<br>
<br>p.s.<br>After about one day of hands on, I switched and NEVER use the new one.<br>I changed my view to Classic View but still have to ctrl-shift-10 to get<br>the details. Every time. PIA!!!<br><br>Sign me up on the petition.<br>
<br>Rick Sample<br>SAP Business Workflow Developer<br>Graybar, Inc.<br><br><br>"We must hang together, gentlemen...else, we shall most assuredly hang<br>separately."<br>-- Benjamin Franklin<br><br>Oops! wrong group! Again! ;<br>
<br><br><br><br>________________________________<br><br>From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] On Behalf<br>
Of David Trant<br>Sent: Friday, March 07, 2008 8:16 AM<br>To: SAP Workflow Users' Group<br>Subject: RE: ECC Log format (warning: rant)<br><br><br>I won't be at ASUG to comment in person, but add my "vote" to the list!<br>
I don't know how many times I've sat with a superuser trying to debug a<br>production workflow issue and said, "well I used to know how to do this,<br>but I can't seem to find the &#*! thing anywhere now...." :-)<br>
<br>Happy Friday,<br>David<br><br><br><br>________________________________<br><br><br>> From: <a href="mailto:keohan@ll.mit.edu">keohan@ll.mit.edu</a><br>> To: <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>
> Date: Fri, 7 Mar 2008 08:13:21 -0500<br>> Subject: RE: ECC Log format (warning: rant)<br>><br>> Hi Mike,<br>><br>> I too have felt this pain, with our upgrade to SRM 5.0 though.<br>> One thing I know is that I've never spent that much time with the new<br>
log. I click on the log icon, and get the new view, and then hit<br>Control-P which gives me the 'old technical view'.<br>> Yes, I've tried various WLC parameter settings, but none of them<br>brings me to the technical view, so CTRL-P and I are now good friends<br>
(although sometimes it wants to print the log instead).<br>><br>> One area where we might have some recourse with SAP is via the ASUG<br>Influence Council, specifically the one taking place this May at the<br>ASUG Annual Conference. The WF/BPM luminaries will be there, and it's an<br>
opportunity to help them feel our pain. Those of you in other<br>geographies may have similar 'Influence Councils' in your user groups,<br>and I encourage you to make use of them.<br>><br>> I don't think it's just a matter of teaching an old dog new tricks, as<br>
Mike is a very much younger dog than I. Perhaps someday we will<br>understand the reasoning behind this 'enhancement'.<br>><br>> Glad your mouse has a cord,<br>> Sue<br>><br>><br>><br>> ----<br>
> Susan R. Keohan<br>> SAP Workflow Specialist<br>> MIT Lincoln Laboratory<br>> 244 Wood Street, LI-200<br>> Lexington, MA. 02420<br>> Ph: 781-981-3561<br>> Fax: 781-981-1607<br>> <a href="mailto:keohan@LL.MIT.EDU">keohan@LL.MIT.EDU</a><br>
><br>><br>> -----Original Message-----<br>> From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] On<br>Behalf Of Mike Pokraka<br>
> Sent: Friday, March 07, 2008 6:35 AM<br>> To: <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>> Subject: ECC Log format (warning: rant)<br>><br>> Hello wuggers,<br>><br>> Am I the only one who gets the same feeling from the new ECC workflow<br>
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<br>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,<br>stupid.<br>> I'm sorry if this upsets some people who have invested significant<br>time<br>> into this as it's a fairly complex tool and looks very pretty, but it<br>
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<br>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<br>
the<br>> wrong one.<br>><br>> 5. Click to expand other one, realize you need a SECOND click to<br>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<br>
are<br>> more forks further down.<br>><br>> 7. Think how nice it would be to sit in a traffic jam on a Friday<br>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<br>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<br>
out<br>> the ones you're interested in. Luckily mouse is attached by a cable<br>(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<br>
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<br>
SAP<br>> to re-design it or at least in the meantime give us our old log back<br>as a<br>> *default* option?<br>><br>> I can't help thinking one or two development requests are not going to<br>cut<br>> it, and even if they respond via that route then the thought of<br>
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></blockquote>
</div>