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-A76381 · Issue 252811

Customizable when added for PegaPULSE delete button

Resolved in Pega Version 7.2.2

In order to support more customization, an enhancement has been added to hide the delete link on PegaPULSE entries based on conditional circumstances (i.e. entry is older than x hours). The overridable when rule 'pyCanDeletePost' has been provided and is referenced in the pzISCurrentUser when rule with AND condition to the existing condition.

SR-A24719 · Issue 252331

Correct Bulk processing status when no transfer occurs

Resolved in Pega Version 7.2.2

Searching by Work bulk processing was not transferring items when there were multiple assignments yet was showing a Transferred status and not displaying an error. This was traced to a missing 'when' condition check in the handling, and has been fixed.

SR-A67005 · Issue 251958

Work-.Close function updated to resolve "Flow not at task" error

Resolved in Pega Version 7.2.2

The Work-.Close function has been updated to improve synchronization between operators in cases where having a combined standard flow and screen flow as a sub flow could cause a "Flow not at task" error as one operator moved forward and the other subsequently tried to save an already open work object.

SR-A76914 · Issue 252778

Short Description parameter cleared every loop to ensure data integrity

Resolved in Pega Version 7.2.2

When adding the coverable work types in a case, the description which comes in the Actions menu was not correct due to the Short Description parameter not being cleared. This caused the same description to be used for the next flows. To fix this, the system will now clear the parameter Short Description in the activity LookupCoverableProcessList at the end of every loop, ensuring every flow takes its own short description.

SR-A24246 · Issue 248666

Event size difference on calendar corrected

Resolved in Pega Version 7.2.2

When using the out-of-the-box calendar gadget to display some events apart from the worklist goals and deadlines, an event shown on the calendar was correct in the monthly view but had the wrong time and duration in the daily view. This was traced to the way the height of the div tag was calculated in different functions, and has been corrected.

SR-A38578 · Issue 253239

Population handling added for null value flowType property

Resolved in Pega Version 7.2.2

While launching the case local action, a clipboard error was generated indicating the InternalStageFlow failed to find the named RULE-OBJ-FLOW. This was caused by a null flowType property value in the PegaProComUtilities populateFlowActions--(ClipboardPage, ClipboardPage, PublicAPI) function due to the order of actions, and the system has been updated to seek the flowType property of an assignment if it encounters a null value.

SR-A19119 · Issue 241157

Improved error handling for XML-executed BIX extract failures

Resolved in Pega Version 7.2.2

When BIX extracts configured through an XML script encountered a target table that did not exist, the script itself did not visibly fail even though the error "Table doesn't exist in target database" was logged, and any extracts that were executed after that error did not generate any output. This has been corrected to set the correct error flags to ensure expected behavior.

SR-A87291 · Issue 255631

JDBC password encryption check logic updated

Resolved in Pega Version 7.2.2

When using a Database instance with a JDBC connection URL, the specified password is encrypted. An issue was occurring where multiple saves of the instance caused the encrypted password to be encrypted again, causing the agent to lose access to the DB due to an authentication failure. The problem was traced to a logic flaw in the method used to check whether the password was already encrypted, and has been fixed.

SR-A23916 · Issue 253818

BIX extract WO handling corrected

Resolved in Pega Version 7.2.2

After upgrade, a BIX report was not working correctly due to the difference in work object handling. During BIX extract, the currently extracted WO was being maintained on a tempPage that was not subsequently being used for the lookup. This has been fixed.

SR-A76413 · Issue 254770

Custom datatypes import support added to SQL RD

Resolved in Pega Version 7.2.2

After upgrade, external classes of type 'text' mapped to an external DB were throwing an error while executing report definition. This was due to the method used to get the column type, and the logic has been updated to correct this.

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