Knowledge Articles from HR Knowledge Base are being set to retired without clicking Retire UI Action
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2025 05:20 AM
Hi Team,
There is a weird scenario which i came across recently.
Knowledge Articles from HR Knowledge Base are instantly getting retired without clicking on Retire UI Action when any change is made on knowledge article when it's in published state.
Scenario 1: When i tried to extend the validity of a knowledge article using custom UI Action, the validity got extended but the workflow state was
set to retired without triggering any approval.
Scenario 2: When i tried to update the knowledge article author from list view using list context menu, the author got updated but workflow state was set to retired without triggering any approval.
What could be the possible reasons for such behaviour. Could someone please suggest.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2025 05:42 AM
Hi @Vdevmat33
Try repair the plugin once. Hr core and knowledge management.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2025 06:10 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2025 05:54 AM
What is the 'valid to' date on the articles? I am wondering if the 'valid to' is being set to a date in the past, like the first day of 2025.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2025 06:09 AM
In most of the cases valid to is in future like below.
Old Valid to - 10 Feb 2025
After clicking custom UI Action which extends the valid to by a year
New Valid to - 09 Feb 2026