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-B426 · Issue 271503

Error label highlighting corrected for inside grid

Resolved in Pega Version 7.2.2

The correct label associated with the UI element in which the client side error was thrown was not highlighted when inside a grid. To fix this, the function findLabelFor has been updated to handle the case specific to the grid, as the error elements ID and the label's 'for' attribute were never equal due to the 'for' attribute changing value when used on repeating elements within a grid.

SR-A92731 · Issue 264546

Localization wizard correctly narrows to only rulesets

Resolved in Pega Version 7.2.2

Despite narrowing the localization wizard to select only rulesets, platform rules and messages ere also picked. This has been corrected by modifying the logic in the pzGetCLassLabels activity to only get populated rulesets when this filter is used.

SR-A24962 · Issue 250080

DataSet-Execute updated to correct time-to-live error

Resolved in Pega Version 7.2.2

When using the time to live option of a Decision Data Store dataset, the java generation for the DataSet-Execute method was causing java compilation errors. This was due to an inconsistency between the code generation for DataSet-Execute method in an activity and the settings provided. To correct this, the algorithm used to generate the code for DataSet-Execute method has been updated to include the time to live setting and to generate correct and compilable code.

SR-A24962 · Issue 248678

DataSet-Execute updated to correct time-to-live error

Resolved in Pega Version 7.2.2

When using the time to live option of a Decision Data Store dataset, the java generation for the DataSet-Execute method was causing java compilation errors. This was due to an inconsistency between the code generation for DataSet-Execute method in an activity and the settings provided. To correct this, the algorithm used to generate the code for DataSet-Execute method has been updated to include the time to live setting and to generate correct and compilable code.

INC-142557 · Issue 600528

Accessibility added to Recents

Resolved in Pega Version 8.5.2

Under all recent items, the work object was not opened when using the keyboard and the focus was on the work object. Clicking with the mouse worked. Investigation showed that on pressing the enter key, actions were not triggered because the action string was not on the same SPAN tag (but in child node). This has been resolved with an update to add tabindex on the same span where action-string is added. In addition, accessibility was not enabled on the out-of-the-box Recents table because the work object elements in the table used a formatted text control; this has been updated to use a link control which will enable the accessibility feature while using keyboard navigation.

INC-142557 · Issue 600532

Accessibility added to Recents

Resolved in Pega Version 8.4.4

Under all recent items, the work object was not opened when using the keyboard and the focus was on the work object. Clicking with the mouse worked. Investigation showed that on pressing the enter key, actions were not triggered because the action string was not on the same SPAN tag (but in child node). This has been resolved with an update to add tabindex on the same span where action-string is added. In addition, accessibility was not enabled on the out-of-the-box Recents table because the work object elements in the table used a formatted text control; this has been updated to use a link control which will enable the accessibility feature while using keyboard navigation.

INC-142557 · Issue 600529

Accessibility added to Recents

Resolved in Pega Version 8.4.4

Under all recent items, the work object was not opened when using the keyboard and the focus was on the work object. Clicking with the mouse worked. Investigation showed that on pressing the enter key, actions were not triggered because the action string was not on the same SPAN tag (but in child node). This has been resolved with an update to add tabindex on the same span where action-string is added. In addition, accessibility was not enabled on the out-of-the-box Recents table because the work object elements in the table used a formatted text control; this has been updated to use a link control which will enable the accessibility feature while using keyboard navigation.

INC-140101 · Issue 597637

System will attempt to decrypt data ending in "+"

Resolved in Pega Version 8.5.2

Encrypting and decrypting one specific email address was not working properly when showing on the UI. It was possible to force a decryption using decryptproperty, but Pega generated an error. This was due to the actual encrypted value ending with '+', which conflicted with a system check that skips decryption if the encrypted property value ends with + . To resolve this, the system will attempt to decrypt the property even when encryptedText ends with + .

SR-A82337 · Issue 256391

Optimized properties populated in exposed columns

Resolved in Pega Version 7.2.2

After using the property optimization wizard to expose a property in a higher class, the column was not populated with data for existing instances of lower classes that used that property even though the column population job ran on those classes. The column was also not populated when new instances of the lower classes were created. This was an issue where the API was using different update methods for optimized and regular properties, causing propagation problems. HandleSchemaUpdates has been modified to update the class map for all the classes mapped to the table instead of just the class name with which the API is invoked.

SR-A86522 · Issue 266946

ResumeFlow updated to handle SLA update in batch mode

Resolved in Pega Version 7.2.2

When any assignment configured with SLA was resumed by any agent in batch mode, the associated record in the pr_sys_queue_sla table was not getting deleted. To resolve this, the deletion method used in CompleteAssignment has been updated.

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