In Content Manager > Pages, you can create templates and customize the HTML by clicking the edit button on the right side of the entry. You can also upload images and copy their URLs to include in the template. Remember to save the template before previewing it. Objects, such as PIM Products and Customers, can be selected to see exactly what the template will look like when that template is displayed with the object.
For delivery notes and invoices, use Configuration > WMS to set up the appropriate conditions for each specific PDF. For product previews, use Configuration > Product > PIM to set the appropriate templates for listing and detail previews.
The edit page of a template contains an HTML sandbox. Our engine parses standard HTML as well as special strings and tags. The HTML parser replaces special strings with the appropriate product and order information. These special strings have the following structure: __type.code__. The double underscores indicate that it’s a value that needs to be replaced, and the type and codes are columns found in core_attributes. Several special strings that depart from the standard are listed below.
|__domain__||Renders the current of domain. Typically used with image paths.|
|__days__||Renders the remaining number of days for pickup.|
|__customLabel__||Renders the label of a custom attribute. Must be used in a <customAttributes> tag.|
|__customValue__||Renders the value of a custom attribute. Must be used in a <customAttributes> tag.|
Custom tags have been implemented to properly render the templates. All tags are double tags, with opening and closing tags.
Wraps around a date value. Uses a format property that follows Carbon date formatting.
|<deadline>||Renders the deadline date for pickup.|
|<today>||Renders today’s date in Y-m-d format.|
|<yesterday>||Renders yesterday’s date in Y-m-d format.|
|<tomorrow>||Renders tomorrow’s date in Y-m-d format.|
|<auto_number>||Renders an auto-incrementing integer. Typically used for numbering items in a table.|
Formats the number in between by adding commas and decimal places. Contains the following properties:
decimals: Specifies the number of decimal places.
decimal-separator: Specifies the character used to separate the decimals. Uses "." by default.
thousands-separator: Specifies the character used to separate the thousands. Uses "," by default.
<numberFormat decimals=”2” decimal-separator="." thousands-separator=",">1300</numberFormat>.
The example above will render 1,300.00.
Renders a value by evaluating the expression within the tag.
<calc>2+5</calc> // will render 7
<calc>__fulfilment_orders.total_amount__ - __fulfilment_orders.discount__</calc>
|<pdf_style>||Wraps around <style> tags.|
|<pdf_header>||Typically wraps around the logo and information in the top right of the PDF.|
|<pdf_above_table>||Wraps around HTML sticking out above a table. Typically used for additional customer information and total quantities.|
|<pdf_table>||Wraps around <table> tags. Should include table headers.|
|<pdf_table_tr relation="relationName">||Wraps around <tr> tags. Should not be in <pdf_table>. Only one <pdf_table_tr> is needed per table as the parser will loop over provided objects to render each row. See <loop relation="relationName"> for more details.|
|<pdf_below_table>||Wraps around HTML sticking out below a table. Typically used for subtotals.|
|<pdf_footer>||Wraps around footer HTML. Typically used for business information.|
These tags are used to retrieve complex data from the database. Data associated with a specific object are organized into different object types and are connected via relationships. For example, an order object has a customer object as they are the one that made the order. These tags are used to get information from objects related to the selected object.
Gets an object specified by the target attribute relationship. An example of this would be using <relation target="saleOrder"> to get the sale order associated with a fulfilment order.
Example with a fulfilment order object:
Loops over the objects specified by the relation attribute relationship. Same functionality as <pdf_table_tr> but for non-pdf templates. The relationship should point to an array of objects.
Example with a fulfilment order object:
Typically used with PIM products. Fetches custom attributes that are meant to be shown on preview. Uses the HTML inside of <customAttributes> as a template to generate each instance of a custom attribute. An example of a custom attribute would be “Clothing Material”: “Denim.” The text surrounded by double underscores will be replaced with the corresponding data.
<td style="width: 25%; font-weight: bold;">
<td style="width: 75%;">
Renders a barcode with the text in between. Order numbers and ids can be set here.
Renders a QR code with the text in between. Order numbers and ids can be set here. To control the styling, wrap the tag in a div with inline styling.
<div style="width:100px;height:100px;vertical-align: middle;margin: auto;">
Renders the logo specified in Configuration > Design. Attributes can be attached to this tag, such as class and style.
<logo class="logo-img" style="margin: 2px"></logo>
Renders the company name specified in Configuration > General. To get the company name in an email subject, use __company_name__ instead. If no company name is specified, this tag will return "CLEARomni Team".
Happy shopping, <companyName></companyName>
Renders the site name specified in Configuration > General. To get the site name in an email subject, use __site_name__ instead.
Example in an email subject:
__site_name__: You have new products!