2018.1

Connect 2018.1.1 Enhancements/Fixes
Section cloning issues
Two separate Section cloning issues were fixed. (SHARED-64087)
The issues were:
l
Cloned content was being based upon the section for which addBefore or addAfter was
invoked, rather than the section the clone was originally based on.
l The rendered page count could be incorrect. This was due to the page count of a section
bundle (consisting of sections with continuous page numbering) mistakenly overwriting
the page count of the previous section bundle.
Weaver Engine memory leak
Improvements made to how the Weaver Engine reclaims memory, in order to reduce any
memory leakage. (SHARED-64205)
DataMapper issue with PDF input
In PlanetPress Connect 1.8 and previous versions, the DataMapper's boundaries.find()
function returned the region searched within PDF files, whereas for text files it returned the
exact region where the text was found. In 2018.1 this was changed so that boundaries.find()
on PDFs would return the exact region where the text was found, the same as for text files.
However, it was subsequently found that this could cause issues with previously created
templates using the function on PDF files. Consequently, this change was reverted in 2018.1.1.
(SHARED-64201)
Workflow - Updated GetKeySets() implementation now made backwards compatible
The Workflow function to retrieve key values GetKeySets() was updated in Workflow 2018.1 to
use the more formerly correct asterisk '*' parameter for retrieving all key sets. This change broke
existing jobs that used the previously allowable blank entry to retrieve all Key Sets.
In Workflow 2018.1.1 the GetKeySets() function has been changed to support both the more
correct asterisk '*' parameter as well as the deprecated blank entry. (SHARED-64162)
Page 1201