Skip to main content

Wondering how people are managing template changes & organization. 

Our templates are used via an integration, and so it can be challenging to make updates because projects may be created while trying to make edits and updates.

I’ve started making copies of the existing template, updating it and then swapping it out. However now I have a number of templates that  dont need anymore. Theres no archive and I worry about messing with reporting if I delete the templates. 

​@EHill Our approach is similar to your organizations. Our integrations point to template SKUs, which allows us to duplicate templates and make changes freely until we’re ready to connect them to the integration. Then we update the SKUs when we’re ready to use the new version (connected to the integration)

This doesn’t address cleaning up older template versions and we have a significant accumulation of old/un-published templates as well. We started putting “1.” in front of our published templates so that they rise to the top of the list. I hope this helps a little!

Ive tried the duplicate and replace but was worried about creating that backlog like you are currently working with 

I have thought about adding V1,V2. V3, etc

Reply


Terms & ConditionsCookie settings