Idea ID 1625906
Briefly describe your idea
Currently the notification template for task (and approval) is shared (e.g., Change and Request share the same notification template)
Why is this important, when it would it be used
When fields are not available in both entity types DSL syntax is needed to not display these fields if they don't exist. This can make the template full of lines of DSL to choose those fields that are relevant to either the Task or approval.
If you were designing the solution, how would you do it?
Separate email templates would make it easier to maintain them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.