At SnapLogic, we follow an Agile development process to allow us to provide features to you sooner. As a result, the code and the documentation may not always be in sync. We try our best to have quality documentation with each release, but it is hard worksometimes there might be a lag.
|Documentation for Snaps only covers those Snaps developed by SnapLogic that are generally available. Documentation for Private Snaps (those Snaps developed or modified for a single customer) will not be made available on our documentation site. Third-party developers that create Snaps are responsible for hosting any documentation for of those Snaps.|
documentation onMobile Devices
As our documentation site is a uses Confluence siteCloud, it will have the same behaviors and limitations as other Confluence sites viewed on mobile devices. See the Confluence Mobile documentation for more information.Contributing to
Cross functional collaboration on SnapLogic Documentation
We want our documentation to be a collaborative process between our teams and our customers. Our Doc documentation team works collaborates with our engineers during engineers and product managers during the development process to gather information on how each feature works and together, they to create the documentation. Input from our field and support teams cross functional teams like support and field is also incorporated to provide a more user-focused perspective.
We want to hear from you
Do you have tips or tricks that you think other users would benefit from? Do you have a detailed use case that won't fit in the feedback mechanism that you would like to see added? Send Send an email to firstname.lastname@example.org.
SnapLogic, Inc. | 1825 S. Grant St 5th Floor | San Mateo CA 94402 | USA