Better handling of role resolution failure (Was RE: 2 year waitvs Batch Report)
Tiwari, Rammanohar
rammanohar.tiwari at logicacmg.com
Mon May 9 09:17:54 EDT 2005
Hi Kjetil,
Nice mail.
I would like to implement the NewJoiner-female employee-single-25To35 notification workflow but I'll try to keep it a secret and my user-id will be hardcode as for as role-resolution is concerned :-).
About triggering events based on changes in PA0002-FAMST - seems to be a good idea. Some time employees waste a lot of effort and resources on wrong targets, due to lack of information.
Another one. Thankfully that's still not a real requirement in my part of the world (India), but I'll suggest you guys must consider it, I guess it's in fashion over there. Watch out for a change in PA0002-GESCH :-)
Good thing SAP made it time dependent.
Cheers,
Ram
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
Of Kjetil Kilhavn
Sent: Monday, May 09, 2005 12:35 PM
To: SAP Workflow Users' Group
Subject: Re: Better handling of role resolution failure (Was RE: 2 year
waitvs Batch Report)
Don't you have the "remember to send a congratulations e-mail" workflow
going to all subordinates (not only direct subordinates) on birthdays? So
once a year, when the top guy has a birthday everyone should receive it and
send him (let's face it, statistics indicate it is a he) a "happy birthday"
e-mail. Well, we don't have it here either, but it would be a bit cool.
Just a bit though, as the CEO probably wouldn't be so happy about the 2 000
e-mails (assuming one in ten responds).
The other Very Useful (tm) workflow would be the one which sends a
notification to all single employees when a single person of the opposite
sex is employed at the same office location :-) Hmm... considering the
state of the world today it would probably be wise to also have a
triggering event based on changes in PA0002-FAMST.
Ram's suggestion would be a bit like the solution for what happens to an
event linkage when there is an event error where you can specify that it
should act like the system default or specify explicitly what should happen
for your particular linkage. Good idea.
--
Kjetil Kilhavn
Peter Roehlen
<theycallmepete at yah To: sap-wug at mit.edu
oo.com.au> cc: (bcc: Kjetil Kilhavn)
Sent by: Subject: Better handling of role resolution failure (Was RE: 2 year wait vs Batch
sap-wug-bounces at mit Report)
.edu
06.05.2005 07:22
Please respond to
"SAP Workflow
Users' Group"
Hi Ram,
I don't know about any 'right' to make mistakes but I think your idea is a
good one. In my experience, most tasks with a standard role end up as a
General Task particularly if the pool of possible agents can't be confined
to a specific business area or a few other categories.
I doubt that there has ever been a workflow that has been intentionally
designed to go to all users in the business so a global or workflow level
setting to prevent this would be very valuable. In lieu of that, I'd
settle for the 'Terminate' flag to be defaulted to 'on'.
Cheers
Peter Roehlen.
Date: Thu, 5 May 2005 21:52:02 +0530
From: Ram Manohar Tiwari <rammanohar.tiwari at gmail.com>
To: sap-wug at mit.edu
Subject: RE: 2 year wait vs Batch Report
Hi Peter,
But for your case, I will put some blame on SAP as well.
I mean how many times do we actually want to forward any workitem to
all the users in the system.
Also, we are developers and I think it's our right to make mistakes.
It's SAP's responsibility to stop us.
I think SAP should provide a way for workflow administrator to decide
what should happen if no agents could be determined ( specially for
general tasks ).
* Forward it to all users
* Don't forward it to anyone and send a WI to the Administrator
who will decide what needs to be done.
That config should be placed at workflow system configuration level,
Workflow Level and then at Task Level.
Am I thinking loud?
I hope I am not in the process of finding another example for my Book :-)
Cheers,
Ram
<<<
Hi Ram,
Make sure you look me up when you write your book. I'm sure that I've
got more than a couple of contributions I can make from my own painful
experiences. For example, have you ever brought a companies mail
system to a screaming halt by moving a new general task into PRD and
forgetting to set the 'terminate if role resolution has no result' on
the standard role? (Trust me, I'm a workflow expert... : )
Anyway, it's all good fun.
Cheers - Peter.
>>>
Find local movie times and trailers on Yahoo! Movies.
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
More information about the SAP-WUG
mailing list