PDF list and form reports fails if there is a "global.Color" Script Include on the instance - Known Error

PDF list and form reports fails if there is a "global.Color" Script Include on the instance Description If there is a class with name "Color", the PDF export from forms and lists fails with an empty page, or the thrown error: "Could not initialize class com.glide.pdf.itext.components.Color".

The issue was observed after upgrading to Quebec. The reporting is not resilient to the name of the classes custom created as script includes.

Steps to Reproduce

1. Create a new Script Include "Color" as follows: var Color = Class.create(); Color.prototype = { }

2. Try to export a list view to PDF, or open an incident and try to export to PDF.

The export will not happen, either not completing, or opening a blank page.

Workaround Custom Script Includes created with the same name as a PDF component provided as scoped scriptable inevitably cause the pdf generation to fail, as the component class fails to load at runtime.

After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make this decision lightly, and we apologise for any inconvenience.

The workaround is to rename the Script Include "Color" to something like "ColorCustom".