You are here: Document Engine > Document Engine Management Center

Document Engine Management Center

OVERVIEW

Use the Document Engine Management Center to manage your documents and which Printer-Friendly XSL Views they will be attached to.

  1. Click Admin to go to the Admin Home Page.

  2. Click Documents under Commerce and Documents.

    The Document Engine Management Center appears.

    The left-most panel shows Processes.

    The right-most panel shows the Document Editor List. This is where you will perform the majority of your actions.

ClosedProcesses Panel Icons


ClosedDocument Editor List Icons


ADMINISTRATION

Most of the document engine administration can be completed within Documents.

ClosedCreating a new document

  1. Go to the Document Engine Management Center.
  2. In the Document Editor List, click Add Document.

  1. Enter the Name, Variable Name and Description for your document. Optional: Select a document template. The default selection is Blank Document.
  2. Click Add.
  3. Click Open Document Editor to open the Document Engine and begin creating your document.
  4. Once your have finished editing your document, and saved it, close the Document Editor and select Deploy for the document.
    1. To edit your Documents, click on the Document Name; the Document Editor will appear.

ClosedMigrating a document between CPQ Cloud sites

  1. Go to the Document Engine Management Center.
  2. From the Document Editor list, locate the document that you'd like to migrate.
  3. Confirm that the file name has only alpha_numeric characters and underscores.

Any other characters in the file name will cause the subsequent upload to fail.

  1. Click Export.
    1. The exported .ZIP file has the same name as the document that is being exported.

  1. Save the ZIP file to your computer.
  2. On the production site, or Commerce Process, that you are migrating the document to, go to the Document Editor List page and click Import.
    1. Documents on the test site and the production site are not considered equivalent if both are manually created, even if they have the same variable name.

      For documents to be equivalent in production and test, the production documents must have been created through an upload action (as described above) OR the two sties must be exact database copies.

Once you have created or migrated documents with the Document List, and deployed the documents, link them to a printer-friendly XSL view. Otherwise, end users cannot see or use the document.


NOTES

RELATED TOPICS

Related Topics Link IconSee Also