Service Management Project
Attachments and Images Directory
Define the parameter ID = 479 value informing the attachments directory, where the files used to e-mail readout and dispatch will be stored; It also must be mapped in the volumes of the docker containers.
E-mail dispatch
To utilize the e-mail dispatch through Graph Mail integration, it is necessary to define the parameter MAIL_AUTHENTICATION_TYPE – ID: 477 with the options Microsoft Graph Mail, for a general parameterization where the default value will be used: graphMailQueue, for the name of the mail queue. In case the user desires a configuration for each mailbox, configure the email box screen, with the name of the registered queues in WildFly:
📌IMPORTANT!
The email dispatch control was altered, therefore the old classes ControleEmail and ControleEmailNotificacao should not be used for sending in rhino scripts. Instead, the classes MensagemEmail or MensagemEmailNotificacao.
E-mail readout
The system will read a Microsoft E-mail inbox through the Oauth2 authentication method, shooting registered and defined automatic actions for each inbox and folder. Provided by Microsoft, the SDK java will be utilized to simplify and make the integration safer and more adequate. This new implementation does not interfere with the reading process and automatic actions shooting (that already exist, or that use Job-Quartz) for e-mail readout using IMAP and POP3.
The Service Management Project:
- Listens to queues registered on the automatic action screen via e-mail;
- For each retrieved message, the system obtains the automatic action configured from the name of the queue and the folder; It also implements the feature to avoid multiple searches to the database for a configuration already retrieved, during processing;
- Processes the retrieved action using the contents of the retrieved message;
Readout Configuration
The user must register the automatic actions, which must be shot with each e-mailed reading carried out by a Microsoft account; For correct operation and because the search is case-sensitive, it is necessary the name of the queue and folder to be exactly the same as those parameterized by the infrastructure. If during execution the system finds an automatic action configuration via e-mail that is active, that has a queue read by the system with the name and the registered folder is the same, the authentication type is MICROSOT_GRAPH and the end date is empty, it will trigger this action passing as parameters the information read in the e-mail;
It is important to point out that the scenario of folders for reading and automatic actions that must be triggered needs to be considered before starting the infrastructure configuration, bearing in mind that the static parameterizations cannot be changed within the system running, as it implicates onto changing standalone.xml, config.properties, and System-properties files.
On the automatic action configuration via e-mail screen, it is still possible to configure the reading job via IMAP and POP3, as well as the new form of integration with Microsoft graph, as in the following image:
For the readout through Graph Mail:
Or through Job – IMAP or POP3:
