SR-A20634 · Issue 248378
Added handling for missing blob from external data class
Resolved in Pega Version 7.2.1
When using an external data class, an error was generated complaining of "trying to retrieve property pxInsHandle from a fully exposed table that does not contain it". This happened because the external table did not have a blob column but did have pxObjClass and pzInsKey, and handling has been added to correct this.
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-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.
INC-186395 · Issue 677205
Updating handling for for Pega-supplied operators with MFA
Resolved in Pega Version 8.7
When a site is blocking prweb and using prweb/PRAuth for login with MFA enabled, admin user id logins failed and MFA showed the error screen for Pega-supplied users. This was due to MFA verification not being configured for Pega-supplied operators, and has been resolved by adding an Adminstrator condition to skip MFA for for Pega-supplied operators.
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-A18694 · Issue 246976
Method changed for locating Word Templates folder
Resolved in Pega Version 7.2.1
The method used to obtain the Word templates folder always lower cases the folder path, but this poses a problem for the Turkish locale when the path contains capital I with no dot. Turkish has two variants of I - one with dot and one without dot. To resolve this, the Office templates folder path will be determined based on a combination of certain registry keys dependent on the Word version.
INC-175595 · Issue 652831
Java Bean import updated to handling differences in Java 7 and Java 8
Resolved in Pega Version 8.7
The behavior of the java bean Introspector class is inconsistent across different versions of the JDK when detecting indexed properties built off of java.util.List objects, causing Java Bean import to generate differently in Java 7 and Java 8. This has been resolved by updating PRIndexedPropertyDescriptor to better handle this JDK difference by resolving indexed read and write methods manually using simple reflection.
SR-A16938 · Issue 232832
Hardcoded DDL date replaced with dynamic string for Postgres compatibility
Resolved in Pega Version 7.2.1
The PostgreSQL DDL generator for install and upgrade in PRPC 7.1.9 created a PL/pgSQL containing the direct date value "01/01/1990". In some versions of Postgres 9.3, this caused a datestyle mismatch execution error when datestyle was set to "iso, ymd" on the postgresql.conf side. This has been resolved by replacing the hardcoded date value with a to_date function that uses an appropriate format string.
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.
INC-174716 · Issue 656441
Updated handling for validating/saving circumstanced rule on branch
Resolved in Pega Version 8.7
Using 'save as' for an already circumstanced rule with a new property/template caused the Rule-.DictionaryValidation activity to register the error "StandardValidate-CircumPropAlreadyDefined". The same activity Step did not throw an error when saving into Branch. This was traced to the ruleset name not being the same for the branch ruleset due to having _BRANCH_Branch-Name appended to its name, and has been resolved by adding a condition to check for circumstanced rule in a branch.