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-149466 · Issue 607610

Fixed alias assigned to custom categories to handle Oracle limitations

Resolved in Pega Version 8.5.2

When trying to access CHAT via interaction portal, Oracle SQL was fired with incorrect syntax. This was traced to an Oracle limitation of 30 characters on the length of the table name, table alias name, or column name in database versions prior to 12.2. This is caused an SQL exception if the Pega class name was more than 30 characters. To prevent this, a fixed alias has been assigned to the custom category table.

INC-138501 · Issue 592287

Added VBD support for CSRF token setting

Resolved in Pega Version 8.5.2

Attempting to open any VBD reports in the marketing portal for a simulation test caused the user to be logged out. Investigation showed that this happened when CSRF token check was enabled in System > Settings > Cross-Site Request Forgery, and was caused by the planner not passing the CSRF tokens in its Ajax calls. To resolve this, handling for the CSRF tokens has been added to the necessary Ajax calls.

INC-143531 · Issue 598644

Dirty Flag reset updated

Resolved in Pega Version 8.5.2

After opening a case in Cosmos, making updates, and then navigating away without saving, the dirty flag message appeared as expected and offered the option to save, discard, or cancel. After clicking on save and opening the next case, performing the same steps did not cause the dirty flag to display when navigating away. This has been resolved by updating the reset of the isDirtyDialogOpen inside the hide API of a modal close.

INC-146237 · Issue 608744

Corrected popover scroll for AnyPicker

Resolved in Pega Version 8.5.2

Using the AnyPicker control caused display problems. In the initial display of the selection list, the line of choices and the search field overlapped and they were displayed from the second line of choices which forced the user to scroll up to see the first line. After displaying the selection list, clicking outside the selection list without selecting anything to close the list and then displaying the selection again caused the options to be displayed from the 4th line, requiring a scroll up to see lines 1 to 3. This has been resolved to ensure the Scroll on Popover goes to the first element.

SR-D38415 · Issue 507994

Resolved Transfer to Queue duplicate assignments

Resolved in Pega Version 8.3.1

The Transfer to a Queue option was creating duplicate assignments after accepting the Chat. Once the chat was accepted, an instance was created\maintained in both Assign-Workbasket and Assign-Worklist tables. This happened after adding the "Transfers" queue to an Agent; if that queue was not added, the transfer to a queue option gave an error to the Agent receiving\accepting the chat. The Work-.ReassignDefaults activity is an extension that was customized in the Pega-DecisionManager ruleset for a certain use case in revision management. The customization is no longer required and has become redundant and has therefore been removed to resolve this issue.

SR-D43776 · Issue 510761

Clipboard ExecuteActivity button updated to get classname

Resolved in Pega Version 8.3.1

In Clipboard, clicking the execute activity button did not trigger any action in the backend. Investigation showed that previously the ID attribute for the HTML element used to be same as the property name, and the value of property "pyClassName" was found in the document.getElementById function. Due to work done to provide a feature that generates unique IDs for UI elements (auto generated controls), this must be done through other functions such as document.querySelector to get the value of the property from DOM. The necessary updates have now been made to the javascript function in control pzExecuteActivityButton.

INC-153631 · Issue 613851

Table selector updated to handle complex autocomplete dropdowns

Resolved in Pega Version 8.7.1

Whenever an autocomplete and a table were in different sections, only the first 40 results were visible in the dropdown and the other spaces were shown as blank. The issue did not occur if the table and autocomplete were in same section. This was traced to a specific configuration where Section A had an autocomplete inside the dropdown list and autocomplete was enabled to show the results in a table (presentation tab) and Section B, which contained a grid, was included in Section A in the same autocomplete dropdown list. This has been resolved by updating the table selector in ui_grid so it uses the correct dom elements.

SR-D11655 · Issue 485707

JMS Listener modified to ensure connections are closed after encountering an exception

Resolved in Pega Version 8.3.1

JMS listener logs were detailing exceptConnection leaks with the message " J000100: Closing a connection for you. Please close them yourself". Investigation showed that when the JMSListener is configured for JBOSS, it goes via EngineImpl. However, connections opened during engineimpl.ivokeEngine were prevented from closing if they encountered an exception. To resolve this, the execution of the connection close command has been moved to the finally block.

INC-143908 · Issue 606549

Data Page Save correct in batch mode

Resolved in Pega Version 8.5.2

After configuring a List type savable Data Page with save activity in Code-Pega-List, the save data page was triggered from utility of flow from the queue processor to handle queueing 10k data items and creating 10k work objects. When this was run, a field dpClassName was being changed by different threads in DataPageSaverImpl.java. This has been resolved by making the class DataPageSaverImpl.java stateless to ensure thread safety.

SR-D26010 · Issue 500163

Modified VBD insertion logic to improve handling

Resolved in Pega Version 8.3.1

An issue with not being able to launch an additional VDB node was traced to two processes inserting into VBD with different field signatures and triggering unnecessary object creation. This was amplified when adding a second node as the objects were serialized. To resolve this, the insertion logic has been modified to avoid creating new data container/field descriptors after a new field is included, as well as a measurement with smaller data type than previous container.

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