Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Concept (Imports)

All projects which have been exported using the “Manage Exports” process can be imported using the “Manage Imports” process.

Tip: The “Manage Imports” step allows importing all or a part of the data related to a specific workspace and/or a specific project.

When receiving project data from another environment, it is not infrequent to see that these projects have been created in another workspace.

Tip: As of release 8.0, the missing workspaces can be automatically created

Moreover, it is possible that some objects in the export file contain structural links to object that are not a part of the export file. In this case, the Designer will force the creation of objects having the same name.

Tip: The Designer avoids model corruption by creating forced objects.

Forced objects can be unforced either by changing their forced status in the objects dictionary, by “mass unforcing” them in the objects dictionary or by modifying their settings (description, etc.).

Forced objects are created with a validity date forced to 01/01/1900. It guarantees their invalidity and ensure these objects to not be displayed at runtime.

Warning: The capability to import objects of the file into another workspace is not currently supported for Excel-based imports.

For information on how to perform imports, please see Executing Imports.

Additional information can be found in Understanding Excel-based Exports & Imports.