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.

Show Page Sections

Concept (Exports)

All projects, all underlying objects, all basic data and all business rules which have been created in the

Designer can be exported to an XML/Excel file using a dedicated format.

The ultimate goal of this export is to provide an XML or Excel representation which can be used:

  • As a backup of data
  • As a means to exchange data between people modeling in on different servers
  • As a way to exchange data with PROS Software Customer Services
    Tip: It is recommended to use the XML format for automated data exchange / batch processes.

    The Excel format can be used for manual massive data import/export as it is more ‘readable’.

The export feature is “version-oriented”, meaning that all objects from all workspaces may be exported.

Exports can be done in 2 ways: incrementally or full.

Definition:

A full export will contain the complete image of the version (or fix), including items which have been created or modified in previous versions but which have not been modified in the version to be exported.

This export mode has 2 variants:

  • All objects in all workspaces (full)
    • The resulting file contains a full export of the modeling environment and this mode is faster than the filtered export
  • Only a subset of objects (full filtered)
    • The meta-modeling Processes that can be selected in the ‘Select Content’ step are part of from the current workspace (selected in the Dashboard)
    • The resulting file contains a full export of all objects of interest (as well as their dependencies) but this mode is slower.

Definition:

An incremental (or delta) export will contain only the differences between the exported version (or fix) and the previous version (or fix).

This export mode contains all modified objects in all workspaces. This mode has a small footprint and is fast.

Tip: In the context of an automatic distribution process, all exports are done incrementally. Full exports will typically not be used, unless you want to restore a node in a cluster.

The file resulting of the “Full Filtered” mode may contain objects from several workspaces. Indeed, if the meta-modeling Processes you have selected in the ‘Select Content’ step are dependent on some items from other workspaces, these items will be automatically included in the result of the export process to ensure its consistency.

In order to create an export project, the following steps are available:

  • Define the scope and mode of your export.
  • Select the content. This step is only available for a ‘Full filtered’ mode i.e. for a full export when ‘Select workspace’ is equal to ‘current’. The list of projects presented is the same as the list presented on the dashboard, and takes into account the access rights and team assignment.
  • Apply filters on the content you want to export. A filter can be applied in order to restrict the export to certain objects only.
  • Execute the export and follow-up its execution.
    Warning: The export does not lock the objects being exported. Ensure that your colleagues know you are exporting a project and that they stop working. Otherwise, the content you export might not correspond to what you expect.