Version
Release Date: March 11, 2021
New Features |
---|
Use <batch_flush_interval> for the number of seconds that will trigger a batch SQL statement execution with batch processing. |
Use <skip_performance_tag> to stop the Agent from reporting performance metrics (statsx) to the Integration Mesh. |
Enable truncating table in the database by the DataSync Agent using Truncate Before Share. |
<use_instance_credentials/> is now available to use instead of access keys in AWS S3 Subscriber Agent to use IAM roles when uploading to the S3 buckets. |
Customize your temporal database table's archive date and time stamp in the psp_valid_to column with <archive_datetime/>. |
Enhancements |
---|
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. |
Bug Fixes |
---|
Error when inserting/updated a record into a SAP HANA table that has 2 billion+ rows because of metadata query. |
The attribute, use_basic_consume, in the agent.xml will reflect on the protocol given upon the configuration in DataSync Agent installer. |
Emojis will no longer be removed in incoming messages to the DataSync Agent when at lease one custom schema feature is used (tablename, column_name, _dv suffix). |
After deleting a field from a ServiceNow table, the old value of that field will no longer be inserted into the database. |
After adding a string field with default value in a ServiceNow table, executing a bulk share will no longer generate a timestamp error. |
Table stats data will now show the correct timezone offset. |
Removed Features |
---|
Removed the following DataSync Type options in the DataSync Agent Installer that are no longer being used: Rabbit MQ and Other. |