Release Highlights
Purge Database
Purging is the process of freeing space in the database by deleting obsolete data that is no longer required. The Adonis Replicator now offers the functionality to delete obsolete person information onboard. The Replicator supports two methods; One deletes persons that have not received updates from the main-site or hub for an n number of dates, or two by using SQL.
For more information, see: Purge Database
Scheduled program update
In version 2021.10, we have finalized the scheduled program update, allowing you to distribute and execute the Adonis Personnel Manager and Personnel portal.
For more information, see: Scheduled Program Update
Android Replication Monitoring Service
The Android Replication Monitoring Service (ARM) allows real-time replicator surveillance from your mobile phone Android only.
This service developed for our internal support and technical team is now available for our customers.
The ARM is available as SAAS or On Premise. Please contact our sales department for pricing details.
For more information, see: Adonis Replicator Monitoring Service
Resolved Jira Issues
Key | Summary | Issue Type | Release Notes |
|---|---|---|---|
AR-90 | Change to new Modified Icons | Change Request | Updated icons for application and installation set |
AR-94 | Replicator throws sql Security Error | Bug | To support TLS 1.2 and above we have implemented the possibility to support multiple database providers. In the connection properties, you can select the OLE DB Provider. If you receive the following error message, see below, you select MSOLEDBSQL Connection failed:  |
AR-95 | When processing repl_delete the system should continue when deleting from a non existing table | Bug | The replicator continues with the remaining scheduled tasks after it failed to delete information from a non-existing table. |
AR-98 | "Connection closed gracefully" during connection to SFTP | Bug | To transfer replication files via SFTP protocol, select SFTP as the mail system on the first page of the replicator settings wizard. The settings page for setting up a connection to an SFTP server is almost the same as the FTP settings page. The SFTP protocol is a subsystem of the SSH protocol and it protects the communications between client and server with strong encryption. This is why there is one important difference between setting up an FTP connection and an SFTP connection. Before the replicator can connect to an SFTP server automatically (and transfer files to and from it), a person who sets up an SFTP connection must verify the server's host key. This can be done with the Test connection button on the SFTP settings page. In the middle of the SFTP connection test, you can see a dialogue box that shows the host key fingerprint. The dialogue enables you to verify or reject the server's host key.  A dialogue looking like this will be shown each time when you hit the Test connection button on the SFTP settings page. Due to his, you can always know the server's key fingerprint. You can also cancel the key verification if you do not trust the server anymore and then the replicator will not be able to connect to the server automatically. Before setting up a connection to an SFTP server, we recommend reading short descriptions below that explain how to authenticate a server by its SSH host key. Links: |
AR-111 | Allow dropping repl_Distrib_PW001OLEDOCS table | Bug | We changed distrib update query, and now it updates only those records where the state is actually changed. This optimization will reduce the amount of data the query writes to the transaction log |
AR-113 | Not possible to use CTE (WITH Statement) in the select statement used as the restriction query | Bug | Common Table Expressions (CTE) as restriction queries are now supported. |
AR-124 | Not possible to use CTE (WITH Statement) in the select statement used as a purge rule | Change request | Implemented support for common table expression in the purge query |
AR-140 | P0P, P1R, and P05, P08 updates not picked by Replicator for no reason | Bug | Fixed the initialization problem when setting up a partial replication. In certain situations when the first time replication of the restriction query did not result in any pin, persons, to export. The system treated the next exports as if the destination site was a full replicated database that is transferred into partial replication site. |
AR-100 | New loading screen | Change request | Updated Icons for login and loading screens |
AR-116 | Incorrect purge of distribution tables | Bug | Modified purge database query to only delete records related to the current destination site |
AR-42 | Add a setting for update timeout | Change request | If due to some reasons the upgrade process is performing longer than value PROG_UPDATE_TIMEOUT_MIN from Replicator.ini then the upgrade won't be finished and the corresponding error message will appear in the Last Update Log. |
AR-125 | Change type of PKS parameter to match db field type | Change request | Various performance-related improvements. |