In earlier Designer versions, packages had to be imported into the project catalog before they were used. In this release, importing packages manually is no longer required. The auto-import feature handles the importing of the required packages as required.
All packages in Designer are available for package operations without having to import the packages manually. For example, when you install or upgrade a package, it is automatically imported.
Earlier an option to import all packages was displayed on opening a project to limit multiple manual package imports to a one time activity. Now, this option is no longer displayed. With the Dynamic Auto-import of Packages feature, you need not import packages manually.
Importing all packages into a project results in a large memory footprint and large project size on the disk, which in turn results in performance issues.Now Designer provides you the option of removing unused packages that you don't use.Please take a look at Remove Unused Packages from the catalog feature.
The following figures illustrates a package install operation without importing the package into the project's package catalog.
If you have many packages imported into the project catalog and you want to clean up the project, Designer provides the Remove Unused Packages option to perform this operation. When you right-click on the package catalog and category folders, and select the Remove Unused Packages option from the menu, all packages that are not installed on any Driver, Driver-set, or Identity Vault are automatically detected and removed from the project. You can re-import the removed packages. Right-click the package catalog and select Import Package...
To have a better control over package versions, the package version now has 4 parts; that is, (x.x.x.xxxx) Major + Minor + Revision + Build-Id. The newly added build-Id is a time stamp that represents the package build time in yyyyMMddHHmmss format.
With this change, you can create new package version without changing the three part version(Major + Minor + Revision ) for every modification. This results in controlled version number changes for package releasing process.
Previous packages (packages that do not have build-Id) would still show three part version numbers where the build-Id is taken as zero . For package operations , build-Id is considered for determining the higher and lower version if both the versions have same three part version number.
When you open a policy after configuring the driver packages, a dialog box is displayed. The dialog box displays a prompt that the policy object that is being edited is provided by a specific package and any changes made to the policy might result in the object being marked as customized. To avoid the dialog box from being displayed repeatedly each time a package based policy is opened, a new preference option has been added that allows the user to choose not to display this prompt when opening package based policies.