Workbooks uses a templating language called XSLT to define how things are rendered into PDF. XSLT is very flexible and can produce a wide range of output. The XSL template is combined with an data from Workbooks to create the PDF. The data is in XML format. You can create your own XSL template from scratch, but often you will adapt an existing XSL template such as the supplied unified.xsl. To download a copy of a template click on its Filename in the list of PDF templates.
Examining the XML-formatted data
When Workbooks generates a PDF document the web browser downloads it from a URL like this:
This URL includes the internal ID of the document and template together with the format of output which is required: pdf. Replace pdf with xml to see the XML which is available:
The XML contains a lot of data, much of which will not be needed by the template. A typical XML document generated by Workbooks looks like this in outline (fetch a real one using the technique above to find out more):
... lots of fields ...
<document_currency_cost amount="145.84" code="GBP">£145.84</document_currency_cost>
... lots more fields ...
As you can see, there is an array of /hash/order_line_items and a set of settings under /hash/text: using the PDF Settings within Workbooks Configuration you can add additional settings which appear here. Other related fields and objects are also included within the XML.
As previously mentioned XSLT is used as the templating language for PDF output documents within Workbooks. Currently, we are using v1.0 of the XSL coding language. Various tutorials exist on the web and there are also several books available. We suggest you start with unified.xsl for examples, however, our forums contain lots of useful code, here. A code snippet can be seen below from the unified template which iterates over each line item on your Workbooks record:
<!-- extracts the setting called Line_Total_Label which is configured in the PDF Settings within Workbooks. -->
<xsl:for-each select="/hash/order_line_items/order_line_item[contains(./_preload_product_id, 'SHIPPING')=false()]">
<!-- Specify the code to iterate over. Typically this would be a table with rows and cells -->
The above introduces a block which is processed for every line item where the Product ID does not contain the string "SHIPPING". The behaviour can be reversed by changing FALSE to TRUE. The code will then process for every line item that does contain the string "SHIPPING".
The example XSLT (unified.xsl) includes configuration which applies when the document is being produced in Landscape mode as opposed to in Portrait mode. Within the XSLT you can tell the mode by testing the setting /hash/test/Page_Orientation (which is set to 'Landscape' if the template is name ends in _landscape).
In particular note that XSLT is not forgiving with regard to the number of columns in a table. If there is a cell which should be put in a non-existent column then the template will fail to render and you an error will be visible.
An example XSL template
Because unified.xsl is used in a wide variety of contexts it is particularly complex and contains a lot of 'if' and 'case' statements. A custom template will often be much simpler.
For example this template produces a page containing only an object_ref.
<!-- A very simple XSLT intended to be adapted for test purposes. -->
<xslt:stylesheet xmlns:date="http://exslt.org/dates-and-times" xmlns:str="http://exslt.org/strings" xmlns:xslt="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xslt:output indent="yes" encoding="utf-8"/>
<fo:simple-page-master master-name="Letter Page" page-width="11.7in" page-height="8.3in">
<fo:page-sequence master-reference="Letter Page">