Snap Packs (project level)

The Snap Packs page in a project lists the Snap Packs explicitly added to that project. Snap Packs added to the shared project are accessible to all users, and those added to another project are only available in that project.

Hover over the Snap Pack name to access the context menu. From there, you have access to view the Snap Pack's Activity log to view when it was created or modified.

Behavior change

In versions before 4.33, Snaps from a Custom Snap Pack uploaded to a Project, the Project shared folder, or the Global shared folder were accessible in the Project. However, the latest update has modified this behavior. Now, when you upload a Snap Pack to the project space containing Snaps different from those uploaded to a shared folder, only the Snaps directly uploaded to the Project will be visible. Refer to the example below for a better understanding of the behavior change.

Your existing pipelines utilizing Snap Packs might no longer be accessible because of this update and will require fixing. To resolve this issue, ensure that you upload the required Snaps directly to your Project folder for the Pipelines to function as expected.

Custom Snap Packs

You can upload Custom Snap Packs to the following folders:

  • Project folder in project space: When working on a project, you can create a specific folder dedicated to that project. This folder is located in a designated area called the project space.
  • Shared folder in project space: In the project space, you can have a folder shared among multiple users working on the project. It allows those users to access and collaborate on the files in that folder.
  • Global shared folder: This refers to a shared folder across different projects or spaces. It is accessible to users in various projects.

For each Custom Snap Pack, SnapLogic looks for it in the following locations, in order, and stops at the first match: the Project where the pipeline is located, then a Project space shared folder, then the environment-level Global shared folder. If a Snap Pack exists in the Project, a pipeline there only sees that Project's copy of it — Snaps from the same Snap Pack uploaded elsewhere aren't visible. If the Snap Pack doesn't exist in the Project, the pipeline falls back to the Project space shared folder, then the Global shared folder. Refer to the examples below for a better understanding.

Snap visibility examples

Most scenarios can be categorized in the examples mentioned below when creating pipelines and determining the visibility of the Snap Packs.

Example 1

If you have Snap Pack A and B uploaded to the following locations,

  • Global shared: Snap Pack A (Snap A-1, Snap A-2)
  • project space shared: Snap Pack B (Snap B-1, Snap B-2)
  • Project: Snap Pack B (Snap B-1, Snap B-3)

The visible Snaps in the Project folder are Snap A-1, Snap A-2, Snap B-1, and Snap B-3 (Snap B-2 isn't visible because it isn't uploaded to the Project).

The visible Snaps in the project space shared folder are Snap A-1, Snap A-2, Snap B-1, and Snap B-2.

The visible Snaps in the Global shared folder are Snap A-1 and Snap A-2

Example 2

If you have Snap Pack B uploaded to the following locations.

  • Global shared: Snap Pack B (Snap B-0, Snap B-1)
  • project space shared: Snap Pack B (Snap B-1, Snap B-2)
  • Project: Snap Pack B (Snap B-1, Snap B-3)

The visible Snaps in the Project folder are Snap B-1, and Snap B-3.

The visible Snaps in the project space shared folder are Snap B-1, and Snap B-2.

The visible Snaps in the Global shared folder are Snap B-0 and Snap B-1.

Example 3

If you have Snap Pack A and B uploaded to the following locations.

  • Global shared: Snap Pack B (Snap B-0, Snap B-1)
  • project space shared: Snap Pack B (Snap B-1, Snap B-2)
  • Project: Snap Pack A (Snap A-1, Snap A-2)

The visible Snaps in the Project folder are Snap A-1, Snap A-2, Snap B-1, and Snap B-2.

The visible Snaps in the project space shared folder are Snap B-1, and Snap B-2.

The visible Snaps in the Global Shared folder are Snap B-0 and Snap B-1