Outlook integration

[Mark_Wonsil]

@MikeGross

What we need is Epicor to write the REST/API Exchange Connector extension

Ahem…

Create a Notification Service outside of the Epicor Core

Notification Service: Move the responsibility of sending “notifications” (email, etc.) out of core of Epicor and crate a service that works across all Epicor products so sending an email from a BPM works the same as from DocStar. Use the single responsibility principle to throw the notification package to the service. Now, all notification work is done in a single place. This makes adding capabilities so much easier. The service could also be able to check for confirmation, email bounce-backs, e…

Poorly named request but that’s exactly what I’m proposing here. However, I’m not limiting it to email. For a group that works with manufacturing people, we IT people sure like push systems!

I’m suggesting more of an Actor Pattern where our customizations/BPMs/Functions just send the information to a queue. The notification system would then do what was needed: email, text, message, fax, Teams/Slack or whatever you dream up. The user would be in charge of how and when they would like to be notified.

The reason I said “outside of Epicor” and by that I mean E10, is then the product would work for Prophet 21, and the other Epicor products fulfilling the “Chicklet” vision we’ve seen at Insights.