- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2022 09:08 AM
We are implementing a functionality to set the kb state as "Retired" for the articles which "valid to" date is passed.
we faced an issue that after setting the retired state to valid to passed article, the related version also getting retired.
this should not happen. Thanks in advance
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2022 09:30 AM
Hi @Roxi1
So Knowledge Article Retirement flow happens from Workflow "Knowledge - Retire Knowledge".
In this flow it calls Script Include 'KBWorkflowSNC' and function retireKnowledge(). As this is SNC protected so you cannot update it. But you can understand this and accordingly create your custom Script Include and use it.
Also, If your related Versions of KB Articles are also having same date as 'Valid to' it will run for same. You can verify by checking 'Show Workflow' related list to check if separate workflow is tagged to separate versions.
Thanks
Anubhav Ritolia
ServiceNow Rising Star 2023
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2022 09:30 AM
Hi @Roxi1
So Knowledge Article Retirement flow happens from Workflow "Knowledge - Retire Knowledge".
In this flow it calls Script Include 'KBWorkflowSNC' and function retireKnowledge(). As this is SNC protected so you cannot update it. But you can understand this and accordingly create your custom Script Include and use it.
Also, If your related Versions of KB Articles are also having same date as 'Valid to' it will run for same. You can verify by checking 'Show Workflow' related list to check if separate workflow is tagged to separate versions.
Thanks
Anubhav Ritolia
ServiceNow Rising Star 2023