The CreatorCon Call for Content is officially open! Get started here.

Does the "Valid to" date always have to update to 12 months in the future?

Keszia
Giga Guru

When an article is updated, the Valid to field automatically updates to 12 months from this date.

 

I would like this to only happen when an article is created, so that the Valid to field is 12 months from when version 1.0 was created. 

 

Sometimes I'll need to edit an article throughout the year but still want to keep the original creation/valid date so I can have stakeholders review the content, after that, I'd want to be able to push the Valid to date out for 12 months from their review.

8 REPLIES 8

I have a follow up question...! Do you know what was changed in the backend that allowed you to do this?

 


@Lauren Methena wrote:

We were able to give me, as knowledge manager, permissions to update the Valid to field from the list view, which was a lot faster, but we had to specifically change something in the backend to make that happen.


 

Hi Keszia, 

 

You need to update the Article Versioning Properties  to allow for minor edits to the valid to field. Take a look at this post for more information.

Please consider marking my reply as Helpful and/or Accept Solution, where applicable. Thanks!

 

harivats
Mega Contributor

No, this is as per ServiceNow and industry standards but the "Valid to" date can be customized according to the need of a project, and content. Some of the functions have a valid to-date set to 12 months extendable up to 15 months and when you check out an article you can choose any date but should not be more than 15 months and some have 2-year fix as those are very valid and different content. 

 

Let me tell you this - you can change the format of the valid to date as well like it is usually set to YYYY-MM-DD but you can customize it to make it more user friendly which means whatever format the user has selected in their profile automatically valid to date will pick that format. 

Thanks - I have the article validity to 365 days at a Knowledge base level. I guess what I was wanting was if I can have something prompt me to ask "do you want to update the valid to date?" so in cases of me fixing a typo or something minor like that, the original valid to date remains for the purposes of annual content reviews.