Deploying additional diagnostics and error tracing from publish wizard in EngageOne Designer

Products Affected: Engage One Designer, EngageOne Generate
Product Feature: Designer
Additional Diagnostics is used for debugging logic in your publication.   Additional information can be found in the Engageone Designer User's Guide in section 'Publishing and Deployment'.

To set trace files, look in the Advanced Options from the Production Job settings:

User-added image

If there is an error with a specific set of customer data, the default option is to Abort the production job, but this can be changed to either "Skip Publication" where it will skip the data for that customer entirely and continue processing the rest of the file or "Record data and skip publication" which will extract the faulty data, and write it out to the location and file name specified in this option.  Please note, this does not work down to a field level, it only works at record level and only where there may be a missing mandatory record, an undefined record is found, or a child of a repeating group is present without its parent record.  Note also that this does not work with anything other than keyed record data (for example, NOT XML). 

The second option (When shape is positioned off the page) is self explanatory, as is the suppress messages option.

The Diagnostics option gives the user the ability to write out a trace file that provides information about precisely where in the publication the job has failed.  It is important to label items in your programming logic, so it is easy to pinpoint exactly where the problem is occurring in your design.

User-added image

The Produce Trace Information check box needs to be activated, and the name and deployment location of the trace file needs to be specified.  If more indepth information is required, once the check box has been activated, the Verbose Trace Information check box will become available.

Both of these options can also be deployed in the Override Production Setting (OPS) file used in conjunction with your production resources as follows:

CPconsole= {0|1}
SuppressMessages={NONE|ALL|INFORMATION|<comma separated message IDs>}

UPDATED:  July 20, 2020