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.

INC-127981 · Issue 562998

Rulesets removed from direct invocation ability

Resolved in Pega Version 8.2.7

The following rules have been updated such that they are no longer available to be invoked directly by a client or service: Clipboard_ExecuteActivity, getClassInstances, getOperatorIDs, and GetXMLRuleData. In addition, pzAutoGenClipboard_ExecuteActivity will now require authentication.

SR-D79831 · Issue 562800

Access Deny working as expected for Offers

Resolved in Pega Version 8.2.7

It was possible to Save-As an offer in PegaMKT-Work-Offer after encountering an access deny rule. The record was not created in Dev Studio, however, and an expected denial of access was not registered at runtime. This was due to Access deny rules not being considered as a part of validation, and has been resolved by adding the necessary permission validation to the new harness that will produce the error message informing the user that they are missing a permission. Additional work has also been done to pass the 'pzKeepPageMessages' parameter as true so that page level error messages are correctly displayed.

SR-D87673 · Issue 548627

PegaCESvcsIntegrator security updated

Resolved in Pega Version 8.2.7

Security updates have been made which now require authentication to consume the services from the PegaCESvcsIntegrator package.

SR-D88451 · Issue 550848

Testcases are not available for 'access when' rules

Resolved in Pega Version 8.2.7

Attempting to create test cases for access when rules resulted in guardrail warnings about the need to create a test case. Because Test Cases are not available for the Access When rule type as per Pega expected behavior, the guardrail warnings are not valid and have been removed.

SR-D91834 · Issue 554424

Related cases of different types properly linked in Case Worker Portal

Resolved in Pega Version 8.2.7

After creating a case of type1 in the Case Worker portal, creating a case of type2 from the first case showed the case ID of the second case in the Related Work section as expected. However, after clicking on the link of the case ID of the second case from the related work section, the second case opened but the case ID of the first case was not shown in the Related work. The cases were correctly associated when the Case Manager portal was used instead. This was traced to the Case Worker clipboard continuing to hold the previous case ID thread, and has been resolved.

INC-194330 · Issue 708711

Added special character handling for DecisionTable column-label

Resolved in Pega Version 8.7.2

The label of a decision-table column was being appended to the original decision-table return-value. The column label and comparator were handled differently for columns containing special characters (+, -, *,...), causing the data after the special character to be trimmed and appended to the row output value. This has been resolved by adding handling for special characters so the output and the label are rendered properly.

INC-200802 · Issue 714845

Line break handling added for setting required question asterisk

Resolved in Pega Version 8.7.2

If a survey question was formed in multiple sentences, the asterisk marking it as required was not displayed in screen. The asterisk displayed as expected if the question was one sentence. This has been resolved by updating the setMandatoryIconforQP script handle linebreaks and set the required symbol as expected.

INC-205666 · Issue 702936

Database table correctly prevents deletion if there are descendant classes

Resolved in Pega Version 8.7.2

When deleting a concrete class with descendant classes via an activity (Rule-.Delete), the Rule-Obj-Class.ValidateDeleteInternal activity was throwing an error message indicating the class could not be deleted due to descendant classes. However, the corresponding database table rule was deleted anyway. Investigation showed this was caused by ValidateDeleteInternal not reaching the Obj-Save-Cancel step. This can be fixed by modifying step 11, the post when conditions, to jump to END and set the END label at the Obj-Save-Cancel step instead Exit-Activity, but this issues has been resolved by updating all failure states to run end step. In addition, security has been updated to disallow "Allow invocation from browser".

INC-209426 · Issue 706804

GetFunctionsForLibrary retrieves 10,000 rows

Resolved in Pega Version 8.7.2

Some functions were missing from the expression builder browser and search results when pyShowInternalLibrary was set to true for including internal functions in the results. To resolve this, the default value for "Maximum number of rows to retrieve" in pzGetFunctionsForLibrary has been increased to 10,000.

INC-213625 · Issue 712296

Corrected null values being set to 0 in GenerateExcel

Resolved in Pega Version 8.7.2

The pxGenerateExcelFile activity was loading $0.00 in place of a null value for decimal columns. This has been resolved by updating the logic for GenerateExcel.java to skip double properties default value for non-existent clipboard props and extend the same fix to the integer class. Safety checks have been added before setting cell type to check if property exists, and handling has been added for a specific exception instead of generic exception for both decimal and integer use cases.

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