SR-A76100 · Issue 254315
GRS supported for JNDI settings in JMS Listener
Resolved in Pega Version 7.2.2
Support has been added to use global resource reference settings for the JNDI server field and the initial context factory field value in the JMS listener during test connections.
SR-A88782 · Issue 263961
GRS supported for JNDI settings in JMS Listener
Resolved in Pega Version 7.2.2
Support has been added to use global resource reference settings for the JNDI server field and the initial context factory field value in the JMS listener during test connections.
SR-121623 · Issue 186850
Added WS-addressing UI check
Resolved in Pega Version 7.1.8
Connect SOAP calls were failing sporadically with a Message Addressing Property error while calling external services even when WS-Addressing was off. This happened when the WS setting was modified: the addressing module is engaged with first call of connector, and there was no cache clearing if the option was turned off for subsequent calls. Code has been added to check the addressing handler status and process it appropriately.
INC-173505 · Issue 657024
Error message updated for data page with REDUX
Resolved in Pega Version 8.7
A WrongModeException was generated when a runtime activity was trying to access a missing property in a data page with REDUX enabled. To clarify the issue, the error has been modified to be a MissingPropertyException. In addition, property information for a page group property was inferred on the top level page when it should have been inferred on the embedded page. This has been changed to infer the correct property information for mode-based processing to work as expected.
SR-124631 · Issue 188702
Resolved class loading errors for XMLSignatureFactory
Resolved in Pega Version 7.1.8
Class loading issues caused errors when loading XMLSignatureFactory as an API. These have been fixed by adjusting the .jar file.
INC-197112 · Issue 689260
Corrected unnecessary Severe Warnings for MSGraph account
Resolved in Pega Version 8.7
After configuring an email account with MSGraph settings and saving the the email account instance, three unneeded severe guardrail warnings were generated related to using D_pxGetApplicationSettingValue instead of a constant value. This has been resolved.
SR-A76413 · Issue 254770
Custom datatypes import support added to SQL RD
Resolved in Pega Version 7.2.2
After upgrade, external classes of type 'text' mapped to an external DB were throwing an error while executing report definition. This was due to the method used to get the column type, and the logic has been updated to correct this.
INC-179888 · Issue 663846
Training data correctly added to model
Resolved in Pega Version 8.7
Negative training data was not getting added to the entity model. This was traced to logic used to remove consecutive spaces which was incorrectly removing new lines and leading to entity detection of entities such as address line. This logic has now been removed.
INC-191033 · Issue 684370
Security updated for viewing data tables
Resolved in Pega Version 8.7
In order to improve security related to viewing data table instances, the privilege pxListClassRecords has been created in @baseclass and added to the "may start" activity ListEditor. Please add the privilege pxListClassRecords to access groups using ListEditor.
SR-125455 · Issue 189496
Error handling improved for importing data instances
Resolved in Pega Version 7.1.8
When importing data instances from a file, messaging showed success even when importing failed due to a database error (e.g.. column length not sufficient). In addition, the error in the log file was not detailed and no error appeared on screen. This problem was specific to Oracle DB and only with Unicode characters with a column size exceeding maximum length of 256. The error handling in this case has been improved: if there is a data base error, a message will appear on the modal dialog and all the changes in the transaction will be rolled back.