Retire Article Comment (reason)

[amarks]

Good afternoon, folks,

We have a group that would like to have a reason added to any article that is being retired.  We currently use instant retire, and so we aren't looking for a retirement workflow. The problem the team wants to solve for is the event when an article is retired that potentially should not have been.

Currently, if an article is flagged for review, then our knowledge experts can add a comment when completing the feedback task. Our challenge is when the author retires the article.

Has anyone faced this challenge? If so, what can you recommend?

Thanks,

Adam

[Dr Atul G- LNG]

Hi @amarks 

According to me, it is process issue, if you set up the process that reason is required then we can change in platform.

[Pierce Preston]

We had the internal ServiceNw team add a mandatory text box that was presented when a user clicked Retire. This was for this very reason. They would need to give a reason for submitting the article as retired before it could proceed.

We don't use instant retire, but I can't see why it wouldn't work in your case.

[mbernste]

Our DevOps team configured the retire button so that when it is clicked, you get a form with a single required field asking for the reason for retirement.  The reason is then placed in the activity stream.  I do understand that not everyone has a DevOps team, but it is certainly doable.

[Dr Atul G- LNG]

SO in this case, you need to modify the OOTB retier UI action and add condition for reason.