...
Support for SOAP web services in Proxies. You can now reference a SOAP service when you create a Proxy endpoint.
See the Platform section for Lifecycle Management Public APIs. You can now use Public API to publish, unpublish, deprecate, and retire APIs.
Enhancements
Added the Trust All Certificates checkbox in the Create proxy endpoint dialog. Similar to the setting in the REST Snaps, you can choose to allow your Proxy to trust self-signed, unsigned, or expired certificates in the endpoints.
API policy violations are now delivered in JSON. When a client executes an API that results in an authorization or authentication error, the error is returned in the JSON format.
Logging added to the Callout Authenticator API policy. You can now troubleshoot why the authentication failed when your Callout Authenticator policy rejects a client request.
Improved error output for the JSON Validator API policy. The API caller can easily determine which part of the JSON failed validation.
Wildcard endpoint support for dynamic base paths and error handling in Proxy endpoint mapping. When the base path is a path parameter, the Proxy uses this endpoint and routes through the mappings.
Improved error handling in the Developer Portal API specification editor. Specification violations now appear in the editor.
Added the Time Unit field in the Client Throttle API policy. You can now define a Request Limit value in bits per second.
...
AutoSync now supports the following endpoints:
Google BigQuery as a target
Marketo as a source
CSV or JSON files stored in Amazon S3 as a source
CSV files as a source
The ability to change synchronization type. You can now synchronize data from Salesforce to Snowflake using SCD2.
After creating a data pipeline, edit it. From the Auto Synchronize tab, select the Load type.
The types available depend on what AutoSync supports for the source and endpoint. Learn more.For a Salesforce source, AutoSync automatically handles changes to the column precision, scale, or character limit by propa
gating the changes to the target. Learn more.
Enhancements
Improved scheduling optionssynchronization scheduling. As the last step in the wizard, choose to:
Continue without scheduling.
Pick a preset schedule and set the start time.
Create a custom schedule, which allows you to set an end date.
...
Known Issues
If you save a data pipeline and then edit its name, you cannot delete it.
AutoSync cannot upload a CSV file to the cloud data warehouse if the name includes a special character, such as
#,$,%, or&.Google BigQuery does not support special characters for names. Data pipelines where the source file, table, or object names include special characters will fail. Whitespace, dash, and underscore in the names are not a problem.
At times, AutoSync cannot clean up the Google Cloud Storage staging area after loading from Salesforce to Google BigQuery. If this occurs, you should manually remove the files to retrieve the storage.
In the IIP AutoSync Manager screen, you can create Accounts to use with AutoSync. For Google BigQuery, the Account Type dropdown allows you to select Google Service Account or Google Service Account JSON, which are not supported by AutoSync.
In some cases, when you create or edit the synchronization schedule, you can select a start time in the past. If you do this for a data pipeline that is scheduled to run once, it will not run unless you start it manually.
To use the SCD2 load type for Snowflake, you must modify Snowflake configurations created before the May 2023 release. Because AutoSync automatically sets the timezone to UTC for SCD2 operations, do the following:
For an Account created in the IIP, add a Uri property parameter with the name
TIMEZONEand a value ofUTC.For credentials saved in AutoSync, delete them and create a new configuration.
...