How do you document your customizations?

Aka Guglielmo
ServiceNow Employee
ServiceNow Employee

I'm wondering how do you keep track of all the customizations and configurations you make on a instance.

Please share:

- ideas

- tips

- best practices

- tools

Thank you!

3 REPLIES 3

sergiu_panaite
ServiceNow Employee
ServiceNow Employee

zica
Giga Guru

HI William,



There are a lot of tools to keep track of all customization you are making in your instance, you can find them by calling our friend Google. But personally I am using Excel spreadsheet.


On of the reason to use Excel is because we are not allowed to download application in our company (security policy), and it is quite simple for use. We are two developers so we created two sheets for each and we share it.



How do we keep track of our custo ?


Well, in my Excel file I have couple of columns and I write down everything I am doing into servicenow.


Here is an example : couple days ago, I have been tasked to make the worknotes mandatory when assignment group changes.



In my spreadsheet


I've got this following colomns :


reference (it is an auto number), Raised by, Description of the task, Request or Incident Ref (reference of RITM/INC/TASK within servicenow), Priority, Status (closed, pending, open, waiting info ...), impact (issue), solutions, Where into snow modifications have been made (details of module and script), promoted to UAT ?, promoted to PROD ? testers feedbacks., update set name,



Here is a screenshot


find_real_file.png



you can also put kind of code color in order to highlight critical task (important >> red color), and also when a task is promoted to prod for example (green color)



Hoepfully that will give you an idea to tackle to snow improvements



Kind regards,


ZA



Do not feel shy to mark correct or helpful answer if it helps or is correct


Goran WitchDoc
ServiceNow Employee
ServiceNow Employee

Through our Change records and good code documentation. Documentation sucks and I try to keep it as simple as possible and try to avoid having to document the same thing more than once.