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.

Executing Exports

Once the content of the export project has been defined, and once the filters have been applied, you are ready to execute your export.

In order to execute the export, proceed as follows:

  • [In the menu toolbar]
    • Click on the start function
  • [In the popup]
    • Enter a file name for the export file. By default, a file name will be suggested by the Designer, based on the “export_” text and on the timestamp
  • [In the popup]
    • Enter the export file type. Possible choices are XML or Excel
  • [In the popup, if File type= XML]
    • Enter the type of format. Possible choices are XML or ZIP. The latter choice will allow you to reduce the size of the file
    • If needed, tick ‘Explicit pricing variant’. This option allows to export pricing grids by explicitly generating the combination of aliases for each pricing variant instead of factorizing some elements using fingerprints.
    • If a corresponding Java class is declared in the cameleon.properties file on the server, the "Push meta data to CRM" checkbox is visible. If checked, it allows pushing CPQ XML structure to a CRM like MS Dynamics, so that CRM and CPQ meta elements remain in sync, meaning that every change done on the model in CPQ is proactively applied in the CRM. The declared Java class will be called automatically on a successful export.
  • [In the popup, if File type= Excel]
    • Enter the locale language. The chosen language will be used as the original language for translations.
    • Enter the default workspace. In the exported Excel file, all objects will be default belong to that workspace unless the object is explicitly prefixed by the workspace to which it belongs. For instance, the object “myObject” will belong to the default workspace “wks” unless it is prefixed by another workspace, i.e. “anotherWks/myObject”.
    • Enter the default action. The possible choices are empty, * et x. The chosen valuewill be used as a default value for all “action” cells in the exported file.
      • Check “Group by Business Type” if the objects associated to different business types should

        be grouped into separate Excel sheets

    • Check “One grid per excel sheet” if objects of the same type (CP, SP, SI, etc.) should be grouped in the same Excel sheet.
      • If the latter two options are both chosen, an Excel sheet will be created per object type and per business type.
  • [In the popup]
    • Click on OK.
      Reference: For more information about Excel-based export, please refer to Understanding Excel-based Exports & Imports:

      Do Not: Test campaigns are not taken into account for XLSX type of exports.

Once the export has been started, a line will be added to the table presented in this step. In order to look at the status of the export, click on the status indicator. This will issue a popup window showing the progress of the export, ordered by object type.

The table presented in this step will hold all exported files (unless you’ve specifically deleted them) for the current export project. For each line, you will be able to:

  • Delete it, by checking the line and clicking on the Delete function in the menu toolbar.
  • Look at the log of the export execution, by clicking on the status indication.
  • Download the exported file by clicking on the file link.
  • Check the status of the metadata push to CRM if activated
    Tip: The physical location of the exported file on the server is determined by

    the modeling.api.distributionFolder parameter in the cameleon.properties configuration file.