Uses Composite API when appropriate to improve catchup sync performance
Improvement to push changes API call that was implemented in 9.0to read back the records
Improvement to the dynamic re-sync algorithm to handle relationship sync configuration changes on the server
After sync trigger now runs right after the core sync instead of waiting for the document download which could take a while (some orgs can have thousands of files to download)
For orgs that deal with millions of records changing from batch jobs and making catch-up syncs very long, there is a new setting you can use to detect this and mark tables for resync. This will address the issues with very long catch-up syncs when large changes happen on the server
Support for a new setting to run record reachability on subsequent passes. This is implemented to address use cases when a server trigger changes a record visibility after the local updates are pushed to the server from Pulsar
Retrieve Field Service Mobile Settings via SFDC userSettings endpoint and store in a local property. Previously we relied on syncing MobileSettingsAssignment object to determine which SFS mobile settings to use but community users don’t always have access to this object. This change will address that.
Note that you do need to update the FSL file in your org for this to work.