Template updates for 'Email Assist'

Please have updates made to email templates propagate, and not force people to find every instance of the email template, refresh it, save it, and then move on.

If I want to preserve the original template, and make changes that only impact some playbooks, I will clone the original, update it, and add it to whatever I actually do want changed and leave the rest as it is.

Having a manual refresh option can be useful as an extra layer of ‘make sure it really updated’ protection but it is otherwise not a feature, it’s an unnecessary annoyance.

The only reason this doesn’t have more votes is because a lot of admins probably don’t even REALIZE that when they change an email template it isn’t automatically updated in playbooks. After all, it IS automatically updated in JO programs (you even get a popup to inform you it will be updated and affect the programs!) If we trust automation to handle the change, shouldn’t we trust it to update even when a user will get the chance to see it and change it before sending it out?

I don’t feel like the original reason for not building this makes much sense either. “We have made this choice considering that if a user managing email templates makes some changes in the template, it should not be applied to playbooks unless the user managing playbooks confirms it.” Perhaps this is outdated because I don’t give email template editing permissions to anyone I don’t trust that would make changes we don’t want reflected everywhere.

Certainly how I got here :)

@mindym I agree with the use case and understand that the behavior should be similar to JO. This is certainly on the roadmap. I am unable pin point an exact timeframe yet and will post an update once we have the timeframe. Thank you!

This is also a big request. We recently implemented new email templates and applied to several playbooks. As CSM’s wish to evolve templates and versions we are now having to manually comb through each playbook to refresh the email updates to be applied. It is very easy to overlook some of the playbooks which should have the updates applied. This also resets existing tokens mapped. Sometimes we are simply adding new text to the email template and the tokens would not need remapped, but we must take the extra steps in order to apply email template updates. This is a very time consume task.

Hey @sriram pasupathi any updates on this one?  Thanks! To reiterate what's already been said by everyone in this thread:

Please have updates made to email templates propagate, and not force people to find every instance of the email template, refresh it, save it, and then move on. 

Adding PM for playbooks

@monica  - Currently any change made to email template is not updated on Playbook side which has that email template mapped on its side.

Looking for an update on this issue.  Is this currently on the roadmap?

What’s the status of this idea, 8 years after creation?
 

We have made this choice considering that if a user managing email templates makes some changes in the template, it should not be applied to playbooks unless the user managing playbooks confirms it.

Based on this line above 👆, it would seem logical that there should be a popup that:

• Showed the dependencies for the template being updated
• Gives the admin a checkbox for each dependency (along with an option to “select all”) to allow admins to update all required dependencies with one click