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-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.

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.

SR-B70652 · Issue 325760

Read operations updated for Datastax 3.1.x use

Resolved in Pega Version 7.3.1

In the 3.1.x Datastax driver reads are no longer retried by default. Therefore, the read operations have now been explicitly marked as idempotent to force the Datastax driver to retry timed out reads.

INC-177323 · Issue 672420

Search string wildcard use documentation updated

Resolved in Pega Version 8.7

The support article for the search API has been updated to clarify the ability to use the wildcard character "*" by manually adding it to the prefix of each term in the search string.

INC-173162 · Issue 650795

Certificate match will use Subject Distinguished Name

Resolved in Pega Version 8.7

Signature verification was failing due to the system not finding the matching root certificate for the chain. The root certificate was in the trust store, but the system found a different certificate first and that other certificate (an intermediate certificate) was not considered a valid certificate for validating the whole certificate chain. This was traced to filtering on the Issuer Distinguished Name (DN) instead of the Subject DN and was due to intermediate certificates potentially having the same Issuer as a root certificate (e.g. if that root certificate was used to create the intermediate certificate). To resolve this, an update has been made to check the Subject DN instead of Issuer DN.

INC-189047 · Issue 674759

Session timeout adjusted for use with Apple Safari

Resolved in Pega Version 8.7

A configured browser session logout timer was not working with the Apple Safari browser. This was traced to browser-specific handling for self.location.href and has been resolved by adjusting the logic and moving it inside a setTimeout to improve cross-browser compatibility.

SR-C89656 · Issue 426423

Case urgency value will not be reset when processing wait shapes

Resolved in Pega Version 8.2.1

When a Wait shape was configured with the ‘Users can choose to continue process’ option unchecked, the overall work object SLA urgency was overwritten to 0 when the SLA processed the Wait shape. This was due to the Wait shape using pzWaitTImer, which has all urgency values as 0. The SLA being set to 0 did not occur if ‘Users can choose to continue process’ was checked on the Wait shape because pxSystemFlow was not set to true in that case. To prevent the SLA override, a check has been added that will skip setting the urgency setting if there is a wait shape.

SR-C84921 · Issue 424317

Connection Manager uses keyring for null prconfig password

Resolved in Pega Version 8.2.1

After upgrade, credentials from BIX keyring were failing when using BIX via commandline rather than prconfig. This was traced to a behavior change in the Connection Manager, and has been resolved by modifying the Connection Manager to look up the password from the keyring when given a URL configuration where the password is null in prconfig (URL connection only).

INC-189259 · Issue 674820

Big Decimal used while converting List to Page

Resolved in Pega Version 8.7

Previous work done to handle precision numbers in the JSON response that were being rounded or truncated when parsed for the DataSource page has been updated to also handle the case of mapping a list to a page.

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