After migrating to KB version 3, knowledge_admin can only retire articles created in version 2. - Support and Troubleshooting

After migrating to KB version 3, knowledge_admin can only retire articles created in version 2. Issue  After migrating from KB version 2 to KB version 3, Knowledge admin cannot update the workflow state of published articles other than to retire the article. Cause Expected behavior for Knowledge v3.

Resolution The behavior mentioned is expected behavior for knowledge v3, this has changed since version 2. Please see the client script Enable or disable form fields seen here:

/nav_to.do?uri=sys_script_client.do?sys_id=2d2d5013ff4131003f07ffffffffff92

This is an out-of-the-box client script that checks to see if the knowledge base is v2 or V3. If v3, this sets the workflow field to read-only. This is for all users, it does not matter the roles. In version 2, knowledge admin did have this ability, but out-of-the-box behavior for v3 is that no user should adjust the workflow state. This is likely due to the new workflows used with knowledge v3. Once a knowledge article is published, it will not go back to Review or Draft state, only forward to Retired or Pending Retirement. Pending retirement is part of the Approval Retire workflow.

If it fits your business requirements, you can adjust this client script to allow admins to have access to this field. However, as workflows are involved with the knowledge process, test thoroughly the effect this will have on articles when changing the state manually, in development.