This page (revision-2) was last changed on 17-Sep-2020 14:38 by Kevin Higgs

This page was created on 26-Nov-2021 10:22 by Kevin Higgs

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
2 17-Sep-2020 14:38 1 KB Kevin Higgs to previous
1 26-Nov-2021 10:22 1 KB Kevin Higgs to last

Page References

Incoming links Outgoing links
SOP.CUSTOM_CODE...nobody
SOP.CUSTOM_CODE

Version management

Difference between version and

At line 1 added 2 lines
When a consultant works with a client and creates custom SQL code, this is the procedure to follow
At line 2 changed one line
\\ 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 to me 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. \\
\\ 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. \\
This page (revision-2) was last changed on 17-Sep-2020 14:38 by Kevin HiggsTop