- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2024 08:16 PM
Context: Knowledge Articles Created with Templates cannot trigger custom flow that triggers on records created in kb_knowledge table. When articles are created using templates other than the standard one, they are stored in different tables. As a result, if you use a custom flow in Flow Designer that triggers on records created in the kb_knowledge table, it won't work for articles created through these templates.
Question: How can you still trigger the flow without creating separate flows for each table, especially since we have many templates?
This won't work for me.
Reference: support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0823204
Solved! Go to Solution.
- Labels:
-
Flow Designer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-03-2024 06:56 PM
Found the fix:
This is only for flow designer. Change your flow to 'Run on current and extended tables'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2024 11:41 PM
Why doesn't the support article work for you? It triggers the flow from the child table.
You could of course duplicate the flow, but triggering it through a BR sounds like the best option, just not clear why the solution doesn't work, since your question is almost literally what the support article says.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2024 11:55 PM
Hi, I'm using Flow from flow designer and not the legacy workflows. So the table is in sys_hub_flow.
Business Rule Table: kb_knowledge
Advance Script:
This does not trigger the business rule. I have the same condition for my flow and business rule. That's when kb article record from kb_knowledge table went 'published' or 'retired'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-03-2024 06:56 PM
Found the fix:
This is only for flow designer. Change your flow to 'Run on current and extended tables'