When a consultant works with a client and creates custom SQL code, this is the procedure to follow

1) Custom code should only be modified/tested in the DEMO or TEST environments. If you need something loaded into the clients DEMO or TEST and do not have the access via a client - add the code to the case and request HOSTING to load.
If you have no choice but to work in the production environment - follow the remaining steps anyway to make sure we are tracking the code correctly.
 

2) Any code created should be uploaded onto (XXXXX being the customer code)

yyz-fileserver\Customers\XXXXX\Support\Custom\5.05 Functions

If the folder does not exist - create it (or reach out support if you do not have privileges).

3) Once the client has signed off on the code - create a case/Jira with the reference to your code on FILESERVER requesting QA to release it. QA will create a load file including a reference to VMDC and place the code on the release wiki - No email is required to be sent to the client - No testing is required by QA. The case can be closed once this step is completed.

4) Open a separate case for HOSTING to load into PROD (once released). This can be done in advance if needed - but we want this as a separate item for tracking. Hosting will take the code from the release and load it into PROD.