This article describes the General Settings of a DocumentsCorePack (DCP) template. Click here to see a full list of template settings.
Figure 1: General Settings of DocumentsCorePack
❶ General Settings
- a. Mark as Label Template: This article explains how to create Label Templates.
- b. Do not compress inserted images: You can turn off picture compression. Please note: Pictures can result in very large file sizes.
- c. Template Specific Language: Learn here to learn how to set a Template Specific Language.
- a. Target Output (DPI): Select the resolution of a print or scan.
- b. Enable fast Image Conversion: Generation speed could be improved, but quality could decrease when processing images with this setting enabled.
- a. Do not remove base64 strings from data source: In the document a copy of the inserted image is left as a base64 string. To save space, it is removed by default.
❹ Server Side Properties
- a. Workflow: Define in the template which workflow should be executed.
- b. Preserve Form fields for PDFs: Fillable PDF forms are PDF documents that include certain fields that can be edited without a PDF editor software. Learn more.
- c. Do not export Picture-Link Images as Base64: With this option you can send E-mails with dynamic images. Learn more.
- d. Embed full Fonts in the PDF Files: Non-standard fonts need to be embedded in the PDF to ensure they can be viewed and printed properly. Font embedding is the inclusion of the actual font files inside a pdf file. This can result in larger files.
- e. Enable Open Path Font support for PDFs: To ensure that Open Path Fonts (.opf) are correctly displayed in PDF documents, it is important to activate this option.
- f. PDF Compliance: It is a globally accepted standard, that ensures that PDF documents can still be read without problems even decades later.
- PDF Compliance 1.4: Is independent of the original application software, hardware, and operating system used to create them.
- PDF Compliance 1.5: This version was only used for a short time period.
- PDF Compliance 1.7 (ISO 32000-1): Is the most recent and widely used version DCP supports at the moment.
- PDF/A-1a – Level A conformance (PDF/A-1a): PDF documents can be made accessible to people with disabilities through the use of various accessibility features.
- PDF/A-1b – Referred to as Level B Conformance: This has a lower level of accessibility than PDF/A-1a.
- g. Do not add CRM Signature to generated HTML (deprecated): A marker was set in the HTML to prevent the signature from being inserted in the CRM.
❺ Query (FetchXML) Generation
- a. Use Deep Fetch Analyzer: The Deep Fetch Analyzer is a feature required for templates with many relationships and executes the fetch in an alternative way. Learn more.
- b. Use Query Expression: FetchXML will be converted to Query Expression. It represents the basic support for Virtual Tables/Entities.
❻ Note Creation Settings
- a. Note Title: Give a title to the note that is created. Here is the Syntax.
- b. Note Description: Enter a description for the note that is created. Here is the Syntax.
❼ Master Template
- a. Header/Footer (static): Manage the design of the header and footer of the document in a separate template. Learn how to do this here.
- b. Separate Footer (static): This is an optional setting for a Master Template for the footer.
- a. Disable Relative UTC Time Option: With this option, the time will be displayed based on the local time zone defined on the device or server where the document is created.
- b. Enable HTML Formatting for Fields: Maximize your user experience when working with HTML. This guide will help you.
- c. Convert field codes to text after merge (Field codes are not editable in Word for Web): Field codes like what-if statements or page numbering are converted to text in the merge process.
- d. Convert all tables to text: All tables within your document are converted to text in the merge process.
- e. Enable whitespace preservation for text fields: Leading whitespaces from text fields are considered and printed if this is active. Without this setting, the leading whitespaces are removed when merging the document.
That’s it! We appreciate your feedback! Please share your thoughts by sending an email to firstname.lastname@example.org.