Oob files ,custom files,customised oob files

[kiran kumar m1]

does anyone have useful links or information about?

1.Oob files(out of the box)

2.Customised oob files

3.Custom Files

[scott barnard1 · Accepted solution]

Hi Kiran

1. out of the box - these are records supplied by serviceNow that have not been altered by local developer and will be upgraded on the next upgrade if there is an appropriate update.

2. Customised ootb  - These are files that were once supplied by ServiceNow but have been modified and so will not be available for update at your next upgrade and so must be maintained locally. Often referred to as Tech debt. Over time these can get so many that the instance upgrade will skip more files that it upgrades.

3. Custom files. Nothing to do with ServiceNow. Will never be upgraded except by local action.

Historically SN  advised you to mark ootb file inactive then create your own if you wanted a custom behaviour but they seem to change their minds every couple of years.

Key take away. Your org is responsible for any customisations that it performs. They need to be maintained, tested for and potentially updated when the platform moves on and the functions that underpin them change or are deprecated. This burden can become significant and is rarely planned for as most orgs are focussed on new feature release and not maintaining legacy code.

Just an opinion

regards

Regards

[scott barnard1 · Accepted solution]

Hi Kiran

1. out of the box - these are records supplied by serviceNow that have not been altered by local developer and will be upgraded on the next upgrade if there is an appropriate update.

2. Customised ootb  - These are files that were once supplied by ServiceNow but have been modified and so will not be available for update at your next upgrade and so must be maintained locally. Often referred to as Tech debt. Over time these can get so many that the instance upgrade will skip more files that it upgrades.

3. Custom files. Nothing to do with ServiceNow. Will never be upgraded except by local action.

Historically SN  advised you to mark ootb file inactive then create your own if you wanted a custom behaviour but they seem to change their minds every couple of years.

Key take away. Your org is responsible for any customisations that it performs. They need to be maintained, tested for and potentially updated when the platform moves on and the functions that underpin them change or are deprecated. This burden can become significant and is rarely planned for as most orgs are focussed on new feature release and not maintaining legacy code.

Just an opinion

regards

Regards

[Dipen Wadhwana · Accepted solution]

Hi @kiran kumar m1 ,

Here are some definitions to get started:

1. OOB files refer to the Out of Box files that come with ServiceNow. These files are pre-built and are not customized by the user 1.

2. Custom files are files that have been created by the user to meet their specific business requiremen...1.

3. OOB customized files are Out of Box files that have been modified by the user to meet their specific...2.

Here are some useful links that can help you learn more about these topics:

1. How to revert the customized file to base version or OOB version
2. Revert customised record to OOB and transfer via Update-set for Upgradeability
3. Business Services Using OOB CMDB Tables

I hope this helps!

Please mark it helpful if it helped you.

Thanks,

Dipen