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-D30505 · Issue 501895

Revalidate and save works for Service Packages using OAuth2.0

Resolved in Pega Version 8.2.3

Revalidate and Save was failing for service packages of type Data-Admin-ServicePackage which used authentication type as OAuth2.0 . If this was modified to basic authentication / unchecking authentication, revalidate and save was successful. Historically, the implementation of pzOnlyRestServiceType always assumed the primary page was the Service Package rule itself. To support this alternate use, the logic has been updated and a check of the Service Type has been added for the pxResults of the data page.

SR-D22468 · Issue 502036

Bix extract performance improved by only checking cipher type for encrypted properties

Resolved in Pega Version 8.2.3

Previously, if no cipher was configured in extract Rules the cipher type defaulted to null and wasn't cached. This caused performance issues when running against the database. In order to improve performance, the code has been modified to only check for cipher type if the property is encrypted.

SR-D28538 · Issue 502057

Corrected requestor status flag for direct map

Resolved in Pega Version 8.2.3

Numerous "Unable to create requestor" alerts were logged. This was traced to an error in HttpAPI where after retrieving the requestor from the internal requestor map directly, the requestor creation status flag was not set properly. This caused last action to post that alert instead of the correct notice of "existing requestor retrieved". This has been resolved so the flag reflects the correct status.

SR-D33052 · Issue 502062

Blank space removed in email reply

Resolved in Pega Version 8.2.3

An issue with blank space being added between the CSR icon and the email content for the first customer mail has been resolved by setting the window width to 100%.

SR-D25711 · Issue 502135

Updated dependent role validation during rule deletion

Resolved in Pega Version 8.2.3

After checking out and attempting to private-edit the "PegaRULES:WorkMgr4" AR, the rule was still shown as checked out after the edit was discarded. This was a missed use case, as Private checkouts are generally not enabled for most of the customer rulesets. To resolve this, roles in private checkout and branch rulesets will be excluded from going through dependent role validation during rule deletion.

SR-D31066 · Issue 502253

Improved performance for "Show-HTML" in a grid with numerous controls

Resolved in Pega Version 8.2.3

‘Show-HTML’ was taking an excessive amount of time to render a UI for grid with a large number of controls. This was traced to the handling for generating and clearing markup creating an exponential growth situation, and has been resolved by modifying the system to remove redundant copies of a string in the markup string buffer.

SR-D33096 · Issue 502741

pzGetURLHashes returns proper content-type

Resolved in Pega Version 8.2.3

When using an environment set with X-Content-Type-Options:nosniff, the response from pzGetURLHashes was returned with text/html response type and the mashup would not load due to browser exception "MIME Type ('text/html')is not excutable, and strict MIME type checking is enabled." In order to support CORB mitigation in the browser, the javascript content type will be set in the response header for pzGetURLHashes call.

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