Best practices around preventing skipped records

Stefan Coetzer
Tera Contributor

We are a new-ish customer using ServiceNow, haven't worked on the platform before and mainly use it for the GRC module at the moment.

 

We want to stay as OOTB as possible to prevent skipped records, what would be the best way to make updates to default values? 

For example, Number of days to respond (when creating a new policy) is set to 14 by default, if we want to increase/decrease this should we edit the dictionary item default value/create a UI action/Client script? 

 

I would really appreciate any feedback on how you manage these changes and if possible links to any courses we can do to get a better understanding of the platform and how to manage changes.

I've completed the CSA learning path earlier this year but with no prior experience in the platform and very few use cases I'm not very confident about doing things by myself.

 

Thanks in advance!

1 ACCEPTED SOLUTION

@Stefan Coetzer 

yes that's your customization as per customer requirement

Customizations are not altered during upgrade.

The only thing to keep in mind is if you are updating any OOTB dictionary or any other script etc then you need to review the skipped records

There could be a possibility that ServiceNow gave additional features for that dictionary or script and now you have to decide if you want that or keep your custom one or merge

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

View solution in original post

5 REPLIES 5

@Stefan Coetzer 

correct

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader