Recently, we encountered some problems related to email rendering in production. Sometimes, our changes are small, but since currently there is no proper testing procedure, and all we often do is just copy-paste-ing template and saving it, we sometimes are not realize that our small changes might lead to some issues in production. Resolving template issues is also a bit cumbersome, because we don't have proper version control, so we don't know who made the last changes, or what changes that were applied before the last working version.
As an attempt to address above issues, we proposed a new procedure every time we need to update payment template. Now, all payment user communication templates will be saved inside a repository, and any changes should be reviewed first before updated in TAP.
Payment User Communication Template Repository
https://phabricator.noc.tvlk.cloud/source/puct/repository/master/
Docs
https://29022131.atlassian.net/wiki/spaces/PAYMENT/pages/205638033/Updating+Payment+User+Communication+Template
We acknowledge that this new procedure is still in trial, and might look like a bit too complicated. We are open to more feedback and discussions, while waiting until someday we have proper version control in our template management page.
Thank you so much for your attention.
:bow:Warm regards,
Payment Web Engineers