With Axon 12, the override for mail processes is gone - however, the suppression of notifications can only be set to fixed true in the designer and applies in a binary fashion.
While this can be sufficient for a lot of cases, I'm a bit in awe that I now have to model logic in the BPMN I don't want to have in there because it leads to a rather messy layout and it doesn't allow for partial suppression.
The issue I am having to solve:
I only want to suppress the mail for one user - namely the creator - for one given task. The task can either be assigned to a role or a user - in this example the user assignment is always the creator thus making the feature sufficient for the user based assignment. ✅
However the role-based assignment can also include the creator user but suppressing the notification here leads to the other users not receiving a notification either which is not the desired result.
Since the task is also skipping the tasklist, the notification is just bloat and I can understand the customer's perspective, I just don't see the big deal in ignoring that mail or filtering it, but you know, der Kunde ist König 😉
Furthermore I am not a big fan of introducing system-wide or application-wide overrides or hooks which then handle process-specific logic. The solution in Axon Ivy 7, 8 and 10 always felt more like a workaround than a clean solution, because it was always working on an application based level.
I saw Lukas' comment and approach, but I have the feeling that this comes with additional technical debt I don't want to have with every update.
But I know I have the tendency to state my reasoning, but not my desired solution: I'd need the suppression to be more nuanced than the current implementation - maybe something like that:
