Only administrators have access to this tab
This page describes the pages available through the Settings tab in the Appian RPA Console.
You'll find Appian RPA customization and configuration settings on this page.
This section shows read-only information about your Appian RPA instance. This information is for reference and can't be changed.
From this section in the configuration, it is possible to customize the console with the following properties:
- Language: Choose a language for the Appian RPA user interface: English or Spanish.
- Identifier: Console identifier. This information will always be provided by the Appian RPA team and is associated with the console license.
- Instance: Instance name of the console. Just like the identifier, it will always be provided by the Appian RPA team and is associated with the console license.
- Console URL: URL to access the console. It can be useful, for instance, when it is wanted to expose an on-site console outside a corporate network.
In this section, configure console restart behavior.
- Restart: select SSH + command
- Port: Port to establish the SSH connection
- Username: Username for the SSH connection
- Password: Password for the SSH connection
- Command: Command to execute in the machine for the restart
This section of the Configuration page is no longer in use. User access to the Appian RPA Console is managed through Appian. The password requirement options listed here no longer apply and should be disregarded.
SMTP Email configuration
This section allows you to adjust the email server settings used by Appian RPA. The platform uses SMTP to send emails. The settings specified in this section allow you to access the server using this protocol.
- Host: email server's URL
- Port: access port, SMTP, to the email server
- User: username to access the email server
- Password: password to access the email server
- From (email): address that appears on emails sent from the Appian RPA Console
- From (name): name that appears on emails sent from the Appian RPA Console
- Use TLS: enables the TLS security protocol for sent emails
- Check email: email address to be used for testing these setting. Click Check to send the test email.
- Send exceptions: choose whether to send an email every time an exception is thrown
- Exceptions to (emails): email addresses where to send the trace logs of the exceptions thrown in the
console. The field Send exceptions must be enabled. Separate multiple email addresses with commas.
Default dashboard configuration
This section of the Configuration page is no longer in use.
This section shows information for the tools connected to Appian RPA to develop and execute robotic processes, such as Nexus and Maven.
The fields are populated with default information. Do not change these settings.
- Default repository URL (/ ending)
- Default repository username: If you change this value, Appian RPA won't be able to authenticate with Nexus and robotic process executions will fail. Don't change this value.
- Default repository password: The default password listed here is auto-rotated when the Appian RPA Console is opened. If you change this value, it won't auto-update and will be unable to authenticate. Appian RPA won't be able to connect to Nexus and robotic process executions will fail. Don't change this value.
- Maven home
- Default group identifier
- Default initial version
- Tesseract command
- Tesseract data folder (tessdata)
- Mongo commands folder
- Docker command
- VirtualBox command
Server trace configuration
The options in this section let you customize server logs that appear on the Maintenance page. Choose what type of information to include, as well as file sizes. To achieve proper log configuration, remember that log files can consume a lot of disk space in the server.
Configure the following options:
- Application server: Minimum log level for the application server log system. Traces below this level will be ignored.
- Appian RPA: Minimum log level for the Appian RPA log system. Traces below this level will be ignored.
- Maximum file size: Maximum file size for a trace log. Once the maximum file size is reached, the file is archived. A new trace log file is created each time the maximum is reached.
- # backup files: Maximum number of backup files to keep in the server. Once reached, an older file will be removed and replaced by a newly generated file.
- File per resource: when enabled, it permits to create an additional log file for each resource configured in the Console. This way, it is possible to read the log of a specific resource separately.
- Only use specific: when enabled, the log traces will only be written in the log file of the resource, so it won't be replicated in the other files.
On the Maintenance page, you can view log files generated either by the console, the server, or the resources.
The page shows a list with all the log trace files stored on the server. You can download them to conduct the necessary audits. When the files are no longer needed, you can remove the selected files to save space on the server.
On the Sessions page, you can access the list of currently active Console sessions. You can see the users logged into the console, their IP address, the timestamp for when the logged in, when they last accessed the Console, and the session's expiration (normally 30 minutes after the last access).