ECC Log format (warning: rant)

[Neumann, Marcia]

No you are not the only one.  I'm with you.  Although changing the
workflow setting to Classical returns partially to the old log, it is
not enough.

I included this issue as our #1 top pain point in the survey ASUG did
late last year(ASUG Discussion Forum Post: Question from SAP: Top 5
Reports on Business Workflow).  Here is what I sent them even though it
might not have been exactly what they were looking for:

What are your top 5 pain points when designing and deploying these
reports?
1. Workflow Log - View with technical details (most frustrating and time
consuming pain point) 
In ECC 6.0 there is no way to make the view with technical details our
default when viewing the workflow log.  This is the only view that
contains all the necessary information we need to debug a workflow
issue.  Every time we want to look at a workflow log, we have to do
Ctrl+Shift+F10 in order to do our job.  ECC 6.0 went backwards in this
case.



Marcia Neumann
IT Claims Development/Support

Confidentiality notice: The information included in this e-mail,
including any attachments, is for the sole use of the intended recipient
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure, distribution or similar action is
prohibited. If you are not the intended recipient, please contact the
sender and delete all copies of the original message immediately.
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Pokraka
Sent: Friday, March 07, 2008 6:35 AM
To: sap-wug at mit.edu
Subject: ECC Log format (warning: rant)

Hello wuggers,

Am I the only one who gets the same feeling from the new ECC workflow
log
as sitting in a traffic jam?

<rant>
I've tried to get used to it for over a year and I think at one point I
actually managed to discover a useful feature somewhere (though I've
forgotten what it was), but for most part it's just stupid. Yes, stupid.
I'm sorry if this upsets some people who have invested significant time
into this as it's a fairly complex tool and looks very pretty, but it
just
doesn't cut it in the real world.

Let's take looking at a container element for a step in the WF as an
example:

Old style:
1. Click log icon to display workflow log.
2. Click on container icon next to step in question.
3. See container element of interest.
4. Feel a sense of calm and wellbeing.


ECC log:
1. Click log icon to display workflow log

2. Click to expand first fork.

3. See 'Branch 1' 'Branch 2', click on one at random.

4. Resist urge to use foul language in front of client because it's the
wrong one.

5. Click to expand other one, realize you need a SECOND click to expand
branch itself (what's the point of the 'Branch n' tree level?).

6. Click twice to switch to Chronological view when you realize there
are
more forks further down.

7. Think how nice it would be to sit in a traffic jam on a Friday
afternoon.

8. Click to select step of interest.

9. Click on Container tab.

10. Attempt to throw mouse out of window because scroll wheel doesn't
work
in container tab sub-window, which is horizontal and and thus far too
small, and all the system elements are of course at the top, blocking
out
the ones you're interested in. Luckily mouse is attached by a cable (at
least mine is) and can easily be retrieved.

11. Click several times to scroll down the container list to find the
one
you want.
(If it's a mulitline element then clicking it causes it to expand and
cover the entire container in a way that is also really annoying, but
that's a whole different topic.)


Ummm... "New and improved"? Surely someone's been overdoing the happy
pills a little?
</rant>


So, back to my original question: what are our options of pressuring SAP
to re-design it or at least in the meantime give us our old log back as
a
*default* option?

I can't help thinking one or two development requests are not going to
cut
it, and even if they respond via that route then the thought of waiting
two years to see the result in ECC7 is just a bit much.

Any opinions?
Cheers,
Mike



_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080307/dc04eac8/attachment.htm