sections in the article
This article explains the functionality of the Configuration module, available in Print 2.0.
About Print modules
Print 2.0 currently contains four standard modules, as well as modules available as add-ons. Each module serves a separate Print operation.
The Configuration module is part of the standard functionality and is where you create a publication data set.
About the Configuration module
In the Configuration module, you can
- create new configurations.
- determine the entity level for your publication dataset.
- use wildcards in fields when looking for data with child or parent relations.
- apply filters to fields.
- apply formulas to compile the data.
- create table configurations.
Learn more about the other modules available in Print by reading about the Print 2.0 user interface.
Creating a new configuration with floating model options
The main functionality of this module is to create print data set configurations using floating model options. Based on the output, you can configure and compile which fields to contain in your Publication dataset using filters and formulas.
In the Configurations module
do the following:
- Click
NEW CONFIGURATION
the New Print Configuration pop-up window opens.
- Type a name for your configuration in the Name area.
- Use the Selectable drop-down menu to choose the Entity level at which the Publication dataset will be selected.
The level can be a Section, a Subsection, or a Sub-subsection.
- Use the Starting Point drop-down menu to choose the Publication Entity which will act as the starting point for the selection.
Data will be grouped on this level in the .xml file you create using the Prints module.
The maximum difference between your Selectable and your Starting Point is three levels.
- Click
ADD to add a Field in your publication.
- Type in the Content area, to search for the name or path for the Field value.
You will automatically get the Entity Type and suggestions for a Field name. You can edit the Field name that appears.
You can also apply filters and formulas to a Field you have added.
- Click CREATE when you're done.
Your new configuration is now available in the list of Print Configurations.
Making the most of Fields when creating a configuration
Fields have several functionalities that simplify their use.
Reordering Fields
You can change the Field order by editing the number in front of the field, to a different number.
Using wildcards
You can use wildcards to access children-level or parent-level Entities.
example
| Syntax | Example | Result |
|---|---|---|
|
/../ChildEntity.ChildField |
/../Item.ItemName |
If an Item is a child of a Product, this will fetch the Item name. |
|
/../ParentEntity.ParentField |
/../Section.SectionName |
If a Section is a parent of a Product, this will fetch the Section name. |
If a path is valid, the background color of the Content area will turn green.
Fetching data from Entities
You can fetch data from both children and parent level Entities.
example
| Syntax | Example | Result |
|---|---|---|
| ChildEntity.ChildEntityDatafield |
Item.ItemSize |
If an Item is a child of a Product, this will fetch the Item size. |
| Parent.ParentEntityField |
Parent.SectionName |
If a Section is a parent of a Product, this will fetch the Section name. |
| ../ParentEntity.ParentEntityField |
../Section.SectionName |
This will fetch all the Sections where a Product is included. |
For a parent Entity two levels up the syntax is Parent/Parent.parentEntityField
Fetching Resources
You can fetch Resources.
example
| Syntax | Example | Result |
|---|---|---|
| Resource.Url |
Item/Resource.Url
|
If an Item is a child of a Product, this will fetch the Resource from the Item level. |
| Entity/Resource.Url |
Parent/Resource.Url
|
If a Section is a parent of a Product, this will fetch the Resources from the Section level. |
Fetching Specifications
You can fetch Specification attributes by searching on the Specification name (not the FieldId).
example
| Syntax | Example | Result |
|---|---|---|
| SpecificationName |
Hardware |
If you have a Specification called "Hardware" on Product level and the main Entity of your print configuration is a Product this will fetch the Specification for the main Entity. |
| Child.SpecificationName |
Item.Hardware |
If your main Entity is Product, but you need to fetch the "Hardware" specification on Item level, this will fetch the Specification for the Item Entity. |
Applying filters
You can apply filters on a Field.
To apply a filter to a Field
do the following:
- Click
the Field Filter pop-up window opens.
- Type a value in the Filter Value area by which the Field will be filtered.
- Click SAVE
Your filter is applied.
If the filter icon of a Field is orange then a filter is applied to this Field.
example
| Example | Result |
|---|---|
| Brand |
If ProductBrand is the Field, then you can apply a filter with a specific brand as the value. Only the products with this brand value will be available for this Field. |
Using formulas to compile Field data
You can apply one of the available formulas when you need to compile the data of a specific Field.
To apply a formula to a Field
do the following:
- Click
under the Field.
the Formula drop-down list opens.
- Choose the Formula you want to apply, and configure it accordingly using the formula's pop-up window.
Some formulas might allow you to add multiple instances by clicking ADD.
- Click SAVE
Your formula is applied.
There are several available formulas that you can use to compile Field data.
-
AddTitle
Adds the Field title in front of the value.
-
BooleanFormula
Changes a Boolean to a predefined text.
-
ChildFilter
Filters output fields based on a value fromChildEntityField
-
CVLKey
Outputs CVL values or keys
-
FieldTitle
Shows the Field name.
-
Join
If multiple outputs are possible, it collects the values, separated by a chosen separator.
-
RemoveIfEmpty
If inriver does not have a value for this field, all the other formulas will be ignored and this field will not appear at the output.
-
Select
Shows values from a predefined link position.
-
Take
Shows a certain amount of values.
-
Unique
Shows unique values.
-
Wrap
Places the data between chosen characters.
For details on the use of each formula, its configuration options, and examples of its use, you can read Field formulas in Print 2.0 Configuration module.
How to add a table configuration in Print 2.0
The table configuration is an add-on functionality of the Configuration module.
Print 2.0 add-on functionalities will only be available if your organization has purchased them.
The creation of a table dataset is done in the same way as any new configuration. The option to configure the table becomes available as soon as you change the Field Type to Table.
To add a table configuration
do the following:
- Click
- Change the Type to Table.
- Click on the table configuration icon (
) that appears in the Content area.
The table configuration pop-up window appears.
- Select the configuration you want to use as a table, from the Configuration drop-down list.
- Select the formatting and orientation, from the Formatting and Orientation drop-down lists respectively.
You can add specific formatting by adding a .dll file in Control Center.
- Click SET when you're done.
Your table configuration has been added.
Video demonstration
Further reading
Navigating the Print 2.0 user interface
Comments
13 comments
Is it possible to filter based upon NOT having the value? i.e. the negative of the ProductBrand example.
Hello Mark,
Unfortunately no. There is no Formula to exclude specific values from the configuration output.
Best Regards,
Gabriela Dobrescu / Business Solution Architect
Please clarify ... is the syntax is it Resource.URL or Resource.Url?
I believe that it is the latter and the field type ids are case sensitive.
Resource.Url is the correct syntax, article will be revised.
Hello, would there be any docs available to use the output (values) of a Specification linked to an entity (defined as main entity in the Config) through the Config module. For entities fields, it is quite flexible, but I miss documentation when it comes to a specification fields and my investigations so far are quite erratic..
Thanks in advance!
Hi Florian. I added a point for Specifications in the list of functionalities. Thank you for pointing out the omission. Hope it helps!
Hello Konstantine,
Thank you. Nevertheless, I still struggle and it doesn't seem to solve my issue.
My Print main entity is Product.
Let's say that I have a Product X which includes a Specification with SpecificationName = "My Product Specification" including 2 fields of type Integer whose Ids are "FieldA" and "FieldB", enriched on Product X with "10" and "12".
If I put in Print content "My Product Specification", "Specification.FieldA"... there is no output...
So basically, I'm still stuck.
So first question is: how do we do to output one single field value of a specification template linked to a product?
Second question: is it possible to output the entire product specification at once?
Thanks for support.
Hello Florian,
Please consider raising a zendesk ticket for support and we will assist with your configuration.
Regards,
Andrei
Florian,
In your example, try using the specification name directly in the syntax, for example:
FieldA or FieldB
Is it possible to filter on more than 1 value?
For example items with ItemColour 'white' or 'black'?
It should be possible to filter out 2 values at once by separating them with “|”.
Thanks Andrei Feleaga! Where did you find this information?
Another question, how do I get the fieldset (ID and/ or name) in Print 2.0?
Right now, it’s not possible to fetch this information out of the box.
Please sign in to leave a comment.