Knowledge notification are not getting triggered - when workflow state = outdated.

[Snehal Madakatt]

I want to trigger notification for knowledge article states:

1. KB article when created --state: draft

2. KB article will be retired --state: pending retirement

3. KB article is retired --state: retired

4. KB article is outdated --state: outdated

I have configured as below. But notifications are not getting triggered.

Kindly help.

[Gunjan Kiratkar]

Hi @Snehal Madakatt ,

Please open any one notification and share the snapshot of when to send and what it will contain tab.

Ensure that the content of "what it will contain" is error-free. Notifications might not be triggered if errors are present. It's worth confirming that other notifications are functioning correctly. 

[Snehal Madakatt]

I tried by eventqueue, that too is not working. All i need is to send the notifications on KB when workflow_state is in state draft, pending retirement, retired, outdated.

As of now i have configured but its not working.

[Gunjan Kiratkar]

Hi @Snehal Madakatt ,

Validate few things as below :

1) Are the states properly changing to outdated for article?

2) Are you validating weather notification is send or not from "sys_email" table without any filter?

3) Check if any similar notification is there with same conditions on same table then try to increase weight of your notification.

4) Share the snapshot of who will receive tab.

I tried on my PDI for retired and it works as expected as below :-

Notification :

Logs :-

[Snehal Madakatt]

@Gunjan Kiratkar , can u please try for outdated and let me know if its working?

Are u able to get notifications for above states? especially for outdated state, its not getting triggered. 

1) Are the states properly changing to outdated for article?==>yes

2) Are you validating weather notification is send or not from "sys_email" table without any filter?==>yes

3) Check if any similar notification is there with same conditions on same table then try to increase weight of your notification.==>no, there are no such

4) Share the snapshot of who will receive tab.--snap given above