This page will display a list of packages defined in the platform. Packages represent a logical bundle of configuration items that can be migrated from a source environment to a destination once configuration has been completed and tested.
This page can be accessed from the Configuration workbench. From the menu, select 'Configuration' under the 'Administration' section. This will open the configuration workbench.
From the configuration workbench select Packages from the Migrations section.
The packages dashboard lists packages for a specific environment.
From the Select Environment filter select an environment to view all the packages in that environment. Choose the local environment from the list to view packages in the the current environment.
Click on the ‘+’ sign in this page to create a new package. The will open the Package Details page.
If there is no +' sign then either the user does not have the authority to create a package
Click on an existing package to view the Package Details page.
Click on an existing package to view the Package Details page. From this page it is possible to make updates to the package.
Packages cannot be deleted. If the package should not be used any further then the title can be renamed to reflect this if required.
It is possible to copy a package from a different environment into the current one. This scenario is useful if needing to migrate from more than 2 environments, for example from Development to Test to Production. In such a scenario, the package would be created in Development and then migrated to Test. Once testing is complete a package needs to be created in Test so that it can be migrated to production.
Prior to copying the package from the source to the target, the package should already have been migrated to the target so that the underlying configuration exists in the target.
In this dashboard, select the source environment to show all the packages in that environment.
From the results list click on the 'right-hand' drill-down arrow to view the Package Details page
On the details page, click on Copy Package to create a package in the local environment as a replica of the one in the source.
Q: If I update configuration items after they have been added to the package, does the package automatically migrate the most recent version?
A: No. The package will contain the version of the configuration item as it was when it was created. If the configuration is subsequently updated and the package should be updated to the latest version then open the Package Details page and click on Latest Versions. This will update the package with the most recent version of all the configuration items. It is recommended to also click on Add New Dependencies (also on the Package Details page). This will ensure that any dependencies created during the change in configuration are also added to the package.