SR-A22458 · Issue 243317
Plus '+' sign encoding corrected in connect-HTTP
Resolved in Pega Version 7.2.1
Using connect-http get to send an encrypted string to the external endpoint was not working due to missing encoding for the plus '+' string. The encoding has now been fixed.
SR-A22722 · Issue 246998
pxDereferenceEndpoint Activity can be overridden by the customer
Resolved in Pega Version 7.2.1
The generic pxDereferenceEndpoint Activity that applies to the Rule-Connect-REST class was not the functionality desired by the customer, so they wanted to be able to change it, but it was set to ?Final? and couldn?t be changed. The availability of the pxDereferenceEndpoint Activity has now been set to ?Available? so that customers may override it in any RuleSet. (No logic changes have been made to this activity.)
SR-A22794 · Issue 245278
parseXML able to map multiple values
Resolved in Pega Version 7.2.1
In order to present more information for custom use, parseXML as been updated with a new pagelist property that can map multiple attribute values.
SR-A23050 · Issue 244774
Rule generation updated to handle related JSONs
Resolved in Pega Version 7.2.1
The system was failing to parse inbound JSONs when the corresponding Pega Data Model was generated using the same JSON, and was unable to use valuelist or pagelist properties for generating JSON to pass to connect-Rest Method. This generation and runtime of rest connector was failing when the same name property existed in multiple places with different modes and same levels. To support this use, the rule generation has been updated to correctly populate the qualifier name along with modified run time code to support mapping when same properties are there in the same class.
SR-A23527 · Issue 247288
Extension point added to enable/disable CMIS integration
Resolved in Pega Version 7.2.1
The implementation for the extension points of the CMIS integration to invoke other integration mechanisms (e.g. SOAP) that can bring the document back and forth from/to the DMS system were public (e.g. trigger pySaveContent, pyDeleteContent, activity pyRetrieveAttachmentContent, etc.) , but the actual 'when' rule needed to enable/disable the functionality was final. To correct this, a new py when rule has been added as an extension point, and pxCMISEnabled is used with it as an OR condition.
SR-A23694 · Issue 246996
Timeliness functions modified to return 0 in place of NULL
Resolved in Pega Version 7.2.1
The "Timeliness" function aliases returned NULL for all the CASE statements that returned false, but NULL value using the AVERAGE summarize function in a report definition returned an incorrect result. The following Function Aliases have been updated to return a 0 instead of NULL when the result is false: - pxSLAAgeByClassTimeliness - pxSLAAgeTimeliness - pxSLAHistoryTimeliness - pxSLAAssignTimeliness
SR-A23862 · Issue 246708
VPD Data Page passes custom properties
Resolved in Pega Version 7.2.1
When trying to set up Oracle VPD custom properties as instructed in a PDN article, an exception was generated due to missing handling for custom class/property definitions. The new pyCustomProperties if PageList has been added to Code-Pega-DBApplicationContext .
SR-A24183 · Issue 247604
Added visibility for XML Stream Rule Form fields
Resolved in Pega Version 7.2.1
The configurable fields "Stream Name" and "XML Type" have been made visible when "Mapping Mode" is "Apply Rule" in the XML Stream Rule Form.
SR-A5733 · Issue 235301
Excel editing fixed for delegated data tables
Resolved in Pega Version 7.2.1
An error was generated when attempting 'edit in Excel' on a delegated data table. This was due to an import/export error linked to a visibility condition, and has been corrected.
SR-A9921 · Issue 222554
Updated PDF generation to minimize font conversion temp file creation
Resolved in Pega Version 7.2.1
When HTML containing Chinese characters is converted to PDF using HTMLtoPDF, files like "+~JF690731093475584931.tmp" were created in the temp folder for each conversion and were not cleared after PDF is generated. This has been fixed by modifying the PDF utility to create only one fonts.properties file.