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.
I previously wrote about integrating with the DocuSign eSignature API with the REST Snap Pack and OAuth 2.0 authentication, but for those that wish to control their access a bit more, DocuSign supports authenticating with JSON Web Tokens (JWTs) too.
...
HTTP-compatible Snap Packs can leverage an HTTP proxy configured in the Snaplex’s Network Proxies configuration tab within the SnapLogic Manager web application.
However, the Script Snap is different because you can write Scripts to call external pro...
In order for SnapLogic’s Snaplex application to be able to read and write data to your Amazon Redshift cluster, we need allow external connection from the SnapLogic IP addresses for inbound access.
Open the Clusters page within the Amazon Redshift co...
DocuSign’s latest REST API version is 2.1 and also supports OAuth 2.0 authentication (replacing the legacy X-DocuSign-Authentication header-based auth).
DocuSign also provides free (no credit card neccessary) developer accounts to try out their API.
...
Platform Release Notes
Security Enhancements
Password requirements enhanced to included minimum characters, restricted items, and complexity. See Changing Your Password for details of the new password requirements.User Session Timeout Policy added to...
Netsuite + OAuth 2.0
@johnnys I created an Integration in Netsuite (Setup > Integration > Manage Integrations), enabled REST Web Services and Auth Code Grant under OAuth section and entered in the SnapLogic REST Callback URL (https://elastic.snaplogi...
Is there a way to just flatten the KSSK elements and ignore the V_Fleet ones ?
You can delete the V_FLEET entry in the JSON Splitter’s “Include Paths” setting and then update the rest of the pipeline where those fields were being referenced.