Knowledge articles stuck in Pending Retirement. How do I move to retire?

glj0892
Tera Expert

I have several knowledge articles that are all in the state "Pending retirement".

 

I believe they're all on the approval retire workflow, but they're not moving to retire and I cannot seem to force them to retire without running a script. Some have been in this state for months, others a few weeks. 

 

How do I force these articles in to retirement, so I can republish them with a new Valid to date?

1 ACCEPTED SOLUTION

glj0892
Tera Expert

There was a customised script that was searching for pending_retirement articles, but not pushing them to retirement. There is no UIAction on an out-of-the-box instance to move your articles to retirement. 

View solution in original post

10 REPLIES 10

How is this accomplished? This would make it easier for the clean up I am trying to conduct.

On the Knowledge Base level just set the Retire Workflow to Instant Retire.
Knowledge Retire Workflow.jpg
Go to Knowledge - Knowledge Bases.

Open the required Knowledge Base.

Select Knowledg-Instant Retire from the Retire Workflow drop-down
Save.


Now anybody with Contribute Access to the Knowledge Base is able to instantly Retire articles (same for if you use the Publish Workflow to Instantly Publish articles).

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



This is great - thank you @Eoghan Sinnott

 

With this I guess I cannot set it so only a select few folks can instant retire?

Do you know if there are any issues changes the workflow back and forth? For example if I set to instant retire for a short time then back to the original workflow in a week?

 

Also a side note - do you use a program to blur your images? I think this would be helpful for creating help documentation for my organization.

You are welcome! We have the approval retire workflow set that we have an approval group, so the members of that group are the ones that approve anything that has been put forward for retirement. But we also have it that anybody that's a member of that group bypasses the approval process and is able to instantly retire, basically so that they don't have to approve their own requests. I think it was a pretty simple logic change to the workflow to do this. 

Also there shouldn't be any issue with moving between the different workflows.

 

I use SnagIT for blurring the images. It's just a tool to take screenshots/screen captures and has a few basic built in editing functions like highlighting, blurring and cropping. Yes we find it very useful for blurring out any sensitive info that we don't want to show in articles. 

glj0892
Tera Expert

There was a customised script that was searching for pending_retirement articles, but not pushing them to retirement. There is no UIAction on an out-of-the-box instance to move your articles to retirement.