Rolling Out Advanced Team Packages

The method in which advanced team packages are rolled out to end users varies depending on the delegation policy settings. One thing that always remains the same is that principal package changes always flow to associated secondary packages without affecting team-specific secondary package configurations.

In this tutorial, you will learn how to:

  • Promote principal packages
  • Promote secondary packages

Duration Time: 10 Minutes

Start Tutorial Now

Don't have SDC? Download Now

1. Promoting a Principal Package

Two Delegation policy options control how packages are promoted - Promote Packages and Auto-Promote Secondary Packages.

First, when promoting principal package changes, you can simultaneously promote associated secondary packages by enabling the Auto-Promote Secondary Packages option. A toggle appears on the Promote window allowing you to build installers as well.

Note: If you auto-promote secondary packages along with a primary package, committed changes made by the secondary package's group admin will also be promoted.

Second, use the Delegation policy to indicate if you want to allow group admins the ability to promote secondary packages. With the Promote Packages option disabled, the central admin must promote changes made to secondary packages.

promotion_settings
Delegation policy settings related to package promotion

Central administrators create, maintain, and promote principal packages. Promoting a principal package rolls changes to its associated secondary packages. Rolling out to the secondary packages can be automated or require a manual promotion of secondary packages depending on the selection in the Delegation policy.

Note: Workspace tasks provided to a secondary package by a principal package can be overridden by secondary package workspace task changes.

  1. Commit changes to the principal package.
  2. Select Promotable Changes in the Notifications area, and select the principal package you want to promote.
    promote_page
    Selecting principal package to promote
  3. Click Promote Changes.
  4. Enter a promotion comment. If the package's Delegation policy has Auto-Promote Secondary Packages disabled, simply click OK. Only the principal package is promoted.
    promote_no_build
    Promote window when Auto-Promote Secondary Packages is disabledIf the Auto-Promote Secondary Packages option is enabled, you have the option to build installers for the principal package and its associated secondary packages.

    promote_with_build
    Promote window when Auto-Promote Secondary Packages is enabled
  5. If you want to build installers, change the toggle to Yes, and click OK. Regardless of your installer build selection, the secondary packages are promoted along with the principal package.

2. Promoting Secondary Packages

Changes made to secondary packages can be committed and promoted at any time. If the associated principal package's Delegation policy allows, group admins can perform the steps below. However, if the policy does not allow group admins to promote secondary packages, this task must be done by a central admin.

If the Delegation policy of the principal package is enabled for auto-promotion of secondary packages, the packages will be promoted along with the primary package. In this case, local uncommitted changes made by group admins will be lost.

  1. Commit changes to the secondary package.
  2. Select Promotable Changes in the Notifications area, and select the secondary package you want to promote.
    promote_page2
    Selecting secondary package to promote
  3. Click Promote Changes.
  4. Enter a promotion comment.
    promote_secondary
    Promote window
  5. If you want to build installers, change the toggle to Yes, and click OK. Changes are promoted and rolled out to end users.