Enhancements |
---|
Improved SQL server performance. |
Added PostgresSQL as a DataSync Type option in the Agent installer.
|
The DataSync Agent Installer will now use HTTPS as a protocol by default in <message_connection>.
|
Snowflake DataSync Agent will automatically have parameter values to default to uppercase characters after installation.
|
Choosing Manual Configurations in the DataSync Agent Installer will prompt you to contact Perspectium Support for a guided step.
|
If the agent.xml file is invalid (i.e. bad file format, missing field characters, etc), an error message will now display on the log with a description of the error.
|
Match text field lengths in your DataSync Agent with <match_field_lengths/>.
|
Check the fields values if the updated time is the same from the previous share in your DataSync Agent with <skip_duplicates check_all_fields=”true”/> .
|
Using <column_sort>alpha</column_sort> in your DataSync Agent will now sort new fields.
|
When a table already exists upon an integration, the new reference fields will now have length of 32.
|
<enable_error_log/> will now keep track of the number of invalid records and save the error count in the generated audit file.
|
<close_file_interval> is added to set the amount of time the Agent will wait for tmp files to be modified.
|
Enhanced error recovery when using temporal and the table does not exist in the database.
|
AWS S3 Subscriber Agent now supports sending receipts back to ServiceNow.
|
The <region> directive in the AWS S3 Subscriber Agent is now optional and no longer required.
|
AWS S3 Subscriber Agent logging extended for different levels.
|
Using <update_on_bulk/> will now skip duplicates in the DataSync Agent based on the message action.
|
The agent will now log a warning message that a queue will be created when messages are shared if the agent gets a 404 (queue not found) status.
|
DataSync Agent now supports Java 14.
|
DataSync Agent now supports Java 15.
|
The DataSync Agent Installer will now allow you to enter FedRAMP URLs for your ServiceNow instance information.
|
The action of processing delete messages will not alter the database tables.
|
Agent re-queues delete records up to 3 times when no record in database to delete.
|
Agents installed using the installer will create a conf/agent.xml with instances valued to 1 instead of 4 to minimize data loss.
|
Sharing records from a database to the Integration Mesh will now be consumed without errors.
|
Set your MySQL database with utf8mb4 character set and collation to accept multibyte characters in the agent.xml with <database_table_character_set> and <database_table_collation>.
|