In this article

Overview

Snap Pack versions are independent of Snaplex versions. As an Org admin, you can keep track of the version for your Snap Packs in Manager using the Snap Packs, as well as your Snaplex Versions.

You should consider the following when tracking Snap Pack versions:

• Design time

• Execution time

Design Time

Design time consists of Pipeline development activity. Usually, the Pipeline designer manually executes the Pipeline from SnapLogic Designer to test it.

Pipeline designers should be aware of the following factors during pipeline design:

• Since the Snaplex on which the pipeline run is unknown, an Org-level Snap Catalog is used. This Snap Catalog controls the Snaps that SnapLogic Designer displays and the properties that are displayed in those Snaps.

• The design-time Snap Catalog uses old Snap Pack versions if there is any Snaplex in the Org on an older Snaplex version (which is the version of the platform).

• If all Snaplexes are on the newer Snaplex version, the latest Snap Pack versions are used.

Execution Time

Execution time consists of Pipeline executions that are the result of Task invocation. During Pipeline execution, the Snaps used depends on the Pipeline location and the Snaplex version.

• If the project containing the Pipeline has private Snap Packs, then those Snap Pack versions are used. Otherwise, the Snap Pack corresponding to the Snap distribution is used.

• If the JCC node is on the new Snaplex version, the new Snap Pack versions are used.

• If the JCC node is on a previous Snaplex version, then the previous versions of the Snap Packs are used.

Order of Snap Version Reference

1. The private Snap Pack version in a Project where the Pipeline is located.

2. The private Snap Pack version in a Project space shared folder

3. The private Snap Pack version in Org-level global shared folder

4. The Snap version configured in the distribution (stable/latest) used by the Org. The Org-level version overrides are applied here.

A private Snap Pack version always takes higher precedence over the configured Org-level Snap Pack.

Snaplex Versions and Snap Packs

During the five-week window for Snaplex auto-upgrade, Snaplexes could be in one of three states.

• All Snaplexes are on the previous Platform version--->Design-time Snap catalog uses old Snaps

• Mixed versioned Snaplexes include some Snaplexes that are on the previous Platform version and some that are running on a new version--->Design-time Snap Pack Catalog uses old snaps

• All Snaplexes on new platform version--->Design-time Snap Pack catalog uses new snaps

Until all Snaplexes are upgraded to the new version, the design-time Snap Pack Catalog will use the old Snap Pack Catalog. If one Snaplex is switched back to the previous Snaplex version after the upgrade, the catalog again reverts to the previous version.

However, the execution time Snap Pack Catalog does not have this behavior. Rather, new Snap Pack versions are used on new JCC nodes and the previous versioned Snaps are used on the old JCC nodes with the previous version.