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.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-A7188 · Issue 215492

pzShowConflicts message localized

Resolved in Pega Version 7.2

Localization has been added for pzShowConflicts by adding the configurable field "pyMessageLabel.ShowConflictMessage".

SR-133255 · Issue 204955

Resolved NPE caused by outbound email call after wait shape

Resolved in Pega Version 7.2

After a wait shape, a NullPointerException was thrown when a work item was moved to the problem flow after a call to send an outbound email. Changes have been made to the "ProcessIndividualDepAssignment" activity and "FlowProblems" flow to correct this issue.

SR-A6363 · Issue 216182

Resolved Where AM I issue when there is flow on embedded page

Resolved in Pega Version 7.2

Clicking on the "Where Am I?" option when there was a subprocess defined on embedded page in a flow failed to display anything on screen and an error was logged. This was caused by the obj-open referring to the wrong flow class value, and has been corrected.

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-A6740 · Issue 214445

Bulk delete activity added for ADM models

Resolved in Pega Version 7.2

In order to support the deletion of ADM models in bulk, an enhancement has been added to remove the unwanted models from the database provided a list of them is given as input. The activity pxDeleteModelsByCriteria has been created; "Used to delete ADM models in bulk. Models to be deleted are determined by the criteria selected by this Activity's parameters; a model is deleted if it matches all selected criteria."

SR-A8236 · Issue 217334

Data flow respects vertical scalability settings

Resolved in Pega Version 7.2

The number of threads per node specified in Decision->Simulation Settings->Topology landing page was not taken into account by data flow execution, leading to the inability to configure vertical scalability per PRPC node and/or exclude certain nodes from data flow execution. This was an error where the configuration was being ignored and a default value was always used, and has been corrected.

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