SR-A93912 · Issue 264848
SSLUtils modified to support app container keystore/truststore
Resolved in Pega Version 7.2.2
Keystore and truststore configured at application container level were not being used by SOAP Connectors. To facilitate use, when SSL settings are not provided at a rule level SSLUtils will create a wrapper around the Java default SSL artifact and use that.
SR-A93593 · Issue 260733
Cross Origin mashup request fixed for Microsoft Internet Explorer /Safari
Resolved in Pega Version 7.2.2
When the mashup code hosted in domain1 was trying to access the PRPC content hosted in domain2, it failed when using Microsoft Internet Explorer and Safari but worked in Google Chrome. For a HTTP request whose response status is 303, the response headers given using Dynamic system setting "http/responseHeaders" were not being sent. This has been corrected.
SR-A92015 · Issue 260437
MobileSnapStart portal works with OpenWork
Resolved in Pega Version 7.2.2
When using pyMobileSnapStart and openWorkByHandle, the portal was displaying along with the case. However, any portal action that went through OnDesktopAction failed even though actions within the case were working. This was an issue with Portal actions not working when using openWork, and has been fixed with an added null check for docsRecreateInfo in dynamiccontainer_lite js to handle pyMobileSnapStart cases.
SR-A89295 · Issue 258931
Result count option added to Campaigns for performance tuning
Resolved in Pega Version 7.2.2
Slowness was seen when launching and running Field Marketing Campaigns. This was an issue with loading results using pxRetrieveReportData with paging enabled, as it fetched the total result count for each page. To resolve this, an option has been added to pxRetrieveReportData to disable fetching of total result count. This is available as Embed-QueryInputs property of type TrueFalse called 'pyReturnResultCount' when running report using pxRetrieveSearchData's pyReportParamPageName Parameter.
SR-A100923 · Issue 269979
Property null check added to TrackSecurityChanges
Resolved in Pega Version 7.2.2
When using the out-of-the-box TrackSecurityChangesLogic activity in an application to track the property changes, an Null Pointer Error was generated when saving the property. This was due to a missing null check for the property, and has been fixed.
SR-A94690 · Issue 261686
Report Editor displays Associations
Resolved in Pega Version 7.2.2
When using a custom activity to display properties in the data explorer, the "More" link is not displaying the associations when added. This was an error in the logic which determined whether pyReportEditorProperties exists for the class or not, and has been fixed in pzGetCustomPropsForTreeGrid.
SR-A39964 · Issue 259183
Corrected unexpected rounding of decimal property
Resolved in Pega Version 7.2.2
Decimal value was incorrectly being rounded in the control for a decimal property which has Use Validate in place. This happened when the edit validate rule on the property failed and was then formatted using Double instead of BigDecimal. This has been fixed by updating the pxNumber control generation logic in the pzGenerateTextInput RUF to use BigDecimal instead of Double.
SR-A39964 · Issue 265562
Corrected unexpected rounding of decimal property
Resolved in Pega Version 7.2.2
Decimal value was incorrectly being rounded in the control for a decimal property which has Use Validate in place. This happened when the edit validate rule on the property failed and was then formatted using Double instead of BigDecimal. This has been fixed by updating the pxNumber control generation logic in the pzGenerateTextInput RUF to use BigDecimal instead of Double.
SR-A67007 · Issue 255075
Catch improved to close Message Explorer connections
Resolved in Pega Version 7.2.2
When using the Message Explorer functionality provided on the JMS Connect rule form, it only allows a number invocations equal to the size of the connection pool. Due to an issue with releasing the connections when using Resource Reference mode or IIOP protocol, the pool was being exceeded and the error "Couldn't create connection object" appeared. This has been fixed by changing the conditional catch for closing the connection with a more effective try catch.
SR-A89677 · Issue 257766
Removed erroneous warning from auto-created DataType reports
Resolved in Pega Version 7.2.2
When creating a data type and local source, a report definition is automatically generated for the data type. That report definition contains the warning "Using a custom HTML control to format a column may result in poor performance displaying query results. Consider using auto-generated HTML controls." This was confusing, creating the unintended assumption that something was wrong with the automatically generated report. To clarify this, the warning will not be displayed when the rule is created automatically.