Dynamic sender in extended notifications - possible?

[Rick Bakker]

Hello,

Extended Notifications notifies users when they have new workitems in
their inbox. So it IS an email coming from the system. Why would
anyone want to make it look like it came from someone else? What if
the recipient tries to reply to the email? What if the recipient
writes to the supposed sender directly and refers to an email that the
sender knows nothing about?

Just trying to provide some ammunition...

regards
Rick bakker
hanabi technology

On Thu, Aug 11, 2011 at 2:17 AM, Hilsbos, Margaret A
<Margaret.Hilsbos at dayzim.com> wrote:
> Thanks Mike, your answer tells me exactly what I was looking for. I agree with you about the system-generated vs. 'real person' thing. But I like to have a backup plan in case I need to pick my battles. :)
>
> Margaret
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mike Pokraka
> Sent: Wednesday, August 10, 2011 12:06 PM
> To: SAP Workflow Users' Group
> Subject: RE: Dynamic sender in extended notifications - possible?
>
> Hi Margaret,
>
> I would be very wary to use a 'real' sender in first place. It's
> misleading and I can't think of a reason to disguise the fact that a mail
> is system generated - quite the opposite in fact as I always make a point
> of emphasizing this!
>
> In extended notifications you can configure the deliverer. Not available
> in SWNADMIN, so you'll have to use SWNCONFIG. Create a custom delivery
> type and override the default CL_SWN_DELIVERER_BCS with your own. I notice
> it's not declared as final so you could even create a subtype. In here you
> can play to your heart's content. The tricky bit is figuring out where
> stuff comes from and tying everything together.
>
> Have fun,
> Mike
>
> On Wed, August 10, 2011 3:44 pm, Hilsbos, Margaret A wrote:
>> Hi Mike,
>>
>> Thanks for the suggestion. Let's assume for the moment that my users are
>> inflexible. They want to see the emails in Outlook coming from a real
>> person, not 'whatever system'.  Also assume I have good ABAP skills. In
>> that case, can you give me an idea where you would start with a custom
>> hack?  (I know I could suppress the task in extended notifications, and
>> send custom email with CL_BCS from a parallel workflow step. But I think
>> you mean something else, that would still use the extended notifications
>> job.)
>>
>> Thanks,
>>
>> Margaret
>>
>> -----Original Message-----
>> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
>> Of Mike Pokraka
>> Sent: Wednesday, August 10, 2011 10:28 AM
>> To: SAP Workflow Users' Group
>> Subject: Re: Dynamic sender in extended notifications - possible?
>>
>> Hi Margaret,
>>
>> Not by standard means, but a simple workarounds could be to change the
>> text, e.g. "Approve TNFD 1234 from Jeff White"
>>
>> Otherwise Extended Notifications is certainly flexible enough so that you
>> can custom-hack it, but it's a bit of a job requiring good ABAP skills.
>>
>> Regards,
>> Mike
>>
>> On Wed, August 10, 2011 2:56 pm, Hilsbos, Margaret A wrote:
>>> Hi WUGers,
>>>
>>> I have a requirement where it is important that that the notification
>>> email shows a real person as sender (e.g., 'Mike Jones') rather than a
>>> generic sender like 'Workflow System'. (The 'real person' in this case
>>> would be determined based on information in the object.)
>>>
>>> Is it possible to achieve this with extended notifications? I think it
>>> isn't, but I'm hoping I'm wrong and someone can show me the way.  I am
>>> aware that the sender name can be configured to a different static value
>>> in General Settings,  as in 'Alert System' instead of "Workflow System';
>>> but can it be dynamically determined based on instance data, such as a
>>> container element?
>>>
>>> Thanks for any advice you can give!
>>>
>>> Margaret Hilsbos
>>> Business Systems Analyst, Corporate IT
>>> Day & Zimmermann<http://www.dayzim.com/>
>>> (215) 299-5630
>>>
>>> This e-mail message is for the sole use of the intended recipient(s) and
>>> may contain confidential and/or privileged information. Any unauthorized
>>> review, use, disclosure or distribution is prohibited. If you are not
>>> the
>>> intended recipient, please contact the sender by reply e-mail and
>>> destroy
>>> all copies of the original message.
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>