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-B65837 · Issue 317187

Handling added for blanks when copying parameter pages

Resolved in Pega Version 7.3.1

After Configuring a Call-Asynch-Activity method step on an activity and refreshing the ruleform, the name of the activity being called in the method was no longer shown. To correct this, a 'when' condition has been added to the pzAddAdditionalMethodParameter activity to handle blank pages when copying parameter pages to pyStepsParamUI pages.

SR-B67171 · Issue 317155

Handling added for blanks when copying parameter pages

Resolved in Pega Version 7.3.1

After Configuring a Call-Asynch-Activity method step on an activity and refreshing the ruleform, the name of the activity being called in the method was no longer shown. To correct this, a 'when' condition has been added to the pzAddAdditionalMethodParameter activity to handle blank pages when copying parameter pages to pyStepsParamUI pages.

SR-B68818 · Issue 318268

Corrected section refresh when target section is not in DOM

Resolved in Pega Version 7.3.1

An empty composite tab was displayed after processing a service case due to a reload section request being triggered for the CPMCompositesContainer section that was included in the first tab of the layout group. To resolve this, the system will ignore a refresh client expression if the target section is not in DOM.

SR-B68818 · Issue 316252

Corrected section refresh when target section is not in DOM

Resolved in Pega Version 7.3.1

An empty composite tab was displayed after processing a service case due to a reload section request being triggered for the CPMCompositesContainer section that was included in the first tab of the layout group. To resolve this, the system will ignore a refresh client expression if the target section is not in DOM.

SR-B67327 · Issue 317826

pxUrgencyWorkStageSLA properly resets when no SLA on next stage

Resolved in Pega Version 7.3.1

pxUrgencyWorkStageSLA was not being reset when the next stage did not have an SLA. This has been resolved.

INC-185847 · Issue 669526

Handling added for disabling weekends when no weekends are available

Resolved in Pega Version 8.7

A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance.

INC-211911 · Issue 713052

Able to expand rows when other rows are expanded

Resolved in Pega Version 8.7.2

When multiExpand, threadProcessing, and readonly flags were true, attempting to expand multiple rows at the same time collapsed already opened rows and generated an error indicating "target is not defined". This was caused by 'handleEditItem' not calling the collapse functionality for an opened row correctly, and has been resolved by adding a check which allows the expansion of multiple rows for readOnly details.

INC-212623 · Issue 709550

Dropdown label is accessible when combined with placeholder or tooltip

Resolved in Pega Version 8.7.2

The screenreader was not reading the dropdown label if tooltips or placeholders were added to the dropdown. This was caused by the label of the element being overwritten, and has been resolved by replacing aria-label with aria-describedby on the input element.

SR-D29809 · Issue 505256

Extra <p> tag removed when not needed in RTE generation

Resolved in Pega Version 8.2.4

The RTE was generating an extra <p> tag in the Review harness or when the RTE was non-editable, causing alignment issues in the UI when RTE was displayed using inline dynamic layout with a textarea. This has been corrected.

SR-B49696 · Issue 310805

Enhanced decision tree config using symbols

Resolved in Pega Version 7.3.1

A decision tree with multiple conditions configured using "||" and "&&" symbols resulted in the wrong outputs being returned at run time. Handling has been added to support these symbols in this use.

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