Investigate: can 'bounce messages' be replaced by triggers with notifications?

[jbostoen]

To investigate.

Pro:

• Could allow for a more dynamic notification
  • Any sort of notification (e-mail, webhook, ...)
  • Based on OQL (e.g. language - however, this property is by default stored at the user object, not the contact object)
  • However, certain bounce messages are sent to the caller's e-mail address; while there may not be a "Person" object in iTop. This would require either a new sort of e-mail notification; an adaptation of the original one; a work-around or creation of a person anyway; ... . To check: if a trigger creation is initiated from a mailbox object, can some values be preset? What about the email variables, can they be passed on?
• Would make the mailbox configuration visually more compact.

Con:

• More complex to set up, where it's now easy to simply specify a title + message.

[jbostoen]

If anyone reads this, please let me know if there is any need for non-email notifications which would replace a typical bounce message instead. Feel free to brainstorm about the other parts as well.

Idea instead of configuring bounce messages (subject, title) per policy:

• A new custom trigger is added ("TriggerOnMailPolicy"). Main issue: there may never be a related ticket. Other con: iTop allows to specify a filter OQL on the trigger, but not on the notification.
• To this trigger, one or more notifications could be added. Use case: this would allow a notification to the customer, but perhaps still an internal alert as well.

Aside from making the configuration visually more compact again on the mailbox object, it also allows to trigger multiple and different notifications. The same trigger (perhaps containing the same notification) can be used for different policies, even across different mailboxes.