Creating a Deployment Package

You can create a deployment package that contains deployment extensions and unique keys.

Important:
  • In this release, a deployment package cannot mix up WIP and Governance app types. If you first select a WIP type, your package can only contain WIP types. To identify the types contained in a package, see Customize: 3DEXPERIENCE Platform: 3DSpace Data Model: Unified Typing Reference Dictionary. Seeing PLMEntity or PLMCoreInstance in a package's inheritance path means that the package contains WIP types. If none is mentioned, the package contains Governance types.
  • Deployment Packages names shall contain alphanumeric characters and the "_" character only.
  • After creating a deployment package, you must deploy it and update the index specification.

See Also
Creating and Deleting a Deployment Extension
Deploying a Package
Updating the Package Index
  1. From the Compass, click Social and Collaborative Apps , Data Model Customization, and select Administrate Data Model.
  2. In the List of Deployment Packages window, click New .
    1. Enter the package name in the Name box
    2. Enter the prefix in the Prefix box. You can enter a new prefix or select one from the scrolling list.

      To avoid attributing existing names, a prefix is automatically added to all objects: packages, types, extensions, attributes, and uniqueness keys. The prefix is stored within each package and is automatically added to the object at deployment. A prefix must start with a letter, and be made up at least of three alphanumeric characters (including underscore).

    3. Optional: add a comment in the Comment box.
    4. Click Done to close the window.

The new package appears in the list.

Notes:
  • The Name column displays the DS Parent Package specialized by the current package.
  • The Deployed column indicates if the package is deployed (yes), not deployed (no) or partially deployed (partial). Partially deployed means that the package has already been deployed but one of its objects was modified and the package was not deployed again after modification.
  • The Prefix column displays the prefix used for the package and the associated objects. The list of already used prefixes appears in the scrolling list allowing you to select an existing prefix.
  • The Comment column shows the comments (if any) related to the package.
  • The Creation Date column indicates the date the package was created.

After creating your package and the related extensions, you must:
  1. Deploy it so that the objects contained in the package can be used.
  2. Update the index specification.