The first step to start generating documents for products is to create a document template. If you are unable to do this yourself, we at iSYS are ready to help you create a document template based on your design preferences.

If you have the necessary skills, you can also create the template yourself and upload it directly into feed®. If you have an existing template available, you can easily make adjustments and changes to it. However, remember to back up the template before making changes, so you have a working copy in case you need to revert to the old version.

Create a document template

The feed® Document Generation module uses Word templates (.docx files) as the basis for generating PDF documents. Therefore, to create a document template, you need a word processing tool that can save the document as a Word file (.docx).
If you don't have Word from the Office package available, LibreOffice is a good alternative.

How to create a template to integrate information from product cards in feed® is a course in itself. We can assist in creating a template for you based on design suggestions, or if you prefer to learn it yourself, take a look at the user documentation available on Docmosis:

Docmosis User Documentation

Ensure that the selection is set to Tornado and the document version is (Latest) to access the most up-to-date documentation.

Look for the Template Guide (if you're new to Docmosis) or the Quick Reference (if you prefer a concise functionality overview).

Some simple tips to get started:

It is important to know that the names of the fields you want to map from feed does not have to have the same names in the template.

You also don't need to have import codes in the feed attributes you want to map to Docmosis, and if you add one later on, or change the name of the feed attribute, it will still stay connected in the mapping.  

The field names (variable names) you use in the template has to be without spaces. 

Variables: To create a dynamic field in the template that retrieves data from feed®, use the following syntax: `<<My_variable_name>>`. "My_variable_name" will then be available later in the configuration as a field that can be mapped to data in feed®.

Images: If you want to retrieve an image from the product card in feed®, you must first insert a placeholder image in the template at the desired location and size. Then, you need to select the image (important!) and add a bookmark to the image.

The name of the bookmark must follow a specific naming standard (important!): "imgfit_my_variable," where "imgfit_" is a keyword indicating that the image should fit the specified area for the image in the template. You can also use the keyword <<imgstretch_my_variable" to stretch the picture in the placeholder.
"my_variable" becomes the variable you link to the desired media role in the configuration.

Important: The media role being mapped only retrieves the first image in the feed. If you have multiple placeholders with the same media role, the same image will be displayed multiple times.

Conditional <<cs_>>: Content between the opening element <<cs_and the closing element is included or excluded depending on the value associated with “name” or the expression “expr”. The end tag must match exactly, or may be anonymous: <<es_>>.

<<cs_my_variable>> (choose one attribute, text to map to this element. Only the value will show, not the field name. If the value is blank it will not appear).

<<cs_{my_variable}>>(Let you add attribute and hardcoded text. If the product has a blank/null value on the attribute nothing will appear (hardcoded text or value).

•  example: 
  <<cs_{f_pak_gtin!=null&&f_pak_gtin!=’’}>>
  F-Pak
  GTIN: <<f_pak_gtin>>
  <<es_>>
• The Syntax example above lets you hide attributes with blank values (null values). The setup above will show the hardcoded text "F-Pak", then a line break with the hardcoded text "GTIN:" followed by the GTIN value. If blank, no text or value will be shown.  

Date:
<<{dateFormat($nowUTC, 'EEEE, dd MMMM yyyy')}>>

• • Syntax for timestamp that will present the date when the document was created, or last updated. 

Variants in DocPro

Add your variants to a DocPro document using the "repeating row" segment as shown in the example below.
The way it works is that a table is set up where the first line indicates that a repeating row will follow by starting the tag with "rr_", which stands for Repeating Row.
[*] states that it includes all. 

Then comes the line that will be repeated. In the example below, productnumber, name, and price are added to the line that will be repeated for all variants of the product.
For ending the reapeating row use "er_" for End Row.
 

 
 
In the mapping overview, you will see "variants" as a field that can be mapped. Variants can then be mapped to "Variant." When this field is mapped, the underlying fields will become visible and available for mapping. These underlying fields will then receive values from the variants.
 

 
 

The result in the generated document will then be, for example:

ETIM-features in DocPro

Add your variants to a DocPro document using the "repeating row" segment as shown in the example below.
The way it works is that a table is set up where the first line indicates that a repeating row will follow by starting the tag with "rr_", which stands for Repeating Row.
[*] states that it includes all. 

Then comes the line that will be repeated. In the example below,  id, name, valueId, value, unitName and unitAbbr are added to the line that will be repeated for all ETIM features for a given version for the product.
For ending the reapeating row use "er_" for End Row.

In the mapping overview, you will see "etim_features" as a field that can be mapped.

In the example below it is mapped to ETIM features for version 9.

When this field is mapped, the underlying fields will become visible and available for mapping. These underlying fields will then receive values from the features.