In this Page
This article provides an understanding of how and when to set the version of a Snap Pack for your Org. See SnapLogic Release Process for a detailed-description of the upgrade process and SnapLogic Platform updates.
Org Level Distribution
The Update All Snap Packs for org menu provides an Org-wide setting that controls which Snaps are used.
You can configure each Org to use one of these two Snap Pack distributions:
- Stable: This distribution is usually updated quarterly, along with the platform upgrade. Production Orgs should use the Stable distribution.
- Latest: New Snap Pack builds are made available under Latest distribution as and when fixes are published. Development Orgs should use the Latest distribution.
Snap Pack Overrides
You can apply version overrides for 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 older platform version is not supported.
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.
To check which version of Snaps are used during Pipeline execution:
- Drag any Snap on the canvas in Designer, then click the Snap. The Snap Settings dialog appears.
- Click the Info tab and see the Class FQID (the unique Snap identifier). The Snap Pack version if appended to the identifier.
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.