SR-A7649 · Issue 219010
Fixed RD "Report on Descendant" access to application page
Resolved in Pega Version 7.2
A report definition using the "Report on Descendant" option worked when executed from a user session but did not work when executed by a File Listener Process. This was due to the report not being able to access the application page in the batch requestor context, and has been corrected.
SR-A12707 · Issue 229383
Subreport join/filter updated
Resolved in Pega Version 7.2
An invalid subreport join/filter condition error was thrown if a filter with an unoptimized property from a sub report on one side had an optimized or literal property on the other side, even if the prconfig setting "reporting/useStreamInJoinConditions" was set to true. This has been fixed.
SR-A7513 · Issue 218791
Corrected timing of OnMessage firing on restart
Resolved in Pega Version 7.2
MDB Listeners that have been processing incoming messages successfully were becoming problematic when the JVM was restarted. At that time, PRJMSListener's onMessage() started to process JMS messages from the queue even when the PegaRULES engine had not successfully initialized, resulting in large numbers of repeating error messages in the log file. In order to resolve this, the PRJMSListener.java has been updated to check the node initialization in OnMessage() itself instead of invoke() of JMSListenerServant.
SR-A9129 · Issue 220717
Report Definition error message localized
Resolved in Pega Version 7.2
Localization/customization has been added for the Report Definition error message : "Retrieving the report data exceeded the limit of * seconds. Please try making the report more specific by further limiting which rows to include".
SR-A12941 · Issue 224444
NCHAR column type added to RD supported column types
Resolved in Pega Version 7.2
After upgrade, "No enum constant com.pega.pegarules.data.external.rd.constants.ColumnType.NCHAR " exceptions were being thrown for most access to external database tables. These tables are accessed with internal methods (obj-save, obj-open, etc.). As part of refactoring the Report Definition code, explicit references were needed for external column types and only types given were supported. The NCHAR column type has now been added to the list of supported column types in ColumnType.java
SR-A12941 · Issue 230561
NCHAR column type added to RD supported column types
Resolved in Pega Version 7.2
After upgrade, "No enum constant com.pega.pegarules.data.external.rd.constants.ColumnType.NCHAR " exceptions were being thrown for most access to external database tables. These tables are accessed with internal methods (obj-save, obj-open, etc.). As part of refactoring the Report Definition code, explicit references were needed for external column types and only types given were supported. The NCHAR column type has now been added to the list of supported column types in ColumnType.java
SR-A15878 · Issue 230806
Elastic Search updated for external tables
Resolved in Pega Version 7.2
Elastic Search on an external table was returning incorrectly limited results. This was an issue with passing more than one property set in the query to the external table, and has been resolved by updating AbstractIndexer to add additional properties.
SR-A11148 · Issue 222428
Elastic Search updated for external tables
Resolved in Pega Version 7.2
Elastic Search on an external table was returning incorrectly limited results. This was an issue with passing more than one property set in the query to the external table, and has been resolved by updating AbstractIndexer to add additional properties.
SR-A11148 · Issue 221666
Elastic Search updated for external tables
Resolved in Pega Version 7.2
Elastic Search on an external table was returning incorrectly limited results. This was an issue with passing more than one property set in the query to the external table, and has been resolved by updating AbstractIndexer to add additional properties.
SR-A10518 · Issue 220215
Resolved exception for processing blank email body
Resolved in Pega Version 7.2
Processing was failing when the body of an email message was blank. In addition, the auto-reply header was being processed unnecessarily. Changes have been made to EmailListener.java to handle these scenarios.