Page History

Enhancements

• Create Report in DataSync Agent will now create a folder of log files that are 7 days old. Any log files older than 7 days will be deleted. 

Enhancements

• In the DataSync Agent, running too many threads can slow down the process. To avoid this, a warning will appear when more than 64 threads are created. 

• In DataSync Agent for Salesforce, the <schema_connection> directive's value will be in the format https://login.salesforce.com or https://login.salesforce.com/services/oauth2/token.

New Features

• Setup DataSync Agent for Snowflake through the Agent Installer.

• More visibility into batch receipts generated by the DataSync Agent is now available by configuring your DataSync agent to receive receipts.

• You can now truncate string values if you have exceeded a column's max length (UTF-8) in the DataSync Agent.

Enhancements

• Configure the number of times the DataSync agent will retry after a SQL error with <sql_retries> in the agent.xml.

• Improved better error handling for DataSync agent when messages have empty values.

• DataSync agent name is now automatically generated from the instance name as instancename_subscribe.

• Choose to use the JDK/JRE directory path defined in the JAVA_HOME environment variable when configuring your DataSync Agent.

• The agent.xml configuration file's <database_parms> directive has been standardize.

• Ability to select which temporal columns will be primary key in agent.xml.

• Configure the time difference between temporal entries with <timestamp_difference> in the agent.xml.

• Added machine's hostname, internal IP address, Java version and OS version to DataSync Agent's heartbeat.

• Validation of Repeater Agent installation to confirm if the replicator agent has been installed properly.

• Updated DataSync Agent to utilize 3.9.0 Snowflake JDBC driver.

• Configure your DataSync Agent with sorting your database columns in alphabetical order with <column_sort> in the agent.xml. 

• Prevent your DataSync Agent from altering your database column size with <database_static_column_size> in the agent.xml.

• Polling interval is now limited to 5 seconds or greater. If the polling interval is set to less than 5 seconds, it will default to 5 seconds.

• Repeater agent supports Java 12.

• DataSync agent supports Java 12.

• To ensure multibyte or foreign characters are saved properly for string column types, the DataSync Agent creates column types that can store unicode string data. Changing the data type to your configuration is now available.

• You can now add the tag <skip_duplicates/> to the agent.xml to skip adding temporal rows for duplicate records. 

• S3 file subscriber now allows multiple layers of folders following the bucket name. See the <s3_bucket> directive for more information. 

• Default <skip_table_stats/> when installing SQL Agent through the installer.

• DataSync agent supports Java 13.

• In DataSync Agent for Salesforce, the <schema_connection> directive's value will be in the format https://login.salesforce.com.

Bug Fixes

• Tasks pointing to the same database and server will allocate and start only one table stats collector to avoid placing excessive load on the agent and the database.

• DataSync Agent will now replicate records with foreign character. Having the previous DataSync Agent release will still have the issue, simply upgrading to Gold WILL NOT fix the issue. Check out the following link to fix the issue: Why am I having error replicating records with foreign characters?

• The DataSync Agent's database directive, <database_parms>, now includes another default value (autoReconnect=true) that will save records in the database even when there is no activity in the instance. 

• Fixed an issue where the Agent only ran table stats once instead of intervals

Known Issues

• <batch_insert> and <batch_update> commands do not work properly when reading messages from a queue that has records from different tables. To use these commands, the queue should only have records from one table.

New Features

• Added the ability to send out attachments from Task in Salesforce.

Enhancements

• Enhanced the ability for Salesforce to show what version of records are shared out.

Bug Fixes

• Fixed an issue when setting "Time to Keep Error Logs" = 1 Week in Perspectium Properties caused an error.

Known Issues

• Description field for Perspectium jobs must be left empty by default in order for jobs to process. For a workaround, go to Troubleshooting DataSync for Salesforce and see Why doesn't the Perspectium Job in Salesforce continuously run?

New Features

• Added Delete All option in list view of Perspectium objects such as dynamic share and bulk share to delete all selected records at once.

• Temporal agent is now functional with DataSync for Salesforce.

• Scheduled bulk share is now available in DataSync for Salesforce. 

Enhancements

• Optimized Perspectium Apex Triggers to improve performance and speed.

• Improved error handling for previewing Salesforce bulk shares.

• Previewing a Salesforce bulk share will be prevented while a bulk share is running. 

• A target queue error notification will no longer display upon creation for bulk shares and dynamic shares.

• The Salesforce application will set a header with the number of messages being sent on each post to the Integration Mesh.

• The Salesforce application now sets a header with the org name for each post to the Integration Mesh. 

Bug Fixes

• MultiOutput processing jobs will no longer be present in scheduled jobs after deletion.

• Arrows are centered in the Fields to Share and Include Child Records in the dynamic share and bulk share when selecting records for those fields. 

• Misspelling fix for the success message that appears when After Save Trigger is clicked in the dynamic share. 

Known Issues

• Description field for Perspectium jobs must be left empty by default in order for jobs to process. For a workaround, go to Troubleshooting DataSync for Salesforce and see Why doesn't the Perspectium Job in Salesforce continuously run?

Enhancements

• Enable skipping empty field values in the messages created by using hideEmptyFields in your Meshlet Configurations for Splunk.

• Splunk Meshlets will now process referenced field values such as assigned_to, company, etc. 

Enhancements

• Include all the data for a record's fields in the event field when configuring your Splunk meshlet by using saveInEvent. 

• Configure your Splunk meshlet to dynamically set table name by adding $table value in sourceType.