Hello Tim,

We completely understand the setbacks and inconvenience that regressions can cause, especially when they impact an important part of a customer's workflow. We take regressions very seriously, and our process specifically treats them with the highest priority to ensure they are addressed as quickly as possible.

With that in mind, I would like to inform you that the issue is already under development, and we plan to introduce the fix in our next Document Processing release.

We also agree that it is important for customers to have publicly available information about known regressions. This is one of the main purposes of our Public Feedback Portal, where reported issues are tracked and logged so that customers can stay informed about their status and any relevant workarounds or affected versions.

I have gone ahead and updated the public page for the reported issue to explicitly flag it as a regression and, importantly, to identify the exact version in which the regression was introduced. This gives customers visibility into the issue and allows them to make an informed decision about which version to use if they need to avoid it.

In parallel, the regression itself is being handled through our normal regression process, where it receives the highest priority. We appreciate you bringing this to our attention and understand the importance of getting the fix in place as soon as possible.

Regards,
Yoan
Progress Telerik