Knowledge - calculating 'valid to' date

[10382]

Hello,

I am beginning to look at business requirements for Knowledge, and one of the requirements is that the "valid to" date be calculated to 1 year (365 days), based on the "published date".

Is anyone doing something like this?

Are there reasons you wouldn't want to do this?

Does anyone have a java script that is doing this now, and would be willing to share with me?

Thank you!

Julie

[10382]

AH, ok I do have that.

Thank you!

[sryan]

Julie,

You might consider using the Updated instead of the Published date. Is your goal is to ensure that every knowledge article gets reviewed at least once per year? If so, any update to the knowledge article should "reset" the review date to one year later. Using Published date would limit you to one update cycle.

[10382]

Thank you for sharing!   I appreciate your insights!

[Mark Stanger]

Julie,

I understand what's being asked for, but I don't think basing it off of the 'Published' date is what you want.   For example, what if you have a news article that should only be available for 1 week?   Pushing everything out to a year in advance when it's published wouldn't allow for this.

I think what you really need to do is have a publishing and approval workflow to help handle both the initial publishing and the subsequent recertification of the articles.   What we do is set the 'Valid to' date out to 1 year in advance by default.   This happens out-of-box, but the more important part is that you enforce a maximum valid to date so that all articles can be re-certified periodically.   This is where your review and approval cycle needs to come in.

There are actually several pieces (default values, business rules, workflow, and scheduled jobs) that are required to make this work properly.   Feel free to contact me directly if you'd like to discuss more.   Crossfuze has a comprehensive turnkey KB product that addresses this issue along with many more that you'll encounter with knowledge management.   You can take a closer look at our KB turnkey product here.

Crossfuze Turnkey Packages

[ksweeney]

Hi Julie,

To add on to what lind1006 said, we publish articles with the use of a UI Action called 'Publish'.   (We do not use a workflow, but rather use UI actions, business rules etc to handle the articles lifecycle).   The code in 'Publish' UI action reads the value selected in the   'Expiration' field (3 months, 6 months, 1 year etc...) and calculates the 'Valid To' date from the current sysdate, which happens to be the date we published the article.

I have attached the code from our UI action below....hopefully this helps!

-Kari