The KB-Pocalypse is upon us!
On January 1, 2020 a lot of people will wake up with a headache. While some will be due to the previous night's activities, others will be due to a disappearing Knowledge Base, and a lack of systematic delegation.
What is KB-pocalypse?
ServiceNow's default date value has always been set to 2020-01-01. While this was a good 'future' date to use, the future is now here! This means that some records won't be viewed as valid once the new year begins.
Some examples are:
- Delegates: Delegate records have a default 'ends' date of 2020-01-01. All delegations with this end date will no longer be active.
- Knowledge Base: If your knowledge articles have a Valid to (valid_to) date of 2020-01-01, then they won't be visible to anybody searching for them through the Service Portal, or searching/browsing the Knowledge homepage.
How can I see if this impacts me?
Running the script below will show you what tables still have this default value, and how many records still have a date of 2020-01-01.
Also available on GitHub.
How can I fix it?
You can fix this by completing the following:
- Change all the affected records as identified above
- Updating the dictionary entry so that future records won't still default to 2020-01-01.
Please note that the above script will do this for you if you change the update flag to true.