Calyx RIM 7.0 Publishing

Publish Guidelines

Folders

You can avoid errors in your publishing jobs by following these guidelines.
  • Some publishing attributes in folders may accept or require multiple values. Delimit multiple values for publishing attributes with commas.

Documents

  • Some publishing attributes in documents may accept or require multiple values. Delimit multiple values for publishing attributes with commas.
  • Encrypted PDFs can cause errors during publishing. An encrypted PDF cannot be concatenated with other files and may cause an error for that volume or leaf. For the paper output channel, you will need to remove the encryption prior to successfully publishing the document. For the electronic output channel, you can either remove the encryption, or simply change the Use Native File leaf attribute to Yes on the parent leaf.
  • When output contains a PDF document which is under a leaf set with Use Native File, and then it is Published to a Single File, the TOC generates as expected in that the native leaf and PDF TOC are unchanged in a single file output.
  • Documents in your assembly must be uniquely named in the document repository, relative to other documents in your assembly. If they cannot be uniquely named, they must be stored in uniquely named folders in the repository.
Warning: You should not attempt to manipulate or delete an assigned document or publishing element while it is being published.

Document Placeholders

  • When publishing, document placeholders are flagged as errors, but the publish completes successfully. This is expected behavior.

Leaf Elements

  • Some publishing attributes in leaf elements may accept or require multiple values. Delimit multiple values for publishing attributes with commas.
  • Leaf elements that are to be created in the same output folder cannot have the same output file name. If two leaf elements have the same output file name and are in different folders that have the same output folder locations, the publish log reports duplicate folder/file paths.
  • The Output File attribute must have a value. The file name must include the appropriate extension (for example, outputfile.pdf). The submission cannot be published without a file name.
  • The Output File attribute must include the correct extension. For example, when you choose Yes for the Use Native File attribute to publish a Word document and you enter outputfile.pdf for the Output Filename attribute, you cannot open the file with Acrobat. You can change the file name extension to .doc to open it in Word.
  • If you choose Yes for the Use Native File attribute for a leaf element containing two or more non-PDF documents, a message warns you that Calyx RIM cannot concatenate non-PDF documents.
  • If a leaf element contains multiple documents and one but not all the documents are encrypted or password protected, the output for the leaf comprises only the non-encrypted documents. The encrypted documents are overwritten by the non-encrypted documents.
  • When a leaf element contains multiple encrypted documents, the final output comprises the last encrypted document in the leaf definition.
  • The output file on a leaf must contain content. Otherwise, the following error will occur: unable to calculate attribute checksum for leaf...exception detected...access denied.
  • If a volume break resides on the leaf you are deleting, you should move the volume break to the closest folder. Volume breaks that reside on a deleted leaf will not be published.