Workflow to Release Certificate Template Files

The general workflow to release a certificate template file can be found below. Any change to a certificate template must be also updated in Core Git repository folder CustomerAssets.
Consider /wiki/spaces/CMD/pages/5432385144 creating/updating any certificate template.

Steps to Update/Add a Certificate Template File

Make sure the certificate template uses the correct naming for referenced files (Certificate Template Resource Structure using File Collections)
Get tested and approved certificate template file for release
- Before releasing any certificate template it needs approval from QA
Upload certificate file to server's folder location for certificate templates
- Always copy&paste any existing certificate template file. Never rename an existing certificate template file which is still in use. By renaming a certificate template file the LMS wouldn't be able to award the certificate (missing file) during the time period of renaming and re-adding the updated version of the certificate template file
- Keep the certificate template folder on the server clean - move any not used certificate template file (incl. backups) into sub folder 'Not in Use'
Add/update template files in Git Core repository in folder CustomerAssets.
- If a template is being removed from a live server the Git repository must be updated accordingly so we don't accumulate old/not used templates.

Notes:

Old document used to catalog all released certificate templates: Certificate Template Usage. This is not required anymore because Core Git repository folder CustomerAssets is used to keep track of currently released templates.
Old Google drive location to keep track of certificate template files: https://drive.google.com/drive/folders/1om3B6t1CXeSzVfJzRWW-MKRLfo00G0rv