flow designer workflow for knowledgebase unable to publish
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6 hours ago
Hello,
We have Zurich.
Many of our knowledgebases use the older workflow editor workflow.
We designed a new flow designer workflow and attached it to the knowledgebase.
The Flow Designer workflow is simple publish approval one.
Now when we create the article, select publish button the article does not move forward to review.
Is there something we are missing when we need to move to the flow design workflow to the knowledgebase?
Thanks
Juliet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6 hours ago
Try this
To narrow it down quickly, after clicking Publish, check the flow_context or Flow Executions to see if the flow even triggered. If it didn't trigger at all, the issue is in the trigger/binding. If it triggered but stalled, the issue is in the flow logic itself.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6 hours ago
Hi @JulietChicago ,
A quick checks:
In Flow Designer, is your flow triggered on kb_knowledge record update (e.g., workflow_state change)?
When you click Publish, does the workflow_state actually change?
Can you confirm the Knowledge Base in ServiceNow is configured to use Flow Designer instead of a legacy workflow?
Regards,
Ankit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5 hours ago
To effectively use a Flow Designer workflow in ServiceNow Knowledge Management, make sure the flow is published, the Knowledge Base is configured to use the Flow (instead of Workflow) , and that the article transitions to the Review state.
Typical issues include not activating the flow or failing to include the Publish Knowledge subflow, which is necessary for managing state transitions.
Refer:
How to convert Knowledge base reference field to flow instead of workflow
