eWire Email Notification Process

  1. WebEwire is created by customer on web 

    1. -> email to customer marked as a Pending request

    2. Webewire is sync’d to HO

  2. WebEwire is “approved” by customer service rep - HO

    1. -> No email is sent

  3. WebEwire is “denied” by customer service rep - HO

    1. -> email to customer indicating denial

  4. WebEwire is converted/invoiced by customer service - HO

    1. → email to customer with eWireID and security code

    2. NOTE: this happens at the server where the invoice is created (ie. HO) so we need to make sure this location is configured to send emails and has the email templates necessary (/CXR/Resources/ folder)

  5. eWire is sync’d to eWire server and sync server

  6. eWire is fetched and invoiced by remote site.

    1. eWire is synced back to the eWire server

    2. eWire is synced back to the NZ sync server

    3. Calendar event runs and identifies the eWires as “settled” and generates an email to the customer noting the completion of the transaction

NOTE: currently calendar events run every few hours. We can work on making this more frequent.