Emails provide an easy way to notify users about various events in the system:
- user's approval needed
- state of the ticket changed
- new comment added to a ticket
- announcement
- etc.
In SimpleOne, email processing can be automatic within the system without third-party applications.
In these articles you will learn:
- how to configure email accounts
- how to set up automatic creation of records in specific tables depending on what email you received
- how to set up automatic email reply depending on values of specific records and received emails
- how to keep up users with what happens within the system and within their task pool
For processing emails you need three components:
- Email Account
- Inbound actions
- Notification rules
Email Accounts
First of all, you need to create necessary email accounts. They will be involved in receiving and sending emails.
The email account configuration includes the following steps:
Notifications
Notification Rules help creating automatically sent email letters depending on the status of specific records.
For example, when an incident changes to the Information Needed state, the system sends a letter with specific topic and body to the caller. That is, notifications define what letter a user will receive after specific changes in the system.
SimpleOne provides a number of out-og-the-box notification rules. Refer to the Available Notifications article to see the preconfigured notifications.
Inbound Email Actions
Configure automatic system actions depending on the specified triggers such as the topic of a letter, key words in its body, or more complex dependencies, using script. Unlike Notification Rules, inbound email actions provide a way to interact with records in the system.
For example, while processing an incident in the Information Needed state, the system will insert the body of this letter to the Additional Comment field in the Activity Feed when the caller sends their response. The condition is that the caller's letter contains a defined topic, and the number of the task matches the one in the incident record. That is, inbound email action defines what happens in the system after receiving a letter.
