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

[amarks]

Thanks @Dr Atul G- LNG, is there a better way to do this without moving from OOTB?

We're looking to validate that this is a reasonable if not typical thing people are looking to do. Are there other, better ways of solving this through process or other methodologies?

Thanks,

Adam

[Dr Atul G- LNG]

NO mate, if we want, we need to update OOTB flow only or create the fresh flow for this.

[Mike Van Vooren]

We also have instant retire configured and were facing the same issue.  For us, we did something similar to Pierce, but we created a custom field called "Retirement Reason".  Our platform owner would only approve us using this new custom field if we configured it as a drop-down menu with pre-determined reasons.  We were allowed to include a general one called "Other", which luckily has not been abused in the 5 or 6 months we have been using it. This has been helpful for us in reporting. 

There were some other things we had to consider.  Again, similar to Pierce, we had to configure our "Retire" button to look and see if the "Retirement Reason" field was populated or not.  If it wasn't, a warning message appeared telling the user they have to update that first.  Also in order to minimize complexity, that field is visible all the time in the Editor.  So we have to monitor Published articles to make sure that field is not populated.  So far, it hasn't been much of an issue.  But yes, we had to create a custom field since we didn't have an OOTB option.