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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-B72669 · Issue 326687

FinishAssignment updated for offline mobile reports

Resolved in Pega Version 7.3.1

When a submitted report was saved in offline mode and then retrieved from the client store, the system seemed to only retrieve the N-1 version of the work object. Analysis showed that the call to open the object after being submitted only opened the first transaction and not the last transaction recorded for the case, and the issue was traced to Finish Assignment not saving the updated work-object to the client-store. To fix this, the system will call saveWorkAndAssignment in gotAFlow defined inside finishAssignment when "no next action".

SR-B36794 · Issue 322533

Added reindex check to RuleCheckin

Resolved in Pega Version 7.3.1

After creating new proposition data and saving it, pyPropertyReferences were changing on save of the Decision Data rule. Analysis identified the issue as happening when a rule was privately edited from a locked ruleset version and then checked in into another ruleset/version: rule references were created for the privately edited copy but when the privately edited copy was deleted at step 29, the references were also deleted and since the item being checked in was deleted in the same transaction the commit did not trigger reindexing and the references were not created again. To handle this edge case, a step has been added to the RuleCheckIn activity to reindex if .pzIsPrivateCheckOut == "true" && .

SR-B51112 · Issue 307512

Silverlight MSI file rebuilt without registry keys for bulk installation use

Resolved in Pega Version 7.3.1

MS Word Compatibility for 2016 Office 365 was generating messages like "Error in updating the Registry Key of (AllowLaunchOfElevatedTrustApps): Object reference not set to an instance of an object." This was due to a newly-added registry keys inclusion feature on Silverlight prerequisites that not supported for installing multiple systems. To address this, the Silverlight prerequisites MSI file has been re-built without the inclusion of registry keys

SR-B52083 · Issue 315414

Scrolling does not select checkboxes/buttons

Resolved in Pega Version 7.3.1

Radio buttons and checkboxes were becoming selected inadvertently while scrolling due to a touch events error. This has been fixed by setting the system to ignore a touch event when target is radio or checkbox while scrolling.

SR-B57228 · Issue 325976

Timer exit error fixed for STS SOAP

Resolved in Pega Version 7.3.1

If STS was enabled for a SOAP Connector and if a valid STS token was already available, hundreds of error messages about attempting to stop the timer were logged. This was traced to a step order error which started the timer and then exited before stopping it, and the missing step has been added.

SR-B70379 · Issue 326388

Post-printing screenshot window freeze fixed

Resolved in Pega Version 7.3.1

When an attached screenshot was clicked open and displayed in a pop-up window, the window was freezing after a print operation was performed. This was an issue with closing the ActiveX control through Microsoft Internet Explorer. To resolve this, the ActiveX control previously used has been changed to Silverlight.

SR-B74878 · Issue 325216

Circumstanced table lookup enhanced

Resolved in Pega Version 7.3.1

When editing delegated circumstanced versions of a Decision Table, every circumstanced version brought up the first circumstanced version of the rule instead of an exact match. To resolve this, pzGetResolvedCircumstancedRule has been modified to match all the parameters for circumstancing (Value, Property, Date property, Date value, Start, End date) to find the true match.

SR-B75677 · Issue 326354

Password set removed from Lock and Roll tool

Resolved in Pega Version 7.3.1

The way the Lock and Roll tool set passwords was confusing and often caused a new application to be created with the wrong password, preventing updating the new rule or even requiring administrators to manually create the application rules. To resolve this, pzLPLockAndRollApplication has been changed to remove the setting of pySetPassword and pySetPasswordConfirmText so the values will be empty for the new version.

SR-B77148 · Issue 325930

Handling added for importing PostgreSQL database Application Bundles

Resolved in Pega Version 7.3.1

Application Bundle imports were failing on db2/MSSQL systems due to syntax differences, generating the message "FATAL ERROR: Encountered an issue applying DDL". Postgres database view definitions include ":: and character varying", but other databases do not require those characters. To ensure compatibility when importing the archives to non-Postgres databases from the Postgres instance, "character varying" will be removed through removeTypeCastingFromPostgreSQL in databaseschemaUtils. It will not be removed for import to another Postgres system.

SR-B77536 · Issue 326544

Check added to keep "::" in imports between PostgreSQL systems

Resolved in Pega Version 7.3.1

Application Bundle imports were failing on db2/MSSQL systems due to syntax differences, generating the message "FATAL ERROR: Encountered an issue applying DDL". Postgres database view definitions include ":: and character varying", but other databases do not require those characters. To ensure compatibility when importing the archives to non-Postgres databases from the Postgres instance, "character varying" will be removed through removeTypeCastingFromPostgreSQL in databaseschemaUtils. It will not be removed for import to another Postgres system.

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