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

1. Make sure the certificate template uses the correct naming for referenced files (Certificate Template Resource Structure using File Collections)
2. Get tested and approved certificate template file for release
   • Before releasing any certificate template it needs approval from QA
3. Upload certificate file to server's folder location for certificate templates (can be found in Certificate Template Usage - column Certificate Template Location)
   • 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'
4. Update any changes of the certificate template like KB/KB compressed size in spread sheet Certificate Template Usage
   • Use disk size of the certificate template file. No need to render the certificate with actual data to get the file size. Use regular zip (i.e. 7zip) to get the compressed size
5. Upload the certificate template file to Google Drive (https://drive.google.com/drive/folders/1om3B6t1CXeSzVfJzRWW-MKRLfo00G0rv). Download the latest version of \[Date\] - Carnival Certificate Templates.zip and add/update the certificate template. Re-upload a new version of the zip file \[Date\] - Carnival Certificate Templates.zip. Note: This is a temporary location. Certificate templates (which don't contain PII like signature image) will be moved Git as part of Core
   
   • It is important to keep the Google Drive location in sync with what is released to the customers
6. 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.