SWW_WI_MAIL_SEND

George Caramaliu george_caramaliu at yahoo.com
Tue Oct 30 03:15:52 EDT 2012


Hello,

I am using FM SWW_WI_MAIL_SEND to send a message from workflow to another user requesting some information with reference to WI.
When we implemented this functionality, few years ago, I remember that the SAP mail was sent and the reply was received in the message owner inbox.
Now I see that when the receiver uses the reply button on the receiver address it is automatically prefilled only the work item, not also the message owner, so the reply can be seen only by checking the originating work item or workflow log.

Was something changed in the meantime or I do not remember correctly?


Thank you,
George


________________________________
 From: "Hilsbos, Margaret A" <Margaret.Hilsbos at dayzim.com>
To: SAP Workflow Users' Group <sap-wug at mit.edu> 
Sent: Wednesday, October 24, 2012 3:40 PM
Subject: RE: Agent assignment situation
 

 
Hi Robert,
 
I don’t understand why it can’t be done with standard “non-abap” workflow … but you would have to have the second iteration of the user decision as its own step. Can you do that?
 
Step 1 – UD – goes to group using rule – bind the actual agent to a workflow container element ACTUAL_AGENT.
Step 2 (or 2 through m) – goes on the selected path for processing based on the decision in step 1;
Step 3 (or n) – UD (same task as step 1) – use the agent returned in step 1 .
 
If “step 2” has multiple steps depending on the decision in step 1, you could use sub-workflows there and keep your main workflow very clean and simple.
 
Hope this helps. Good luck with it.
 
Margaret
 
From:sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Robert van den Berg 
Sent: Wednesday, October 24, 2012 7:51 AM
To: SAP Workflow Users' Group; SAP Workflow Users' Group
Subject: Re: Agent assignment situation
 
Hi Florin, Rick,
 
thanx for the replies. Too bad this can't be done on a standard non-abap way...
But the solution from Florin is a nice one.
 
Thanx for the quick replies!
Good to see that the WUG is still active..
 
kind regards,
Robert
 
 
On Oct 24, 2012 13:32 "Florin Wach" <florin.wach at gmx.net> wrote:
Hi,
>yes, I do the same, but within the Rule resolution implementation I usually add a container-element ACTUAL_AGENT. With the workflow, I do the same, i.e. storing the _actual_agent of the recurring step into a separate container element ACTUAL_AGENT_OF_DECISION...
 (or something appropriate) and pass this to the rule.
>
>The rule looks at first into the rule container, checks for the actual_agent element, and if found, it uses this one to the assigned agents and ends the processing, 
>otherwise the rule proceeds normally and find the group or whatever needs to be done. 
>
>best wishes, 
>Florin 
>
>
>
>-------- Original-Nachricht -------- 
>Datum: Wed, 24 Oct 2012 21:59:41 +1100 
>Von: Rick Bakker <rbakker at gmail.com> 
>An: "SAP Workflow Users\' Group" <sap-wug at mit.edu> 
>Betreff: Re: Agent assignment situation 
>Hello, 
>>
>>I would use a container element Current_Agents for the agent and not 
>>use a default rule. 
>>Fill Current_Agents in a step or steps before the user decision. 
>>
>>If a different container element, say Actual_Agent, is empty then have 
>>a step (which calls a task which calls a method that calls fm 
>>RH_GET_ACTORS which calls the rule) to fill Current_Agents, otherwise 
>>assign Actual_Agent to Current_agent. 
>>
>>Actual_Agent is filled with the actual agent of the user decision step. 
>>
>>regards 
>>Rick Bakker / hanabi technology 
>>
>>On Wed, Oct 24, 2012 at 9:43 PM, Robert van den Berg <wug at bergtop-ict.nl> 
>>wrote: 
>>Hi all, 
>>
>>
>>
>>I have a situation where I have a step (user descision) in the workflow 
>>which goes to a group of people via a rule. 
>>
>>Person A takes the task, chooses an option and the next step goes to a 
>>different department. When this task is done, the workflow returns to 
>>the 
>>user descision but I want this task only to be delivered at person A, 
>>not to 
>>the whole group. 
>>
>>
>>
>>I tried to do this using the default rule on the task and on the step, 
>>using 
>>a container element for the agent. So at first, the containerelement is 
>>empty and I assumed that then the default rule would be used. 
>>
>>But now I see that the workflow runs in error because the agent could 
>>not be 
>>determined. 
>>
>>
>>
>>How can I create this requirement? 
>>
>>
>>
>>Kind regards, 
>>
>>Robert 
>>
>>
>>_______________________________________________ 
>>SAP-WUG mailing list 
>>SAP-WUG at mit.edu 
>>http://mailman.mit.edu/mailman/listinfo/sap-wug 
>>_______________________________________________ 
>>SAP-WUG mailing list 
>>SAP-WUG at mit.edu 
>>http://mailman.mit.edu/mailman/listinfo/sap-wug 
>_______________________________________________ 
>SAP-WUG mailing list 
>SAP-WUG at mit.edu 
>http://mailman.mit.edu/mailman/listinfo/sap-wug 
_______________________________________________
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/20121030/78a829fb/attachment.htm


More information about the SAP-WUG mailing list