SR-A16401 · Issue 232956
Design-time email account accepts Data Page for port number
Resolved in Pega Version 7.2.1
When creating an Email Account rule (Integration-Resources), at design-time, the developer was prevented from using a Data Page reference as the Port number for the Sender or Receiver even though the run-time behavior of using a Data Page reference as a port worked. This has been resolved by removing the UI validation when the input starts with 'equal to', allowing Email Account save and connectivity testing to work with non-parameterized Data Page references for the port number in both Sender and Receiver configurations.
SR-A16406 · Issue 237367
Validation handling added for complex criteria values
Resolved in Pega Version 7.2.1
Incorrect validations were appearing when trying to save a List View rule with a criteria value that uses a property embedded in the pxResults page of a declare page in the Value field of the Content tab and that listed the top level declare page in Pages & Classes. This was due to the unusual structure of this referred property not automatically having the necessary links to retrieve the necessary pages and classes, and handling has been added for this special scenario.
SR-A16406 · Issue 231876
Validation handling added for complex criteria values
Resolved in Pega Version 7.2.1
Incorrect validations were appearing when trying to save a List View rule with a criteria value that uses a property embedded in the pxResults page of a declare page in the Value field of the Content tab and that listed the top level declare page in Pages & Classes. This was due to the unusual structure of this referred property not automatically having the necessary links to retrieve the necessary pages and classes, and handling has been added for this special scenario.
SR-A16432 · Issue 232172
Repaired Parse-Byte-Pos in File Listener
Resolved in Pega Version 7.2.1
Due to missing encoding for the type, files in byte format caused a NPE in file listener. This has been fixed.
SR-A16449 · Issue 234627
Java Mail API updated
Resolved in Pega Version 7.2.1
A bug in the Java Mail API 1.5.2 jar caused intermittent failures in receiving email. The API has been updated to the 1.5.3 jar.
SR-A16535 · Issue 231740
Null Boolean and datetime properties passed in command line extraction
Resolved in Pega Version 7.2.1
If a Boolean or a datetime Embedded valuelist /valuegroup /pagelist/page group property was in the WO blob but has no value when extracted from the command line using the -B and -J options, the value in the extract was not valid. This was traced to the handling for empty Boolean and datetime properties, and these properties will now be passed without modification when using the command line options -B and -J in XML output format or when running the extract from the UI.
SR-A16638 · Issue 233607
Changed edit control to prevent Google Chrome adding zeroes when localizing
Resolved in Pega Version 7.2.1
When using Google Chrome in some locales, zeros were being added to values in the skin and corrupting entered values. This was due to Google Chrome defaulting to localizing input type numbers, which caused dual localization after the control had already localized the value after reload. When input type is text, only the control localization will happen, so a workaround for Google Chrome has been added where the type of control has bene changed to text in the editable mode for the pyItemAlignment section.
SR-A16698 · Issue 232105
Support added for MSSQL datatype MONEY
Resolved in Pega Version 7.2.1
After upgrade, generating report definitions failed if the DB contained tables with columns that used the MSSQL-specific type MONEY, generating the error "No enum const class com.pega.pegarules.data.external.rd.constants.ColumnType.MONEY". Support has now been added for this datatype.
SR-A16804 · Issue 244041
Fixed premature execution of export confirmation in Microsoft Internet Explorer
Resolved in Pega Version 7.2.1
Clicking on the 'Export to Excel' open/save file popup in Microsoft Internet Explorer before it changed color to signify readiness generated the error "unable to read." This has been corrected so the button will not execute until the data is ready.
SR-A16849 · Issue 232859
Trimmed BIX logging unless debug enabled
Resolved in Pega Version 7.2.1
In order to improve performance, the statement "Node level information will not be added to the manifest when getAllProperties is selected in the extract rule form for XML extraction" (previously logged every time the XML output format has Include Manifest and Get All Properties checked) will only be printed in the logs if debug mode is enabled for ExtractImpl .