August 2024

main27765

21 Aug 2024 

Stable

Upgraded the org.json.json library from v20090211 to v20240303, which is fully backward compatible.

Enhanced the REST OAuth2 Account with Snaplex support for executing OAuth2 operations.

May 2024

main26341

08 May 2024 

Stable

Updated and certified against the current SnapLogic Platform release.

August 2023

main22460

16 Aug 2023 

Stable

Updated and certified against the current SnapLogic Platform release.

For Snaps using AWS Signature V4 accounts, DNS canonical names are now supported for S3 buckets. 

The REST AWS Sig v4 Account is now enhanced with the AWS Region and Service Name fields that enable the Snap to support Virtual Private Cloud (VPC) endpoint.

• You can set cookie policy specifications using the Cookie Policy dropdown list in REST Snaps .

• Support for auto-retries where the REST Snaps automatically retry when they encounter 429 HTTP status code - Too Many Requests error.

• The REST AWS Sig v4 Account supports:

  • Passing AWS Security Token Service (STS) temporary credentials in the Security Token field.

  • Expression values for Access-key ID and Secret Key fields.

• Improved the performance of REST Snaps when the Snaps encounter Unauthorized (401) or Forbidden (403) errors even when the user credentials are available in the organization and the account type is OAuth2.

429patches17084

• Enhanced the REST Snaps with support for auto-retry where the Snap retries automatically when the Snap encounters 429 HTTP status code - Too many requests error.
• Improved the performance of REST Snaps when the Snaps encountered errors due to Unauthorized (401) or Forbidden (403) statuses though the user credentials are available in the organization and the account type is OAuth2.

Added the REST In-memory OAuth2 Account type with Client Credentials Grant Type that supports and stores the access token in memory for reuse until it expires. When the Snap encounters 401 or 403 errors, this account generates a new token after refreshing the cache.

Fixed an issue that caused REST SSL accounts to fail when the username in the REST SSL Account was null and the Enhanced Encryption level was low, medium, or high.

• Enhanced the REST Post, REST Put, and REST Patch Snaps with the Multipart Type list to support multipart (files and text) upload.

• Renamed the following fields:

  • Upload File(s) field set to Form Upload

  • Upload-file key to Multipart Key

  • Upload file to Multipart Value

4.27

main12833

13 Nov 2021 

Stable

Fixed an issue with the REST Post Snap, where the Snap delayed the fetching of documents, when the batch size is greater than or equal to one.

Enhanced the REST Post Snap to display all cookies (securedauth cookies and httponly cookies) from the CookieStore along with headers when you select the Show all headers checkbox.

• Fixed the REST Post Snap that fails to correctly set the Content-Length header when working with multi-file uploads.
  
• Added Send Client Data as Basic Auth Header check box to the OAuth2 and OAuth2 SSL accounts. This check box enables you to include and pass the client credentials information in the header when connecting to the OAuth endpoint.
• Added a new account type REST AWS Sig V4 Account that adds the ability to call any AWS API.

• Added a new account type, REST OAuth2 SSL, which enables support for the OAuth2 SSL authentication for REST Snaps with endpoints that require client certificates.
• [Docs Update] Applied the enhanced doc template to the Snap Pack's documentation. Improves usability by enhancing Snap field descriptions, functional examples, and use cases. 

snapsmrc542

4.20

snapsmrc535

Stable

• The new Multipart related option in the Upload body type property in the REST Post Snap enables you to post files to the Google Drive API and retain the original names.
• The REST Account now has a new Grant Type option called Client Credentials. This enables the Snap to obtain an access token to the client ID and client secret through the token endpoint URL.

Fixed a regression issue wherein REST Snaps are unable to handle empty XML responses when Show All Headers is enabled.

4.18

Fixed an issue with the NLTM Rest account connection hanging infinitely.

4.14 Patch

rest5782

Fixed an issue wherein the REST POST Snap was not accepting any blank values from upstream Mapper Snap.

Fixed an issue where the Ultra task was not producing a valid response while acknowledging documents.

4.14

snapsmrc490

4.13 Patch

REST POST Snap: New properties: Multipart Content-Type, and Filename to be used added.

Fixed an encoding issue with the REST Get Snap so that it uses the same encoding format (UTF-8) by default on all machines instead of using a different encoding format based on the machine's Operating System.

Fixed an issue that caused the REST OAuth accounts to fail when running in orgs with Enhanced encryption in Medium or higher level. 

Enhanced REST Post Snap to prevent it from encoding file names.

Added Upload body type property to the REST Post Snap for processing the specified content type.

Added support for the Binary File Uploads with the REST POST Snap.

Updated support of NTLM Account Authentication to the REST Snap Pack.

Resolved an issue with the REST GET Snap that often fails to exit properly. This should reduce or eliminate that problem.

Addressed an issue with REST Get displaying the authorization header in plain text

Added Connection timeout property to specify the number of seconds to wait before terminating a connection. The Timeout property has been renamed to Read timeout.

• Addressed an issue in the REST Post Snap with the REST API not returning a full cookie response.
• Added Show all headers setting to the show full cookie response for the Post, Put, Patch and Delete Snaps.

Resolved an issue with REST Get not handling multiple response cookies.

Added a new "Follow redirects" setting to toggle whether redirects should be followed (default behavior is to follow redirects)

• Updated Snaps in the REST Snap Pack with Response entity type field(The DEFAULT option under this property allows the backward compatibility. The addition of the property will not affect the existing production pipelines and allows them to run as before).

• Updated Snaps in the REST Snap Pack with Maximum request attempts and Retry request interval Upload fields.  

• Updated the RESTPost Snap with Upload transfer request type field.

Resolved an issue where Rest Snaps failed to process the received response that is encoded in charsets such as Windows-1252. This fix will process the response purely based on the charset provided in the Content-Type header.

• A new property was added to the REST Get Snap to specify the iteration interval for pagination.

• All Snaps now have at most one input and one output view.

Resolved an issue with REST SSL Accounts with Username not send the Authorization header with the HTTP request.

REST Get now supports using parameters from an input document in the Next URL Setting.

Addressed a defect where REST GET Snap fails saying 'Scheme "http" not registered'

• Two-way SSL support was added to the REST account.

• REST Get 

  • Now has support for iterating over additional result pages.

  • Header variables are now being updated for each input

• REST Post

  • Improved error handling messages.

  • Resolved an issue with the Snap failing with "Failed to execute HTTP request" error.

• Maximum retries and Retry interval support added.

• Resolved an issue with using a REST Dynamic OAuth2 account with Facebook Graph API.

• REST Account: REST SSL account added.

June 27, 2015 (2015.22)

REST Get now allows you to have no output views. Previously, there was exactly one output view.

Rest Post Snap now supports posting a file.

May 2, 2015

REST: Output views made optional 

January 2015

Optional Raw data property added to all REST Snaps. If selected, the HTTP response content is written to the output view as is. If not selected, it is parsed according to the content type specified in the response header.

October 18, 2014

• NEW! REST Patch Snap introduced in this release.

• Addressed an issue where REST GET (and perhaps REST Snaps) error view does not include response body. 

Fall 2014

REST Get: support added for gzip format.

June 30, 2014

Addressed an issue with RestRequestExecutor class writing data into error views even on successful requests status code 201, 204.

May 2014

July 2013

• NEW! REST Delete Snap introduced in this release.

• NEW! REST Get Snap introduced in this release.

• NEW! REST Post Snap introduced in this release.

• NEW! REST Put Snap introduced in this release.