Link to a transaction from a Workflow notification

[Alfano, Judy (ISO)]

Thanks Jocelyn. We'd like the workflow to resume based on action taken
in the custom transaction, not as the result of the user completing the
notification. So the flow would be:
 
1. workflow encounters a data problem that requires user intervention
2. creates an 'issue' object
3. sends notification with link and some issue details
4. wait step begins
5. a user resolves the issue, which raises an event - what's important
here is that the user may or may not have used the link in the
notification to get to the transaction. It may be a different user who
didn't even receive the notification. 
6. wait step reacts to the event and the workflow continues
 
Can I put the notification as a work item on one path of a fork, but set
it up so that that path doesn't need to be completed for the workflow to
continue processing? Putting the notification and the wait on 2 parallel
branches, and setting the necessary branch value to 1 isn't quite right
because I wouldn't want the processing to continue if the user completed
the notification but the wait step criteria hadn't been met. 
 
Thanks again,
 
Judy

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Tuesday, December 16, 2008 10:00 PM
To: SAP Workflow Users' Group
Subject: RE: [LIKELY JUNK]Link to a transaction from a Workflow
notification


Hi Judy, 
You seem to have conflicting requirements - do you want the action to
make the workflow resume or not? 
 
Normally you would just create a normal work item, and use Extended
Notifications to send an equivalent email notification with an execution
hyperlink included. 
 
If you want the workflow to continue past your notification step and
wait at a future point in the workflow, then that sounds more like a
situation where your work item should sit in one path of a fork - so
that other functionality happens in parallel to your work item. 
 
You can't use a send mail for this situation effectively.  And you can't
bind objects to a send mail step to do what you want.
 
Hope that helps. 
Regards,
Jocelyn 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Alfano, Judy (ISO)
Sent: Wednesday, 17 December 2008 10:29 AM
To: sap-wug at mit.edu
Subject: [LIKELY JUNK]Link to a transaction from a Workflow notification



Hello All -

 

I've seen many versions of this same question in the WUG Archives, so I
apologize if it sounds familiar, but none of the scenarios I found quite
fit my current dilemma. 

 

I need to send a notification that an issue has occurred during the
execution of a custom workflow, and need to include a link to a custom
transaction where a user will make a decision that will resolve the
issue. That action will raise an event that the workflow is waiting for,
causing the workflow to resume.

 

I'd like to use a simple Send Mail step, but I've been unable to figure
out how to bind our ABAP Objects object to the task, in order to execute
the default method and offer a link to the transaction. The
AdHoc_Objects or Attachments container elements seem to be specific to
BOR objects. 

 

I've been able to execute the default method and offer the link on a
Work Item, but don't want the workflow to wait until this Work Item is
completed to go on to the next step. 

 

Can you advise me as to the best way to send this notification with a
step that will not interrupt the processing of the workflow? 

 

Any advice would be greatly appreciated! 

 

Thanks and Happy Holidays,

 

Judy Alfano

MassMutual Financial Group

Springfield, MA

---------------------------------------------------------
This e-mail transmission may contain information that is 
proprietary, privileged and/or confidential and is
intended exclusively for the person(s) to whom it is
addressed. Any use, copying, retention or disclosure by
any person other than the intended recipient or the
intended recipient's designees is strictly prohibited. If
you are not the intended recipient or their designee,
please notify the sender immediately by return e-mail and
delete all copies.
---------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20081217/fa74d162/attachment.htm