How to redirect users from Outdated Version to Latest Version of article in the portal?

[Aicel]

We are using versioning of knowledge articles in ServiceNow. However, it is inevitable that some users copy the link from the address bar instead of getting the permalink from the Copy permalink button. Hence, even when an article is already updated, some users still go to the old version of the article as they are using the Direct URL or they bookmarked it in their browser. 
We are thinking of 2 options. Can someone help us how to set this up in the portal?

1. Option 1: When users go to an old version of an article in the portal, they will see a message at the top of the article: "This is an outdated version. Go to latest version of the article here." And it should have the link to the latest version. 
2. Option 2:  When users go to an old version of an article in the portal, they will not see the article but instead see an error message or a customized error message like this:  "The URL of the article you used is either retired or not available. Try searching for the title or KB# of the article in the Search bar."

[Ulka1]

Hi Michael, 

We have a similar requirement that when user try to use outdated KB article link, if user bookmark a article link and later on that article's latest version available in system then the user should navigate to latest version of the KB article after clicking the bookmarked KBA link.

I tried the above solution which you suggested but when I open the our ServiceNow instance option I am unable to see the other options where the  "Redirect to the latest article" checkbox is showing here.

For the reference screenshot file is attached here.

Please can you assist or give guideline me to achieve this requirement.

[Jason Sturgeon]

There is a tip that states these two options cannot be used at the same time though.

 

[Elizabeth32]

We have this enabled and it has been great since many don't copy the permalink. However, if the latest version of the article is in draft state, non-itil users don't have access to that version. They receive the record not found error message. Has anyone run into this? Do you let non-itil users see draft articles?

[Mike Van Vooren]

Elizabeth, we had the same issue.  Our developer had to switch things around behind the scenes to force the system to recognize that the latest "Published" version was the "latest" version, not the "Draft".  This did not fix the visibility of those Drafts to non-ITIL users, but it did minimize the risk of someone stumbling on them.  I can get more specific details if that would be helpful.

In addition, we did submit an enhancement request on the Idea board which is currently "In Consideration": Knowledge Article Visibility on Service Portal for End Users.  Please feel free to up vote it :).  The general idea was to hide Outdated versions too, but someone else suggested that those would still be useful in HR scenarios.  So hopefully SN can provide flexibility for what's visible and what's not.

[sethhumphrey]

Michael,

Can you please share the code for:

developer had to switch things around behind the scenes to force the system to recognize that the latest "Published" version was the "latest" version, not the "Draft".

This has been plaguing me too and can't figure it out.

Thanks!