Email rules are the rules that are applied to incoming emails as they are received. Rules are based on conditions and actions. If an email meets the conditions, apply the actions.
Add as many email rules as required and control the order in which they are applied to incoming emails. Once a rule has been run and its conditions met, choose to stop processing any additional rules. This allows rules to be effectively chained.
 |
It is suggested to create a rule for each email account to ensure emails arrive in the correct folder. |
For example, the first rule may be to determine the cardfile to be related to the email, then additional rules apply email tags, then even more rules create a job, etc.
Typically, set up the first two rules, as follows:
This rule will apply to all incoming emails, and attempts to match the sender's email address to a cardfile in Jim2. Once this rule has been processed, the following rule will be executed.
|
This rule will check if the email is related to an existing Jim2 object (job, quote, etc.), and will apply the tags from any existing emails related to that object. The email is related to the Jim2 object because it has an email token in the subject.
Example Rule: Create Job from Email 
This example rule will do the following:
Conditions Check that the email was sent to, or via training@, and that it is not related to an existing Jim2 object.
Actions If the above conditions are met, tag the email as Training. There is one more action to this rule: Create Job, but it is flagged as <Manual>. This means that this action applies to this email with the intention of not automatically performing this action.
When viewing the email from an email list, it is flagged that there is an outstanding action (
This function is only available if the company is licensed to use eBusiness products.
Email rules include a Process as Order email action. The purpose of this action is to simplify the processing of incoming CSV or XML orders by making use of Jim2 incoming email functionality.
The Process as Order email action provides much better control and visibility of email order processing within Jim2.
All existing email conditions and actions apply when using the Process as Order action.
In basic terms, an email with an attached CSV/XML order comes in via email and is processed via email rules. If the email rules conditions are met, the Process as Order email action places the email attachment (eg. CSV/XML order) in the incoming eBusiness queue for processing. Once the CSV/XML order is placed in the incoming B2B queue, the normal Jes CSV/XML order processing then occurs.
Processing of incoming orders in CSV format supports multiple orders in one file. If there is an issue within the file, all contained orders will not be processed.
The mapping name must match the name of a mapping configuration file in the Jes OrderMapFiles directory. Should more specific mapping be required, please contact support@happen.biz to assist in developing the mapping. CSV date format is only required if the date format in the CSV cannot be parsed by the system default settings.
As with all incoming emails, the email can be tagged, viewed via an email folder, then optionally deleted after a certain amount of time, etc.
Rule: Decoded text This option allows email actions to be applied to an email’s decoded text within the Email Actions screen. Decoded text is a text version of an email with all HTML markup, etc. stripped out. This greatly simplifies the process of extracting information from an incoming email – looking for a serial number, for example, which typically requires the use of a complex Regular Expression.
By default, Email Rules will always be applied to the decoded text. To use the raw email content, tick Use raw content when entering a Regular Expression.
The decoded text that the email action will be applied to is available directly from an email within Jim2 by opening the email, selecting Properties, and selecting the Email Body – Text tab.
The same source can use any number of different templates. Jim2 will then randomly pick a template when sending this type of email.
Email rules Project support (only applies if the company is licensed to use Projects):
 |
). The email can then be qualified, eg. this is a support email, then the action manually run, at which point a job is created.
Further information