Import Process

Before the import starts, the system revalidates all of the objects in the package. The revalidation allows the system to make sure that it is always using the most current snapshot of what is contained within the system.

The revalidation is important if a package is uploaded several days before it is imported. During this lag time, anything can happen. For example, objects that are identified as new within a package could be manually created or imported as part of a different package. This could cause much confusion if the Import process tries to recreate the same object. The revalidation is one of the most important stages of the entire process.

Note: The import validation is the same process that can be triggered manually by the user.

After the revalidation, if any errors are encountered, the import stops and the package status changes to Import Failed.

If no errors occur, the process imports the objects in the following order:

Content
Document
Form Style
Budget Token
Record Data for UOM_Type and UOM_Values
Module
Business Object
Form
Record Data (excluding UOM_Type and UOM_Values)
UX components (Application, Web Component, and related UX metadata)
Hierarchy Structure
Query
Workflow
Navigation Collection
Navigation Item
Group
Portal
Portal Section
List

To help resolve any circular dependencies/references, the system automatically imports the package two times. After each pass, the system refreshes all system caches on the environment in which the import is being performed. If there are other running process servers or application servers, the caches on those systems should be manually refreshed.

During import, if an Application or Web Component object exists in the target environment, a revision of the object is created in the target environment. To prepare a clean target, all UX metadata that is related to the specific Application or Web Component object in the target environment, but is not included in the import package, is deleted.