#26 variable for template use for what 'service is called'

[Anonymous]

The functional application owners here are amending our local branch of filelocker to 'rename the service' something else (Filelocker -> $edu-name Secure File Transfer). A lot of this whack-a-mole by our edu's part could be resolved if the 'filelocker' nomenclature throughout the templates were populated with a variable like other varaibles throughout (think $fl.serviceName or something).