Difference between revisions of "BEMail onArrival matching engine"
From All n One's bxp software Wixi
Philip Lacey (talk | contribs) |
Philip Lacey (talk | contribs) |
||
| Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
| + | {| class="wikitable" | ||
| + | ! style="width:20%" | Setup | ||
| + | ! style="width:20%" | Content Retrieval | ||
| + | ! style="width:20%" | Content Replacement | ||
| + | ! style="width:20%" | onArrival | ||
| + | ! style="width:20%" | SPAM | ||
| + | |- | ||
| + | || [[BEmail_(_Email-2-Campaign_)|Link]] | ||
| + | || [[BEmail_Content_Retrieval|Link]] | ||
| + | || [[BEmail_Content_Replacement|Link]] | ||
| + | || [[BEMail_onArrival_matching_engine|Link]] | ||
| + | || [[BEmail_SPAM_Management|Link]] | ||
| + | |- | ||
| + | |} | ||
bxp has the ability to retrieve emails from an Inbox and log them straight into a form as a CDA record. [[BEmail_(_Email-2-Campaign_)]] | bxp has the ability to retrieve emails from an Inbox and log them straight into a form as a CDA record. [[BEmail_(_Email-2-Campaign_)]] | ||
Revision as of 15:22, 8 February 2018
Overview
| Setup | Content Retrieval | Content Replacement | onArrival | SPAM |
|---|---|---|---|---|
| Link | Link | Link | Link | Link |
bxp has the ability to retrieve emails from an Inbox and log them straight into a form as a CDA record. BEmail_(_Email-2-Campaign_)
As part of this process it is possible to extend the functionality to perform additional intelligent matching and automatic classification of inbound emails.
There are three flags available to the onArrival matching engine.
- Match contact
- Match owner
- Match company
Using the email address of the sender matches can be made. The first match is to match the email to a contact. In a separate form a complete list of contacts can be held. One of the fields being an email address. "Match owner" will attempt to look up the field that contains the email address and attempt a match.
In order to do the look up the engine needs to check a different form. This is the "Match Form Id" field.
Within that form, the email address field is identified as "Contact (Email) Field". This field should contain the proper email address of the contact.
Two other fields for each contact can also be specified.
- Each contact can have a link to a Companies form. i.e. this person is associate with this company
- Also a staff drop down list to signify the "owner" of this contact can be specified
So now the engine can do a look up on the email address and link it with a person, a company and a primary owner who works in the business.
With these lookups complete the engine needs to know which fields to store the results in which gives rise to
- Contact Result field : Will store the Id from the Contacts form intCDA_X_Id
- Company Result field : Will store the Id from the Companies form
- Owner Result field : Will store the user id from the bxp system who is responsible for these emails
Finally as the look ups are done there are a number of potential set outcomes to the matching process.
- No contact found
- Contact found, Company not found
- Contact found, Owner not found
- Contact found, company and Owner not found
- Contact and Company found, Owner not found
- Contact and Owner found, Company not found
- Contact found
- Contact and Company found
- Contact and Owner found
- Contact, Company and Owner found
- Identified as spam, search not performed
The results of these attempts are stored in "Matching result field"
