This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
We will be releasing APIM capabilities that will be Native to the SnapLogic platform. With the release, there will be policies for access and authorization for users (OAuth) and machines (API key and token introspection), traffic control policies (e....
We are pleased to announce the upcoming August 2020 release of the SnapLogic Intelligent Integration Platform. The first deployment to UAT will take place on Friday, July 24th, 2020 at 11:00 AM PT. New features, enhancements, and documentation will b...
A highly recommended patch has been released.
We are writing this note to let you know that we have released a new build: master-7451 - 4.21 Patch 1 (Recommended). This build contains a fix for an identified security vulnerability and we highly recom...
Issue
An issue that impacts SnapLogic pipeline executions has been raised which has been traced as being caused by an AWS SDK issue #2070. The AWS SDK issue was discovered and reported to the AWS SDK GitHub repository site on August 5th, 2019. AWS ac...
Since the 4.18 release, we have customers in three categories:
Customers who have upgraded to 4.18 - Patch 3, no action required.
Customers who have upgraded to 4.18 GA, 4.18 Patch 1, or 4.18 Patch 2, we recommend that these customers migrate to the...
We understand that this is not optimal. We will look for a way to generically support obfuscation for types of use cases that leverage REST Snap. Thanks!
For a=foo and b=bar, if you do:
$a + ‘\n’ + $b
Result in json should be:
[{“output”:“foo\nbar”}]
Depending on your target system and how it renders newlines, that should work.