Hi Chad,
Apologies for the late response. I wasn't subscribed to this forum and didn't see your topic at first.
We have integrated EdgeFrontier with various notification systems (i.e. SMS Aggregators) in the past. Each project/scenario implemented different business rules and different workflows that met the needs of the agency/client. Additionally, the APIs were different in (1) connection method and (2) commands/functionality exposed via the API.
When building EF Systems, here is the approach I take...
-
What is the connection method? Web services, TCP/IP, HTTP, etc.
-
What is the format of the data and is there a document that describes the fields included in the data? XML, ASCII; A table that maps out all the potential fields/values in the message, the datatype, required/not required, etc.
If you can validate these 2 items, then the next thing to do is determine your business rules (which will result in deriving knowledge) and then determine your workflows that will respond to your business rules.
Can you provide a description of the business rules that you are looking to configure?
While EF has been used to integrate to many notification systems, the true value of EF is to be able to quicly build a new integration/interface by supporting flexible connectivity, interpretation, business rules, and workflows to overcome any 3rd party API shortcomings and to tailor the workflow to solve your specific agency's needs.
So any additional information on the business rules / workflows would help to guide you on how to configure this interface in EF. Typically, from personal experience, interfaces to notification systems usually very doable and configurable in EF (they make for a very good use-case).
Let me know your thoughts and if you have any additional questions.
Thanks,
-Jack
