Deploying a Specialization Package

After creating your package and the related extensions, you must deploy it so that the objects contained in the package can be used. The deployment updates the administration vault by importing the content of the selected packages. You can deploy several packages in the administrative vault at the same time. This vault is updated with the changes made in the source package. It means a package can be deployed several times. To be taken into account by the applications, every change must be deployed.

Each object has a computed deployed status:

  • Not deployed: The object has never been deployed.
  • Deployed: The object is fully deployed.
  • Partially deployed: The object has been deployed at least once but its definition has been changed afterwards.
Notes:
  • An attribute is considered as deployed if its characteristics are deployed: name, type, dimension (if any), preferred unit (if applicable), default value, user access mode, reset on cloning mode.
  • An extension is considered as deployed if its attributes, its description, and abstract/concrete status are deployed.
  • A package is considered as deployed if its extensions and unique keys are deployed.
  • Deploying a package does not update the index specification. To update the index specification, see link in the See Also section of this page.

See Also
Creating a Specialization Package
Updating the Index Specification
  1. From the List of Specialization Packages window, select the check box of the package you want to deploy.
  2. Click Deploy Package(s) .
  3. Click OK to update the administration vault.

    Warning: You cannot undo this command.

The package is deployed.

You may need to update the index specification for content to be available in web apps. For more information, see link in the See Also section of this page.