> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/assessment-framework/assessment-framework-styling-tools-for-pdf.md).
# Assessment Framework Styling Tools for PDF
## Description
The Assessment Framework can be configured to produce a PDF document (replica of the report) that users can download or print. This PDF is produced by the report logicnet and any custom PDF stylesheets added by the user. Tools to aid in the styling of the final PDF are available by changing the following in Project Settings to YES.
## PDF Styling Tools
When you run an application in TEST mode the system displays additional support tools on screen to make the PDF styling process more efficient. The system does NOT display these elements when the application runs in production mode from a URL or package launcher.
### Show HTML Link
With the *Show HTML Link* option checked in the Designer, the runtime TEST displays a link to the HTML page generated by the specific run of the LogicNets application. You can download this file and use it in generic CSS tools to help create and modify the desired CSS settings.
### Show Upload and Convert
With *Show Upload and Convert* option checked in the Designer, the runtime TEST shows a File Upload function that will receive any HTML file. Pressing the CONVERT button applies the designated CSS files to the HTML file and output a PDF. With both the CSS file open in the Designer in one window and the TEST run open in a second window, the Designer can easily edit the CSS, convert an example or control HTML file, and verify the desired styling effects quickly, without having to restart the whole application.
Note that the above tools are only generated when running the create PDF part in TEST mode.
* To hide these choices navigate to the Framework settings and set *Show PDF styling tools in test mode* to *No.*
* To hide these choices temporarily on any given screen, use F12 Developer tools, locate the DIV called pdf-help and add *display:none*, or paste in *.pdf\_help {display:none}* into the CSS file in-line.
* To remove the choices for all TEST runs, paste the same CSS into your custom CSS file for the application.
For more information, go to the [create pdf](/release-9/platform-documentation/process-node-parts/create-pdf.md) part definition, and/or download the [example project](/release-9/example-gallery/example-projects-for-parts/create-pdf-example-project.md).
### PDF CSS Syntax
In general, the stylesheet(s) applied to the PDF follow the same syntax as for normal HTML CSS but there are some variations. For more details of the general possibilities of the Prince PDF converter and required syntax, see .
### Tips & Tricks
Below are some pitfalls we have learned to avoid when styling PDF documents. Please reply with any others you encounter and want to share with us!
* \[Excerpt from Prince documentation] Care needs to be taken with `inline-block` elements, because Prince cannot split them over several pages.
* You can control headers and footers on the first and subsequent pages of the PDF to include text, images, page numbers, etc. For an example of all these in use, add a Standard ASF Framework application to your Designer, and inspect the PDF CSS and first logicnet in the report folder.
* PrincePDF has a feature called **flow** that enables the Designer to move content held in a DIV from the main body of the text to a header, footer, etc. The DIV must be placed at the top of the report body being converted to PDF and it can be "flowed" from there (placing the DIV at the foot of the report body will not be successful). For an example of flow in use, add a Standard ASF Framework application to your Designer, and inspect the PDF CSS and first logicnet in the report folder.
* Breaking long words without spaces (e.g. email addresses, URLs, etc.) in small spaces (like table columns) can be achieved using the soft-break tag `` or ``
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/assessment-framework/assessment-framework-styling-tools-for-pdf.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.