exclude groups from Department Change Notifications

[LJ_23]

I have a list of 125 groups i need to exclude from receiving trigger notifications.

I have located the workflow in question that is contributing to firing the event 

These are the conditions i have added,

so under the 125 groups the parent is this^ but i am struggling with the next steps as when i test the flow it stops at action 1 and doesnt run the flow, aslo how do i know all said groups are excluded from the notification

[Hemanth M]

Hi @LJ_23 ,

Could you clarify why there is an additional 'AND' condition after 'Parent is not XYZ group'? The logic should look at all groups except those 125. Additionally,

do you see any errors any errors in your flow/action context when testing action 1?, can you check action steps logs?

[Abhishek_W]

Hi @LJ_23 ,

The problem I see is:
1) The “Look Up Records” action returns zero groups because the AND conditions (Active, Type contains, Parent is not) plus the OR block of Department.Parent pills must all match, and the trigger pills (Trigger - R… Department R…) are likely resolving empty in your test, so the flow stops at action 1.
2) The lookup also finds groups rather than excluding them, so even when it works, it doesn’t stop notifications for your 125 groups.

What you can do:

1. Mark the 125 groups with a flag field (e.g. u_exclude_notifications = true) or a dedicated Group Type, then add is false / is not as the exclusion condition in the flow or the Notification’s conditions.
2. Verify by filtering sys_user_group with the same condition (count should be 125), then trigger one excluded and one normal group and check sys_email for who received mail.
3. If the flow only fires an event, put the exclusion on the Notification itself (“Who will receive”/Conditions) so it applies regardless of the flow path.

If you find this helpfull, Accept  ✔️ the solution and mark helpful 👍.

Regards,

Abhishek

[LJ_23]

I cannot add the condition "parent is not operational resilience" to the notification because its using the department table not the sys_user_group

not sure what you mean by adding a flag field ? this may have a knock on effect on the groups receiving other notifications.

Is there an alternative way to exclude the said groups in the flow logic without adding a flag field? Is there a way to just update the flow instead of amending the notification, or vice versa?

Initially the flow has ran previously with the same conditions so curious why sometimes it runs and sometimes it stops.