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.

SR-D72141 · Issue 542661

Approved flow rule image unlocked

Resolved in Pega Version 8.3.3

When the Approval Required check box was enabled for rulesets (i.e another person with access to this work queue should approve changes to the rules), a rule which was approved was unlocked and moved back to the original ruleset as expected, but the binary image associated with the flow rule remained locked and any other user other than the one who previously checked in the rule was denied access with a "check out failed" error. This locking error has been resolved by modifying the Rule-Obj-Flow!CleanUp activity to set Param.IgnoreInstanceLockedBy = true.

SR-D90544 · Issue 550371

Corrected row focus for deleting in App Studio case model

Resolved in Pega Version 8.3.3

When attempting to delete a row of properties from the 2nd page of the data model of a case type while using App Studio, clicking on the delete icon brought up a dialog box asking for confirmation for deletion but at the same time the screen went back to the first page of the data model instead of remaining on the second page. Because of this, clicking on the OK button to confirm the deletion caused a random property from the first page to be deleted instead of the targeted row of the second page as expected. This was due to the refresh being triggered immediately within overlay UI actions, and has been resolved by updating the first trash icon action set for the section pzExpressFieldActions to be a modal instead of an overlay when launching local action.

SR-D76492 · Issue 549968

Added check for test case creation when cross-site scripting security enabled

Resolved in Pega Version 8.3.3

Test case creation was failing. Investigation showed that when the "Cross-Site Request Forgery" security setting was enabled, the CSRF token and Browser fingerprint were not included in AJAX calls, and the Ruleinskey was not getting passed. This has been resolved by adding a check to evaluate whether security measures are included or not when making a server call from AJAX, and including the tokens required when appropriate.

SR-D78467 · Issue 542317

Component rule check added to suppress unnecessary guardrail warnings

Resolved in Pega Version 8.3.3

After creating a component application using Configure > Application > Components, guardrail warnings were seen when saving the component. The component application allowed adding rulesets or other applications, but did not have all the tabs found in a normal application, so there was no option for adding the associated classes to define the UI class, Integration class and data class in the component application. As component is mostly a part of (or embedded inside) an application, this function was not given options to justify or suppress guardrail warnings like Rule-Application. To resolve this, a check has been added for component rule before generating guardrail warnings for Empty UI page, Empty Integration class, and Empty Data class.

SR-D85111 · Issue 549196

Paging method updated for Select All in Broken Queue

Resolved in Pega Version 8.3.3

After clicking the 'Select All' box in Broken Queue In Admin Studio, scrolling up and down rapidly caused the checkboxes to be unselected. This was traced to the use of progressing paging in this scenario, and has been resolved by removing progressive paging and replacing it with the out of the box '1 of X' paging method.

SR-D87671 · Issue 547572

PegaCESvcsIntegrator security updated

Resolved in Pega Version 8.3.3

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

SR-D87673 · Issue 548626

PegaCESvcsIntegrator security updated

Resolved in Pega Version 8.3.3

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

SR-D90520 · Issue 552017

REST parameters updated for SauceLabs compatibility

Resolved in Pega Version 8.3.3

After configuring a call to SauceLabs testing through Deployment manager, the REST call was timing out. Investigation traced the issue to SauceLabs changing its parameter name from "browser" to "browsername", and the Pega parameter names have now been updated to reflect that change.

SR-D79397 · Issue 546415

Rule-Utility-Function references updated with library information

Resolved in Pega Version 8.3.3

The "changeSystemName” operation failed. This was traced to the function “getLocalizedValue” (Rule-Utility-Function) being saved into the PegaFS library due to runtime resolution based on the function signature even though the actual Rule-Utility-Function from “Pega-Rules” ruleset needed to be picked in this case. To ensure the correct ruleset is picked, Rule-Utility-Function references have been updated with library information to resolve the resolution collision scenario.

SR-D80539 · Issue 544793

Testcases are not available for 'access when' rules

Resolved in Pega Version 8.3.3

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.

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