ContributionsMost RecentMost LikesSolutionsLaunched: Native SnapLogic API Management 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.g. rate limiting and IP restriction), and other API Management concepts like generating swagger documentation, REST to SOAP, and API facade. With a single platform, ease of use for configuration, management, and deployment provides a seamless experience for your APIM and integration needs. Snaplogic August 2020 Release 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 be made available during this first UAT push. The release is currently scheduled for deployment to production on Saturday, August 8th, 2020 at 9:00 PM PT / Sunday, August 9th at 4:00 AM GMT. Join our product team for a UAT webinar on Wednesday, July 29 at 9:00 AM PT / 4:00 PM GMT as we walk through new features and enhancements. Please register here. The release schedule is planned as follows: Friday, July 24, 11:00 AM PT Release to UAT Wednesday, July 29, 9:00 AM PT Register for UAT Webinar Friday, July 31, 11:00 AM PT UAT Update Saturday, August 8, 9:00 PM PT August 2020 release to production (Up to 1-hour planned downtime) Saturday, September 12, 9:00 PM PT Update of remaining Snaplexes to August 2020 release A follow up communication will be sent on Friday, July 24th with more details on new features and enhancements. Stay tuned. Lastly, contact us directly if you have questions about the release at support@snaplogic.com. Thank you! SnapLogic Product Team Please Update: Highly Recommended Patch for SnapLogic May 2020 (4.21) 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 recommend that you apply this build to your Snaplexes as soon as possible. For release notes on patch please review patch release documentation. The steps to apply this patch are available in our documentation: As an Org admin, log in to the SnapLogic Manager. Navigate to the Snaplex list in the Shared Project. Select a Snaplex and open the Update panel. In the Update panel, select the latest recommended patch from the Version drop-down, then click Update. Repeat the above procedure for each Snaplex you want to update. Please contact us directly if you have questions about this update at support@snaplogic.com. Thank you! SnapLogic Product Team Re: RESOLVED [Potential Regression]: Pipeline Impacting Issue All outstanding patches have been deployed and this issue is now closed. If you have Snaps that are impacted please update to the latest version. RESOLVED [Potential Regression]: Pipeline Impacting Issue 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 acknowledged the regression and committed a fix on August 7th and included in build 1.11.610. The issue #2070 affects all SnapLogic customers that use AWS related Snaps that have HTTP or HTTPS proxy configured without a username and/or password. Impacted Snap Packs Binary Redshift Hadoop Snowflake Details of Impact The problem affected any SnapLogic customers that leveraged AWS functionality whose Snaplex had either a system configuration that used an unauthenticated HTTP/HTTP proxy, or who had the same defined via Environment Variables. If a proxy was not used, or a proxy username and password was used, then customers were not affected. Solution To fix this, we are upgrading our dependency versions and will release new versions of the Snap Packs affected. This effort is currently undergoing QA review. When review is complete, we will send a follow up communication confirming that new versions are ready to be applied. Please contact us directly if you have questions about this at support@snaplogic.com. Thank you! SnapLogic Product Team Important for all customers: 4.18 Mandatory Snaplex Upgrade and Snaplex Patch 3 Notice 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 Patch 3 version of the build - master-5912 - 4.18 Patch 3 (Recommended) Customers who are still on 4.17 Snaplex version (on any patch) on September 14th will receive the forced update and no action will be required. For additional details about the forced update, please see the note below that was distributed to Org Admin’s last week. The SnapLogic August 2019 (4.18) release was deployed and has been GA on production since August 10th, 2019. We provide customers the flexibility to plan and update their Snaplex nodes in a 5 week window, accommodating their organization’s requirements the best. For the 4.18 release, customers have up until Saturday, September 14, 2019 (9:00 PM PT) to update their Snaplexes, after which SnapLogic will execute a forced update of all Snaplexes to the latest recommended version (currently master-5912 4.18 Patch 3). The steps to apply this patch are available in our documentation: As an Org admin, log in to the SnapLogic Manager. Navigate to the Snaplex list in the Shared Project. Select a Snaplex and open the Update panel. In the Update panel, select the latest recommended patch from the Version drop-down, then click Update. Repeat the above procedure for each Snaplex you want to update. Please contact us directly if you have questions about this update at support@snaplogic.com. Thank you! SnapLogic Product Team Re: Rest API Snap Issue: Too Many Request What is the error? Re: Changing snaplex of a task using api or any automated process You should be able to use the metadata snap to read tasks and then update the snaplex name/path. Re: Connecting to Marketo with the REST Snap Pack 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! Re: Append string to a new line 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.