Create Account Task Completion email is sent to beneficiary as well as task owner

[Sairam_k]

Hi,

Getting Create Account Task Completion email for User, endpoint owner and task owner.

The requirement states that only the beneficiary user should receive the Task Completion Email. And mentioned ${user.email} in Create Account Task Completion Email template to receive email for user(Beneficiary).

[pmahalle]

@Sairam_k ,

What's the issue here? After you added ${user.email} beneficiary user not getting email after task completion?

[rushikeshvartak]

Please validate supported variables.

Purpose :

To get what variables are present to use in the email template.

Email Template steps :

keep Advanced HTML CSS flag is checked

Keep your email Address in TO

TO /CC/BCC & Subject - Don't use any dynamic variables

Add only below code in Email Body
${this.binding.variables.each {k,v -> println "$k = $v" + "" + "br" + ">"}}

Output : using the below expression. By putting it in the email body, it will print all variable names with values, and then accordingly, you can use it:

[Sairam_k]

Our requirement is sending account name and password to beneficiary user after account gets created. Issue we are facing is that - the email is triggered multiple times to beneficiary and task owners.

I tried creating test email template and printed all binding variables. But same result. I got multiple emails - one having binding user set to beneficiary and others having binding variable user set to task owners.

[rushikeshvartak]

• Where is email template attached ?
• What is type of workflow used ?

[Sairam_k]

Email template is attached at endpoint level - for new account - on task completion.

Doesn't look like workflow issue. We have 2 level approval workflow in production but for ease of creating tasks, we are using auto approval workflow for creating pending tasks quickly.

At endpoint level we have set some owner which becomes task owner when task gets created. Sometimes owner is user group. And they are receiving this mail as well. e.g. account is being requested for abc and xyz is task owner, we are receiving 2 emails. In beneficiary email, all ${user.<>} are resolved to beneficiary abc and in another email all ${user.<>} are resolved to owner xyz. 

Account name remains same.

[rushikeshvartak]

Please validate supported variables.

Purpose :

To get what variables are present to use in the email template.

Email Template steps :

keep Advanced HTML CSS flag is checked

Keep your email Address in TO

TO /CC/BCC & Subject - Don't use any dynamic variables

Add only below code in Email Body
${this.binding.variables.each {k,v -> println "$k = $v" + "" + "br" + ">"}}

Output : using the below expression. By putting it in the email body, it will print all variable names with values, and then accordingly, you can use it:

[NM]

Hi @Sairam_k , on endpoint level have you set new account with beneficiary?

Try to set "new account"