VERIFIED SOLUTION i

Creating an XML Journal for an eHTML device for a Vault file type in EngageOne Vault

Product Feature: Printing-General Output
Product affected: EngageOne Generate
 
EngageOne® Generate will not produce an XML style journal for an eHTML device when the file type is set to Vault in the output channel definition in EngageOne Server Admin.

The reason for this is that eHTML cannot be loaded natively into Vault, it can only be loaded as a Collection and this type of ingestion does not support XML journals, therefore a flat journal is created.

If the device is either AFP, PDF or Postscript, then an XML journal will be produced as expected.
UPDATED:  May 23, 2019