Hi @ShariqhM
The trigger logic is essentially the condition that causes the notification to be sent.
In your screenshot, the notification is configured to send when the event knowledge.approval.rejected is fired. Therefore, the trigger logic is not defined directly in the notification itself. The notification is simply listening for that event.
To identify the actual trigger logic, you need to find where the event knowledge.approval.rejected is being queued. You can do this by searching for the event name in:
- Business Rules
- Flow Designer flows/actions
- Workflows
- Script Includes
- Any scripts using gs.eventQueue('knowledge.approval.rejected', ...)
The business logic that fires this event is the actual trigger logic behind the notification.
For example, the trigger logic might be:
- "When a Knowledge Article approval is rejected, queue the event knowledge.approval.rejected, which then triggers this notification."
So, in short:
- Notification Trigger = Event knowledge.approval.rejected
- Actual Trigger Logic = The Business Rule, Flow, Workflow, or Script that fires the event
You can navigate to System Policy > Events > Event Registry, open the knowledge.approval.rejected event, and then search the instance for references to that event name to find the exact logic behind it.
Hope this clarifies the difference between the notification trigger and the underlying business logic.
Thank You!
Juhi Poddar
Thank You!
Juhi Poddar
