SR-A13184 · Issue 230179
Corrected count mismatch in compared XML outputs
Resolved in Pega Version 7.2.1
A count mismatch between the XML output file and the manifest file for XML output format for embedded page list properties has been resolved to ensure accurate reporting.
SR-A13184 · Issue 229061
Corrected count mismatch in compared XML outputs
Resolved in Pega Version 7.2.1
A count mismatch between the XML output file and the manifest file for XML output format for embedded page list properties has been resolved to ensure accurate reporting.
SR-A13187 · Issue 226047
JSON mapping performance enhanced
Resolved in Pega Version 7.2.1
JSON mapping performance has been enhanced with the addition of a native JSON property cache along with the introduction of a DSS to skip all unnecessary intensive checks if the JSON node name is found to be valid. This will be handled through a DSS JSON/useNativeAPI which when set uses adoptJSONObject/adoptJSONArray() as the API for inbound JSON parsing. Please note that if the DSS is set, homogeneous arrays are only supported with valuelist configuration in connectors. Heterogeneous arrays are not supported when DSS is set.
SR-A13590 · Issue 239611
Updated handling for Cyrillic usernames
Resolved in Pega Version 7.2.1
On systems where Windows user name was created in Cyrillic (ex C:\Users\?????? ????), generated word documents would be empty due to the characters in the directory name not being properly handled. The system now contains modified Silverlight code that will read the registry keys using RegOpenKeyEx, RegQueryValueEx and RegCloseKey functions of advapi32.dll as opposed to previously used RegRead function of Wscript.shell. These new registry functions are Unicode-aware. The Silverlight Prerequisites installer has also been modified to include the latest certificate.
SR-A13729 · Issue 231588
Embedded Valuelist/valuegroup count included in manifest file
Resolved in Pega Version 7.2.1
The pxTotalInsertsCount for Embedded ValueList /ValueGroup Property was missing in the Manifest file while the pxTotalInsertsCount for Toplevel ValueList /ValueGroup Property was present. The Embedded Valuelist/valuegroup property count will now be included as expected.
SR-A13926 · Issue 230498
Resolved invalid page causing missing bulk items
Resolved in Pega Version 7.2.1
When trying to perform bulk transfer, some of the work objects were sporadically not displayed in the bulk processing list. This was caused by an invalid page getting passed while invoking checkActionWhens to act on the 'when' for showing the assignments list. The proper page is now set by updating the GETBULKPROCESSCONTENT activity to set pxRefObjectKey to the assignment page while invoking checkActionWhens.
SR-A14004 · Issue 231765
Flow designer XML fixed when using copy/paste
Resolved in Pega Version 7.2.1
Copy and paste are available in the Flow Designer, but tickets where the End shape was copy/pasted and a new ticket set created for the new End shape resulted in incorrect XML. To correct this, the flowmethodbody function will use pyTicketShapes instead of pyModifierRefs for java generation.
SR-A14014 · Issue 227004
HTTP Connector API will dynamically set TLS protocol
Resolved in Pega Version 7.2.1
The HTTP Connector was failing to connect using TLS v1.2 protocol due to the SSL Protocol being hardcoded to TLS while setting SSLContext. To fix this, the system will not pass the protocol while instantiating SSLContext, but will leave it to the API to set to highest protocol from JRE.
SR-A14106 · Issue 227981
Improved sender handling for custom email activities
Resolved in Pega Version 7.2.1
A custom email related activity was producing an authentication exception due to an attempted call to a User ID stored in Param.FromUsername made after that parameter was cleared by SendEmailNotification. To avoid this, if Param.FromUsername is blank, it will be set to the value of Param.AccountID.
SR-A14108 · Issue 242466
Better handling for rules considered duplicates
Resolved in Pega Version 7.2.1
A legacy API was not properly resolving rules present in an earlier ruleset version, leading to the creation of additional rules. The system will now consider rules already present in the earlier ruleset version and present the Other duplicate screen asking to skip, overwrite, or rename the rule.