2020.1

property to retrieve the content set in its entirety (i.e. all content items that belong to that content
set); it isn't possible to retrieve individual content items using that property. Properties added to
a content set are not propagated to the individual items in that content set.
To label both a set and the items in it, use the Set Properties task twice.
Note
Data field values and properties of items in the Connect database are also used when
sorting the output. Make sure to set properties that are necessary for sorting on the
content item level.
Commingling
When documents in one print batch originate from different templates, that is called
commingling.
Commingling isn't very different from batching in how it's done. The content creation phase will
likely be a little different, as there will probably be a separate process or branch for each of the
templates used to create the print content.
However, sorting and grouping can become more important when print content items are
commingled. For instance, when invoices and letters are commingled, they probably need to be
grouped per customer, and sorted in a certain way. Ensure that there is a unique ID in the
different data sets that can be used to group items together that belong to the same mail piece.
Sorting and grouping items in print batches
Print content items can be grouped and sorted by the values of data fields or by the values of
properties set on them in the Connect database.
l
Values:Print content items and sets don't contain data fields, but they do have a link to
the data record with which they were created, so selecting and sorting them by value is
still a possibility.
l
Properties are key/value pairs that can be set on entities in the Connect database. There
are two ways to do that:
l Using the Set Properties task.
Ideally, the Set Properties task directly follows the Create Print Content task in a
Workflow process. The Create Print Content task returns the IDs of the content items
Page 191