SR-D50016 · Issue 515903
Exception stack trace will be included as comments in generated assembly code
Resolved in Pega Version 8.2.5
When there is an exception during assembly time, that original exception message is assembled in the generated code. To improve the process of finding the the root cause by examining the original exception stack, the system has been updated to insert the original exception stack trace into the generated code as comments.
SR-D50161 · Issue 514822
Auto populate disabled during redux page conversion to prevent concurrent modification exception
Resolved in Pega Version 8.2.5
Running a standalone data page sourced from a look up of a class was failing sporadically with a concurrent modification exception. The Data page was backed by redux pages: this meant that when the page fetched from data source was converted to redux page, it was iterating through all properties in the mContent of the page and trying to convert those to redux properties. During this process, when any auto populate property was encountered it was getting triggered and modifying the mContent, resulting in a change in iterator. As a result, when the Iterator was trying to fetch the next element, the concurrent modification exception was thrown. To resolve this issue, auto populate has been disabled during redux page conversion to avoid unnecessary problem during data page load.
SR-D50436 · Issue 513849
Case creation service activity unauthorized response modified
Resolved in Pega Version 8.2.5
When unauthorized users accessed the URL for creating a case, a blank screen appeared instead of the user being routed to a login screen. This was due to the system returning an HTTP 400 error instead of HTTP 401 response, and was traced to the introduction of an anonymous user type in the authentication activity (Authentication service in the service package). Case creation REST service uses pzCreateCase activity to create the cases, but before introducing the anonymous user type it was exiting from the authentication activity and did not call pzCreateCase. This was traced to the error handling relying on a field value to be in English when instead the site had localized the value, causing a mismatch which did not generate the necessary failed status. To avoid this, the system will now use the new pxStatusFlowSecurity process engine status instead of relying on a text match to determine this error.
SR-D50793 · Issue 514258
PegaEmailClient Debug level EmailAccount password issue resolved
Resolved in Pega Version 8.2.5
The SendEmailNotification activity was failing to send email when DEBUG log level was enabled for the com.pega.platform.integrationengine.client.email.PegaEmailClient class. This was traced to the removal of the pyPassword property from the copied object which was done for security reasons, but which is this case led to failed authentication. This has been resolved.
SR-D56079 · Issue 517628
Content type added to Httpclientutils
Resolved in Pega Version 8.2.5
The XML Response received from Connect HTTP Service was being converted to Base64 format automatically. This was traced to there not being a content type in the response header from the service, causing the content to be treated as binary and encoded before being mapped to the clipboard. To correct this, content type has been added to Httpclientutils.
SR-A9699 · Issue 221149
Added handling for CR/LF in imported CSV file
Resolved in Pega Version 7.2
Importing a file failed with a java.lang.StringIndexOutOfBoundsException. On the end user side, the dialog box read 'Uploading...' and then clears the input file name. This was a problem with new line characters within the CSV fields: while importing the file, these new line characters were treated incorrectly and parsed as the end of a row in CSV To correct this, the fields containing new line characters will be enclosed in double quotes while exporting. The import parsing logic was also changed to handle new line characters within the fields.
SR-A8242 · Issue 218454
Check added for double encoded quotes in imported CSV
Resolved in Pega Version 7.2
When the content in a CSV file contained double quotes, it was parsed incorrectly during import if it had been previously edited and saved in Excel. This was due to a double encoding of the quotes, and a check has been added to handle such doubling if it is present in the file.
SR-A6467 · Issue 216163
Check added for externally mapped DB tables during import
Resolved in Pega Version 7.2
While using import/export functionality in the Records tab of Data Designer, the import of the CSV file failed with a DB error due to additional create/update properties being added which did not have corresponding columns for externally mapped tables. To resolve this, the system will check whether the current data type is externally mapped and the create/update properties will not be added to the record in cases where it is an externally mapped table.
SR-A6399 · Issue 219922
Data type local store enhanced to work with multiple opened ruleset
Resolved in Pega Version 7.2
It is a common practice in many complex delivery environments to have two ruleset versions opened simultaneously. However, this can cause issues and errors when work is happening in two different major versions while running the local data storage and the RD is created in the highest open major version. In order to support this dual-ruleset use, the highest open rule set version will be fetched from the list of ruleset versions which are available to the application. RD and data pages will be created in this ruleset version. Following files are modified: pzGenerateDataPages pzGenerateListDataPage pzGenerateLookupDataPage pzGenerateRD pzSetDatatypeContextSettings
SR-A6399 · Issue 220402
Data type local store enhanced to work with multiple opened ruleset
Resolved in Pega Version 7.2
It is a common practice in many complex delivery environments to have two ruleset versions opened simultaneously. However, this can cause issues and errors when work is happening in two different major versions while running the local data storage and the RD is created in the highest open major version. In order to support this dual-ruleset use, the highest open rule set version will be fetched from the list of ruleset versions which are available to the application. RD and data pages will be created in this ruleset version. Following files are modified: pzGenerateDataPages pzGenerateListDataPage pzGenerateLookupDataPage pzGenerateRD pzSetDatatypeContextSettings