Managing Secondary Packages

With the Advanced Team Delegation features of SDC, administrators can split package administration responsibilities with team leads. This method of administration uses special packages called principal and secondary packages. Before beginning this tutorial, familiarize yourself with the Advanced Team Delegation concepts.

In this tutorial, you will learn how to:

  • Create a secondary package
  • Migrate a standalone package to a secondary package
  • Convert a secondary package to a standalone
  • Associate a secondary with a different principal package

Duration Time: 10 Minutes

Start Tutorial Now

Don't have SDC? Download Now

1. Creating a Secondary Package

A secondary package is based on the selected principal package. Updates to the associated principal package trickle down to its secondary packages. You can create a new secondary package, or associate an existing standalone package with a principal package to create a secondary package.

To create a new secondary package, you must first have at least one principal package available.

  1. Click Team Packages in the Admin Console navigation.
    opening_team_packages
    Opening the Team Packages page
  2. In the Principal Packages area, select the principal package from which you want to create the secondary package.
    selecting_principal2
    Selecting a principal package
  3. Click addIcon in the Secondary Packages area.
  4. Enter a title for the package. This title will be displayed on the portal web page. Choose one or more delivery groups for the package. If you don't select a group during package creation, you can assign one or more groups on the package's Configuration tab. Click Next.
    creating_secondary
    Naming the new package
  5. Commit and promote the package. The package is now available for customization by the group admin of the associated groups.

2. Migrating a Standalone to a Secondary Package

You can link existing standalone packages to a principal package to create a secondary package.

  1. Click Team Packages in the Admin Console navigation.
    opening_team_packages
    Opening the Team Packages page
  2. In the Principal Packages area, select the principal package from which you want to create the secondary package.
    selecting_principal
    Selecting a principal package
  3. In the Secondary Packages area, click migrate_to_secondary_icon.
    migrate_to_secondary
    Converting a standalone package to a secondary package
  4. Select the standalone package(s) you want to link to the selected principal package, and click OK. The package appears in the Secondary Packages area of the Team Packages page.
    selecting_standalone
    Selecting standalone packages to convert
  5. Commit and promote the package. The package is now available for customization by the group admin of the associated groups.

3. Converting a Secondary Package to a Standalone

If you no longer want to a secondary package linked to a principal package, you can convert it to a standalone.

  1. Click Team Packages in the Admin Console navigation.
    opening_team_packages
    Opening the Team Packages page
  2. Select the package, and click convert_secondary_icon. The package is removed from the Team Packages page and is converted to a standalone package.

4. Associating a Secondary with a Different Principal Package

At times, you might need to change the principal package to which a secondary is associated with, if you are removing a principal package, for example.

  1. Click Team Packages in the Admin Console navigation.
    opening_team_packages
    Opening the Team Packages page
  2. Select the secondary package.
  3. Click change_principal_icon.
  4. Select a new principal package, and click OK.
    switch_principal
    Selecting a new principal package