Home > Forum > Actions > Standard-Mail vs Custom Mail - Taskdetails in mail

Standard-Mail vs Custom Mail - Taskdetails in mail
0

I have a workflow with these steps:
* Start => *Approval

Task name: "upon approval"
Task details: "check and approve the order"

If I use "Standard Mail" in Task-Creation via Task-Configuration I get these info in the mail:
"Approval - upon approval"
"check and approve the order"
=> all correct

If i use "Create Custom Mail" in the action on path i get:
"Start - upon approval"
"check and approve the order"

So the stepname is not correct evaluated ... or am I missing something here? Should be also "Approval" instead of "Start"

Of course I could place the custom-mail to "on entry" of "Approval" ... or create a template an hide "task details" and write custom text....
but that seems to be dirty workarounds.

Any thoughts or ideas?

Thanks
Ernst

MVP

Hi Macchina,
I'm assuming that the difference is strictly connected with order of execution* in Webcon. As you can see on linked image** tasks are created in the On Entry part of the schema, and with those tasks e-mails are sent, so its basically On Entry.

In your case i'd move that action to On Entry, as this would reflect the behavior of sending e-mail via task creation.
Transition to new step happens after On Path automation, this is the direct cause of different behavior you are experiencing.

* in this article you can read more about it: https://community.webcon.com/posts/post/pending-in-transaction-vs-pending-after-transaction/347/3
** especially this image describes very well what happens internally https://community.webcon.com/community/public/uploads/editor/1.5.png

Privacy overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognizing you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.


To see a full list of the cookies we use and learn more about their purposes, visit our Privacy Policy.