Listen for article lifecycle events in Knowledge Authoring
As your authors work on knowledge articles you can fire code to do things like trigger an AI Agent or write data into another system/object. Almost any manual action an author completes on a knowledge article in authoring will now fire an event that gives you access to information about the article that is being created/updated/deleted/approved/published/etc.
This allows you to tie your knowledge authoring process into other tools and processes more deeply than ever before. For example, if you have ever wanted to connect knowledge articles to custom objects you need the unique identifier of an article, which is only available after the article is saved the first time. Now you can listen for the CREATE action in a VB extension and write whatever data you want, including that ID, out to your custom object. Similarly, you could use these events to leverage machine translation to maintain localizations of your articles, this could even be through AI agents.
Steps to Enable and Configure
Leverage the Visual Builder Studio to expose your applications. To learn more about extending your application using Visual Builder, visit Oracle Help Center > your apps service area of interest > Books > Configuration and Extension.
As of 26A, the following pages in Knowledge Authoring now include an event named "kmArticleActionEvent":
| Page | Short description | Potential actions |
|---|---|---|
| create-from-sr | Used when creating an article from an SR or Help Desk request using an Action Plan | CREATE |
| gen-from-sr | Used when generating an article from an SR using generative AI | CREATE |
|
These pages all list knowledge articles and offer the same set of events. list-articles is used most frequently. | DELETE, PUBLISH, UNPUBLISH, WORKFLOW_START |
| manage-article | The page through which most articles are created and updated. | CREATE, UPDATE |
| translate-articles | Page used for manual, side-by-side translation. | UPDATE |
| view-article | UPDATE, PUBLISH, UNPUBLISH, WORKFLOW_START, WORKFLOW_APPROVE, WORKFLOW_REJECT, WORKFLOW_ASSIGN |
Listen to this event to react when authors take any of the actions above. The event contains an action attribute with the values seen in the "Potential actions" column above as well as a complex contentData object. The contentData object's content will vary depending on what sort of action has occurred and should always be enough information to understand what has just occurred to the article.
Tips And Considerations
These events capture when a manual action has been taken on a single article. This means that error states will not trigger these events, nor will mass updates or externally triggered updates (via api). Take this into consideration when determining what you want to do with these events.