Snap Packs Org Level

This document provides an overview of the Snap Pack Org


This article explains how and when to set the version of a Snap Pack for your Org. For a detailed description of the upgrade process and SnapLogic Platform updates refer to SnapLogic Release Process .

Org Level Distribution

The Snap Packs provide an Org-wide setting that controls which Snaps are used.

You can configure the Snap Pack to use one of the following distributions:
  • Stable: Snap Packs that have been tested over a few releases. This distribution is usually updated quarterly, along with the Snaplex upgrade.
  • Latest: New Snap Pack builds are made available when updates are made.
Important: We recommend that you use the Stable version of the Snap Pack by default for your Production Orgs. You can use Development Orgs to test new Snap Packs features in the Latest distribution.

Snap Pack Overrides

You can apply version overrides for the Snap Pack versions. The version override applies to the distribution as chosen for the Org. You should apply version overrides in consultation with SnapLogic Support. Running older Snap Pack builds on the latest platform version is supported, but running new Snap Pack builds on the older platform version is not supported.

Pipeline Executions

When executing a Pipeline, the version of Snaps that are used depends on which version of the platform the Snaplex nodes are running. If the Snaplex node is running the current platform version, then new Snaps are used. If the Snaplex node is running the older platform version, then the older Snaps are used.
  1. Drag any Snap on the canvas in Designer, then click the Snap. The Snap Settings dialog appears.
  2. Click the Info tab and see the Class FQID (the unique Snap identifier). The Snap Pack version is appended to the identifier.
Important: To avoid issues with the Snap Pack version in the Catalog being different from the Snap Pack version during execution, we recommend that all Snaplex instances in the Org are upgraded to the new Platform version simultaneously. This simultaneous upgrade causes the Snap Catalog to use the new versions, and subsequently the version used in the Catalog matches with the version used during Pipeline execution.