Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

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

SR-A2519 · Issue 210033

Added check for assembler handling after upgrade

Resolved in Pega Version 7.2

Due to differences in assembler versions, some SOAP services were not properly executing after upgrade and exhibiting record mapping inconsistencies. A check has been added to call the switchtooldassembler function if appropriate, resolving this problem.

SR-A4641 · Issue 211783

Added handling for null values in JSON

Resolved in Pega Version 7.2

When attempting to serialize a property of type Boolean or Number, a null value caused empty value mapping in the JSON stream (expected is {"Name":null}, but the result is {"Name":} thereby resulting in incorrect JSON). This has been resolved by modifying getPropertyAsJson() of ServiceHelper.java to stream "null" value (without quotes) when a scalar property (of type other than Text) exists in clipboard with an empty/null value. Properties assigned with null objects are considered and shown in the JSON response as below: Ex: {"pyLongDescription":"null","pyauto":"null","pyDueBy":"null"}

SR-A3789 · Issue 212055

Corrected Chinese font PDF margin errors

Resolved in Pega Version 7.2

PDFs generated using Chinese fonts had margin errors that truncated content. To correct this, the htmlWidth will be handled as a parameter and not a fixed value.

SR-A3610 · Issue 217555

Corrected ParseXML clipboard mapping

Resolved in Pega Version 7.2

The ParseXML rule was not correctly mapping data to the clipboard after upgrade. This was a regression: the design limitations of the new parse rule caused an issue with calling child parse rules on the fly based on the context page, and has been fixed by parameterizing the override class of the new parse rule.

SR-A3992 · Issue 212220

Fixed appendment handling for ComplexType elements

Resolved in Pega Version 7.2

If an element was of ComplexType, the attributes were appended before the sequence of elements are appended; this has been corrected.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us