Resolve extra blank page appearing in output following upgrade from Doc1 V5.1 to V5.6 or EngageOne Designer V6.x


Extra blank page appearing in Designer and output following upgrade from 5.1 to 5.6 or 6.x.


There is a difference in the way that the New Page action behaves between versions 5.1 and 5.6/6.x.

The difference is observed when document content occupies the entire printable page (the space remaining at the bottom of the page body is so tight that one more paragraph would cause the natural flow to a new page). If at this point a new page is forced using the New Page action, an additional, unnecessary page is included in versions 5.6 and later.

In 5.1 one additional new page is included, as expected, but with 5.6 onwards two pages are included. The New Page action now takes up space on the page itself, therefore if there is no room on the current page for a new paragraph in the current font, it first causes the overflow to a new page before executing the action resulting in two blank pages.


UPDATED: February 13, 2018
There was a change in New Page action between these two versions, causing this change in behaviour.

The additional blank page can be avoided by using the following parameter in your Ops file:


This should rectify the extra blank page produced within the output, so the old page flow behaviour is adhered to, but will not remove the extra blank page showing in Designer. The ops file parameter specified above is not available in Designer or Preview, but can be deployed in the <Custom> section in advanced preview.  It is also possible to deploy this parameters as part of the production job, in the Advanced Options--> Custom section.

Alternatively the extra page can be avoided in the majority of cases by changing the point size in the new page action to 0 or 1.