The actions that can be assigned to an email are as follows:
Rule Action |
Description |
---|---|
Add Group |
This will tag the email to an email group, as defined in Tools > Setups > Email Folders. If you want to tag this email to multiple groups, you can add the action multiple times to the rule. |
Create Job |
This will create a new job. For this action to be successful the email must already be tagged to a card file. In creating the job, you can define: ▪The Jim2 user for the job, eg. who the job is assigned to. ▪The job Item, eg. sales, service, etc. ▪The job priority, eg. normal, urgent, etc. ▪The job type, eg. NORMAL, CONTRACT, WARRANTY, etc.
If the card file tagged to the email is a ship only card file, the parent card file will be used for the Cust# and the email card file used for the From# and Ship#.
The email will be tagged to the newly created job. |
Auto Assign Email Groups |
This action will search previous emails sent from the same Jim2 object, and link previously linked email groups to it. For this action to work, the email must be tagged to an existing Jim2 object. |
Determine CardFile from Email |
The email will be linked to a card file based on the sender's email address. For this action to work, the email address must be in the contacts on the card file. |
Determine CardFile from Contents |
Using a regular expression, the email will be searched to try and find a Jim2 customer card file code. You can define if you are searching in the email subject, email body or both. If the search is successful, the email will be tagged to that card file.
You are able to use the variable <CustCode> in your regular expression when looking for the Jim2 customer card file code. |
Determine CardFile from Website |
The email will be tagged to a card file based on the domain portion of the sender's email address. For this action to work the sender's website must be on the card file, using the contact type: Web. |
Delete/Purge Email |
If the conditions are met, the email will be deleted, ie. it will be added to the Deleted Email folder. If you choose the Purge Email option, the email will be purged and will not be found in any email list.
Note: If you use the Purge Email option, the email will be permanently deleted. There will not be any record that the email was ever received by Jim2. |
Determine Project from Contents |
Using a regular expression, the email will be searched to try and find either a project serial number or the project code. You can define if you are searching in the email subject, email body or both. You are able to use the variables <SerialNo> when looking for serial number and <ProjectCode> when looking for project code in your regular expression. |
Determine Project from Email |
The email will be tagged to a project based on the sender's email address. For this action to work, the email address must be in the contacts on the card file, and there can only be one project (multiple projects per card file will not work). |
Determine Project from Website |
The email will be tagged to a project based on the domain portion of the sender's email address. For this action to work the sender's website must be on the card file, using the contact type: Web, and there can be only one project (multiple projects per card file will not work). |
Determine Job from contents |
Using a regular expression, the email will be searched to try and find either a job customer reference or a job number. You can define if you are searching in the email subject, email body or both. If the action is successful, the email will be tagged to the existing job.
You are able to use the variables <CustRef> when looking for a job reference, and <JobNo> when looking for a job number, in your regular expression. |
Process as order |
Simplifies the processing of incoming XML orders by making use of the Jim2 incoming email functionality. This provides much better control and visibility of email order processing within Jim2, and negates the need to use POP3ToJes. All existing email conditions and actions apply when using this action.
In basic terms, an email with an attached XML order comes in via email and is processed via email rules. If the email rule conditions are meet, the Process as Order email action places the email attachment (eg. XML order) in the incoming eBusiness queue for processing. Once the XML order is placed in the incoming B2B queue, the normal Jes XML order processing then occurs.
As with all incoming emails, the email can be tagged, viewed via an email folder, then deleted after a certain amount of time, etc.
Note:This email action requires Jim2 eBusiness Link for orders to be processed. |
Execute Action |
Choose from:
For example (using the Billing action above), based on a given set of conditions applied to an email, run a Powershell Script via the Execute Script action and create a billing job. |
Execute Script |
Allows execution of a server-side Powershell script for a given email.
This functionality allows access to the Jim2 API (as used by Jim2 Mobile), and allows almost anything to occur on receipt of an email. Jim2’s scripting engine provides creation and editing of Powershell scripts via the server script type.
For example, based on a given set of conditions applied to an email, run a Powershell Script via the Execute Script action and create a job..
This functionality is currently limited to internal use by Happen, but provides an incredibly powerful method to enhance email and business process automation on behalf of our customers. |
Execute Template |
Here, you can choose a project template for execution. |
Process as MPS Connector |
Allows an email to be qualified and passed through for processing via an MPS Connector. |
Additionally, the following applies to email rule action processing:
Auto Run
The actions in the table above are set by default to run. You can also choose specific actions to not run automatically.
When this is set and the conditions are met, the email summary will show that an action is available. You will need to click Run to run the action.
Here is an example where a Create Job action is ready to run.
Further information: