...
...
...
...
...
...
...
...
...
...
| Info |
|---|
The content from this topic has been migrated to various sections in the new documentation site. For the most |
...
accurate and latest information, |
...
please refer to the relevant sections in the new documentation site linked below. |
In this article
| Table of Contents | ||
|---|---|---|
|
...
You can update Snaplex instances within an Org automatically by selecting the checkbox on Manager > Settings > Auto Upgrade Snaplex. This setting updates the Snaplex to the latest available version.
Upgrade Rules
| Info |
|---|
This content has been migrated to theSnaplex and Snap Pack compatibility section in the new documentation site. |
This new release process allows the following combinations:
...
Impact on your SnapLogic instance during the release window
| Info |
|---|
This content has been migrated to theSnapLogic release updates section in the new documentation site. |
The release update has zero downtime for the SnapLogic platform during the quarterly release. This implementation means that there is no maintenance notice on the SnapLogic UI. You can continue accessing the UI during the maintenance window and make updates. Your Pipelines, API calls, and Scheduled Tasks will operate normally.
...
Grace Period for Upgrades
| Info |
|---|
This content has been migrated to theManage Snap Pack version section in the new documentation site. |
Snaplex and Snap Pack upgrades automatically occur four weeks plus two days after a quarterly release. Older Snaplex nodes and Snap Packs are automatically updated, and Snaplex rollbacks are not allowed. Warning messages are provided well before the grace period ends.
...
| Note |
|---|
|
To upgrade automatically to the latest available version, select the checkbox in Manager > Settings > Auto Upgrade Snaplex.
Snap Pack Configuration Options
| Info |
|---|
This content has been migrated to theSnap Packs section in the new documentation site. |
The options you set on the Manager > Snap Pack page control which Snap Packs are used when Pipelines run. As an Org administrator, you can choose the options that work best for your Org or project. For example, you might configure a developer Org to always have the Latest Snap Packs to test new features. But for a production Org, you might choose Stable Snap Packs to make sure everything works as expected.
...
Snaplex Options | Org Options | Snap Used |
|---|---|---|
New | Latest | Kafka 275 |
Stable | Kafka 273 | |
Old | Latest | Kafka 271 |
Stable | Kafka 270 |
Local Overrides
| Info |
|---|
This content has been migrated to theManage Snap Pack versions section in the new documentation site. |
In addition to the menu choices (Latest/Stable, Old/New), you can also configure individual Snap Pack local overrides to use when a Pipeline runs. For example, you might have a Stable set of Snap Packs configured for your Org, but you can select a later (or earlier) version for a few of the Snap Packs, depending on your needs. 
...
Recommended Upgrade Process for an Org
| Info |
|---|
This content has been migrated to theTest new releases section in the new documentation site. |
When a quarterly release occurs, follow these steps to test the new Snaplex and Snap Packs:
...
Either validate or execute a Pipeline in the given Org where you have upgraded a Snap Pack.
Click the Check Pipeline Statistics
icon to open the Pipeline Validation Statistics screen.Hover over a Snap row—notice the associated Snap build number on the right bottom of the following image.
Rollbacks
| Info |
|---|
This content has been migrated to theDowngrade a Snaplex section in the new documentation site. |
During the grace period, you might need to downgrade a Snaplex or Snap Pack because of compatibility issues, platform restrictions, and so on. In this case, you can rollback a Snaplex. Change the Snaplex version to an older version in the Manager.
...