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-A100816 · Issue 268476

MinimumAgeForProcessing honored when requeuing Broken-Process

Resolved in Pega Version 7.2.2

When using the Requeue feature from SMA, queue items were not honoring the existing (previously used) value of pyMinimumAgeForProcessing, instead setting the value as -1 so, all attempts were happening immediately. This was an issue with the Repair API in QueueManagerImpl not honoring minimumAgeForProcessing if MinimumDateForProcessing already existed in the queue item, and has been fixed.

SR-A77555 · Issue 259289

Improved handling for multiple access 'when' in business event processing

Resolved in Pega Version 7.2.2

It was possible to encounter a missing page in the business event processing if event processing performed a call to tools.getThread().getAuthorization().haveAccess in multiple activities and there were several access 'when' actions defined for the class. The access 'when' requires that a work page be present to evaluate against, and depending on how the call was being performed or if passivation has occurred the process could throw an IndeterminateConditionalException and pass a null as parameter value for "aPage" parameter. To prevent this error, the activities pxCreateSummary and pxGetPrimaryClasses have been changed to pass the ClipboardPage of class for which haveAccess() is being called.

SR-A77555 · Issue 260161

Improved handling for multiple access 'when' in business event processing

Resolved in Pega Version 7.2.2

It was possible to encounter a missing page in the business event processing if event processing performed a call to tools.getThread().getAuthorization().haveAccess in multiple activities and there were several access 'when' actions defined for the class. The access 'when' requires that a work page be present to evaluate against, and depending on how the call was being performed or if passivation has occurred the process could throw an IndeterminateConditionalException and pass a null as parameter value for "aPage" parameter. To prevent this error, the activities pxCreateSummary and pxGetPrimaryClasses have been changed to pass the ClipboardPage of class for which haveAccess() is being called.

SR-A93593 · Issue 260733

Cross Origin mashup request fixed for Microsoft Internet Explorer /Safari

Resolved in Pega Version 7.2.2

When the mashup code hosted in domain1 was trying to access the PRPC content hosted in domain2, it failed when using Microsoft Internet Explorer and Safari but worked in Google Chrome. For a HTTP request whose response status is 303, the response headers given using Dynamic system setting "http/responseHeaders" were not being sent. This has been corrected.

SR-A100923 · Issue 269979

Property null check added to TrackSecurityChanges

Resolved in Pega Version 7.2.2

When using the out-of-the-box TrackSecurityChangesLogic activity in an application to track the property changes, an Null Pointer Error was generated when saving the property. This was due to a missing null check for the property, and has been fixed.

SR-A67932 · Issue 251208

Blank query field in Bulk Actions defaults to none instead of all

Resolved in Pega Version 7.2.2

Due to the MyCheckedOutRulesBulk Listview not adding a default 'when' condition in the query when the query value was blank, using Bulk Actions -> Select All would return a list of all non-resolved rules in the system rather than the expected value of 'none' for the list of checked rules for the bulk processing tool. This has been resolved.

SR-A99155 · Issue 253246

Mobile dirty page handling corrected

Resolved in Pega Version 7.2.2

When the "X" (Close) icon was clicked in the Mobile Create Opportunity/Lead/Contact form and then the cancel button in the prompt popup was clicked, the same page returned and the app went into infinite loading mode. This was caused by a missed use case; when the document is found to be dirty and user decides to stay on the page, the code just returned. This has been fixed.

SR-A92219 · Issue 259481

XSD file contains classes extracted with -c flag

Resolved in Pega Version 7.2.2

When executing a BIX extract to XML using the -c flag, the XML file contained outer tags but the corresponding XSD file did not. This has been corrected.

SR-A76408 · Issue 252207

Additional options added to configure VPD data pages

Resolved in Pega Version 7.2.2

It was previously only possible to configure 'customInfoDataPage' for VPDs through prconfig. This enhancement allows an application developer using Oracle and Enterprise DB to use D-A-S-S or JNDI to pass a customizable set of property values to the DB when a connection is established to the DB so that a SQL statement can be run. The primary use case for this feature is the ability to implement unbreakable object-level security for all data access from a Pega application by defining Virtual Private Databases (VPDs) on class tables that reference this information, for Pega DBMS that support VPDs.

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.

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