WARNING! Please make sure that you do not use your personal email address when configuring the Cron. If you do, it will parse all email messages found, transform them into tickets and then delete the emails.
The RSTickets!Pro Cron plugin extends the standard RSTickets!Pro functionality by adding the possibility to transform an email into a ticket. Basically the administrator can configure an email account, and any emails received on that address can be transformed.
To install this plugin please refer to the RSTickets!Pro installation tutorial. After the successful installation, the Cron plugin can be accessed from within the Components > RSTickets!Pro > Cron Email Parser Configuration area
The basic Cron Email Parser configuration tab displays a list of all the current configured Crons (see image below) that are available on your installation. Yes, this is correct, RSTickets!Pro support multiple crons. A fundamental change has been implemented from its predecessor (RSTickets!). Due to use of a system plugin, now the Cron plugin will run on any page that is being accessed, no longer being chained to accessing the former RSTickts!'s Tickets or My tickets.
Upon clicking New or a editing a existing cron, the core cron configuration area will be displayed (see image below). This screen is divided into: General and Advanced. The main difference from the regular RSTickets! version is the missing Cron type option and the Advanced tab.
Main configuration area:
- Account Name: the name of the cron process.
- Server Address: the email account's server address
- Server Protocol: what email protocol should be used: POP3/IMAP
- Server Port: depending on the protocol and server side settings you have to specify the port number that should be used for the connection
- Username: the username for the specified email account
- Password: the password for the specified email account
- Check Interval: as input it uses a numeric value. This is actually the frequency of the cron. It other words, how often should the cron check the email account for new emails. The more
- Accept New Tickets From: Nobody / Registered users / Everyone. As you can see, some restrictions can be set on what emails can be passed as tickets. This verification is based on the incoming email address
- Assign New Tickets To: a list of your published departments. The tickets that arrive from the cron, can be introduced directly into a department.
- New Tickets Have This Priority: tickets that arrive from the cron will be introduced with the configured priority
- Published: yes / no
Advanced configuration area:
- Use SSL: yes / no. SSL is a cryptographic protocol that provides security for communications over networks such as the Internet.
- Use TLS: yes / no. TLS (SSL predecessor) is a cryptographic protocol that provides security for communications over networks such as the Internet.
- Validate Server Certificate: yes / no. Validate or not the SSL/TSL server. If your server connection uses TLS or SSL you should enable this.
Cron Email Parser Log
The Cron Email Parser Log displays the following information:
- Account Name: The account name for the Cron Email Parsers which activity is tracked.
- Date: The date of the provided activity.
- Subject: The subject of the tickets which were created by the Cron Email Parser or to which replies were added through the Cron.
- Description: The description of the actions that the Cron takes or attempted to take.
To trigger the parser's functionality, you need to either:
- set up a server-side cron task or
- access one of the component's pages