ART is a reporting tool that enables quick deployment of SQL query results. Some of its features include the following.
ART comes with drivers for a number of databases. This means that you can start reporting from these databases right away and don't need to look for or install drivers for them. These include:
Where a driver is not included in the ART distribution, you can still report from that database by obtaining the driver and adding it to the ART installation.
You can specify a report to take a file parameter. Users will be provided with a dialog to select a file and this file can be processed in the report source as need be.
You can specify jobs to run in a specific order e.g. run job1, then job3 then job6.
You can specify that before a job runs, a certain condition must be checked e.g. ensuring that a table has been loaded with data before a job runs. This prevents situations where a scheduled jobs runs in error or returns incorrect results because of a problem or a delay with an ETL process.
You can specify that scheduled jobs should not run on certain days e.g. public holidays. This would prevent running or emailing of jobs unnecessarily.
You can specify that report output is encrypted using the PGP or AES algorithms immediately upon generation. This may be useful if the recipient of a file or report requires that it be encrypted and it can be done automatically on a schedule.
You can specify that PDF or Excel output be password protected upon generation. This may be useful if you need to send report output to a client or clients as password protected and can be done automatically on a schedule. The passwords can come from the SQL query of the report and so can be dynamic and different for different recipients.
You can specify multiple schedules for a report job, in case the schedule required is complex and can't be specified using a single rule.
You can specify to get an email if an error occurs when running a job. This may be useful for critical jobs where you may need to know if an error occurred for you to take action.
You can specify to get an email when application errors or warnings occur. This may be useful to know if the system is performing ok or if there are error conditions that need to be addressed. Application errors can also be viewed on demand from within the Logs page of the application or from server logs.
You can specify that users authenticate to the application using credentials in an LDAP server. This may be useful if LDAP is already used for authentication within the organisation and so users may not need to know new passwords for the ART application.
You can specify that users authenticate to the applications using credentials of a windows domain. This may be helpful to avoid users having to know a new password for the ART application and instead they can just use the password they use to log in to the windows domain.
Report output can be generated in ODF formats i.e. odt and ods. This may be useful if this format is required e.g. by regulation.
You can specify application logs to be written to a database. This may be useful to have a permanent record of the logs, and one that is more easily searchable.
Allow users to create their own dashboards by specifying which reports they would like to appear on them.
Allow users to do basic self service querying, allowing them to select the columns they would like to see and define conditions for the report. This would be useful to have users do simple ad-hoc queries themselves instead of having to go to the IT department for that.
You can send a report file to a number of destinations after a job is run. This may be useful to have backup copies of report files, or to send a report to an external recipient. These destinations include FTP, SFTP, Network Shares, Amazon S3, Microsoft Azure, Google Cloud Storage, Backblaze B2, WebDAV.
You can have a report uploaded to a website after a job is run. This may help to automate a process where a report is required to be uploaded to a website.