Exporting and Importing Specializations

You can export all the specialization elements you have created in a .zip file and import into Enterprise IP Schema Specialization .zip files that contain specialization elements.

These features allow you to create and test your specializations in a development environment and then import them in a production environment. For more information, see Main Workflow.

This task shows you how to:

See Also
Tiles Locks
Creating, Editing, and Deleting Types
Creating and Deleting Attributes Groups
Creating, Editing, and Deleting Extensions
Creating, Editing, and Deleting Attributes

Export Specializations

Before you begin: You must have created at least one type, attributes group, or extension.
  1. From the navigation menu, click Tools.
  2. From the Schema Specialization section, click Export.

  • The .zip file is downloaded to your computer. It contains a .json file that includes:
    • All the specializations.
      Note: To make sure that everything that you have tested and validated as a whole is correctly exported, Enterprise IP Schema Specialization exports all specialization elements at once. You cannot limit the export to the specialization elements of your choice.
    • The code level.
    • The environment of the Enterprise IP Schema Specialization widget that generated the .zip (development or production).
    Important: Do not try to modify the .json file. As it is protected against modifications, trying to import a file you have modified will always fail.
  • If the Enterprise IP Schema Specialization widget that generated the .zip file is in the development environment, an orange lock is added to the tiles of all the elements that have been exported.

Import Specializations

Before you begin: You must have a .zip file that was generated by exporting specializations from a Enterprise IP Schema Specialization application. For more information, see Export Specializations above.
  1. From the navigation menu, click Tools.
  2. From the Schema Specialization section, click Browse and select the .zip file you want to import.
  3. Click .

  • All specialization elements contained in the .zip's .json file are imported into Enterprise IP Schema Specialization if the import complies with the following rules:
    • The import does not impact any existing data (Business Objects, Connections).
    • The .zip's .json file has not been modified.

    If theses rules are not met, the whole import operation stops. Enterprise IP Schema Specialization only either imports all the specializations contained in the .zip file at once or none. Enterprise IP Schema Specialization does not limit the import to the complying specializations and you cannot limit the import to the specialization elements of your choice.

  • Enterprise IP Schema Specialization automatically updates the index specification when the .zip is imported.
  • If the Enterprise IP Schema Specialization widget you have imported the specializations into is in a development environment, a lock is added to the tiles of all the elements that have been imported as follows:
    Environment of the Enterprise IP Schema Specialization Widget that Generated the .zip Lock Color
    Production Red
    Development Orange
Notes:
  • If you import a .zip file that contains a specialization element that you had deleted from your data model, this specialization element will be reintroduced into your data model. You must delete it manually again.
  • Imports never delete specialization elements. For example, if you:
    1. Create 2 types; T1 and T2 in a development environment.
    2. Export these specializations in a .zip file.
    3. Import the .zip file into the production environment: Both types are imported.
    4. Delete the T1 type from the development environment.
    5. Export the specialization in a .zip file: the export file only contains T2.
    6. Import the .zip file into production: T1 remains in production. You must delete it manually (provided that it has never been used to create objects).
  • The lists of authorized values, if any, of imported attributes may appear in a different order on Enterprise IP Schema Specialization and on end-user apps. You cannot control this order.