How do I configure In Out email server settings and general parameters?
This feature allows the configuration of data related to the
SMTP
(Simple Mail Transfer Protocol
) server
that will be used in sending automatic emails and general system parameters
, such as the number of interfaces that can be run in parallel.Editing system settings
Email
- Access the menuRegistration > System Definitions.
- On theSystem Settings Detailsscreen, clickEdit.
- According to the settings, update theEmailtab information.
* Required fields- Host (SMTP)* and Email Port*: Default server address and port by which the system will communicate with the service the company uses to send emails. For example, if the company uses Microsoft Outlook, these fields should be populated with smtp-mail.outlook.com and 25, respectively.
- User Login: The login username on the server (that is, the username of the account that will be used to send emails), for example: john.smith.
- Uses Authentication: The use of authentication allows secure sending of emails by the server, ensuring that the user exists, has a valid account and is who they claim to be. If this field is checked, the server will require alogin password
- Password Login: Login password for the server (i.e., password for the account that will be used to send the emails).
- Email Source:Sender's address of automated emails, for example: john.smith@company.com.
- Email Recipients Notification Service: Addresses receiving automated emails, for example: mary.smith@company.com and ann.smith@company.com.
- HTML notification: A method for sending notifications (in HTML format) to recipient email addresses. This submission can be done in an attached file or inline (in the body of the email).
- ClickSave.
General parameters
- Access the menuRegistration > System Definitions.
- On theSystem Settings Detailsscreen, clickEdit.
- Click theGeneral Parameter tab.

- Click theEdit
button for the descriptionwhosevalueyou want to update:- Language used in translations from service runs: 0-Portuguese, 1-English, 2-Spanish
- Value: 0 (Portuguese), 1 (English), or 2 (Spanish)
- Example: 1 (translations originating from service runs must be made to English)
- Last deletion of old records - DO NOT CHANGE. AUTOMATIC GENERATION
- Dateandtimeof last time old records were deleted. This parameter is automatically valued and the value should not be changed.
- Indicates whether a return file will be generated with data from the execution of the Drawback input interfaces.
- Value: Y (yes) or N (no)
- Example: N (no return file should be generated with data from the execution of the Drawback input interfaces)
- Day of the week, in English, to run record deletion (ALL, SUNDAY, MONDAY,...)
- Value: All, Sunday, Sunday, Tuesday, Wednesday, Thursday, Friday or Saturday
- Example: Monday (records should be deleted every Monday)
tipThe default value is ALL. - History deletion processing schedule (HH)
- Amount: 24-hour format (today)
- Example: 06 (respecting the configured day of the week, the deletion of history should be processed at 06:00)
- Minimum button time: Releases Execution (in hours, minimum 1hour)
- Value: time in number of hours
- Example: 1 (release button must be enabled after 1 hour of actual execution attempt)
- Number of interfaces that can be run in parallel
- Value: quantity in number of interfaces
- Example: 30 (up to 30 interfaces can be run at the same time)
- Number of records per transaction in processing (COMMIT)
- Value: quantity in number of records
- Example: 300 (every 300 records, all transactions must be processed in the database)
- Deadline for elimination of internal processing date history (days)
- Amount: due date in consecutive days
- Example: 120 (every 120 days, history of processed imports and exports must be cleared )
- Deadline for eliminating import errors (days)
- Amount: due date in consecutive days
- Example: 15 (every 15 days, import errors should be deleted)
- Deadline for elimination of import history (days)
- Amount: due date in consecutive days
- Example: 90 (every 90 days, import history must be cleared)
- Wait time for thread release in case of lock of all open threads
- Value: time in number of hours
- Example: 2 (2 hours should be the maximum wait time for one interface to finish running until another is triggered)
- Time to end execution by time out
- Value: time in number of hours (whole numbers only)
- Example: 24 (an interface must run within 24 hours)
tipThe recommended value is 0. - Wait time for a new interface to trigger
- Value: time in number of seconds
- Example: 5 (new interfaces should be triggered every 5 seconds)
- Last compression - DO NOT CHANGE. AUTOMATIC GENERATION
- Value: Automatically generated by the system and records the date and time of the last execution of the compression routine. This record is used to calculate the timing of the run, based on the time and frequency defined. This parameter should not be changed manually.
- Deadline for processing the Compact routine (days)
- Value: Defines how often the compression routine should be executed. This integer value determines the interval of days between runs.
- Example: If set to 7, the routine runs every 7 days.
- Compact Routine Processing Time (HH)
- Value: Integer number between 1 and 24, which determines the specific time of the day on which the compression routine is to be automatically executed.
- Example: If set to 3, the routine will run at 3 a.m.
- Open Arena Integration
- Value:The Open Arena Integration parameter enables artificial intelligence (AI) on the system interfaces. With the Y (Yes) value, AI is enabled on multiple screens. With the value N (No), AI is disabled.
- Example:When AI is enabled, you can useAI Error Insightson theOutput Interface History (LOG)screen.
- ClickSave.
Exporting the values
- Access the menuRegistration > System Definitions.
- On theSystem Settings Detailsscreen, click theGeneral Parametertab.

- Check the parameters you want to export.To export data from all rows in the table, this marking is not required.
- Click
Export.
An Excel file will be generated with the desired parameter
descriptions
and values
, for example: