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-D5904 · Issue 490489

Discard changes dialog now showing for local actions

Resolved in Pega Version 8.1.7

After having modified case data without saving and clicking on a menu entry (left menu, search, ...), the system shows a dialog box to ask the user to confirm it is ok to discard changes. However, this confirmation dialog did not work with local actions, leading users to lose their work without any warning nor any way to step back. This was traced to a difference in the dirty form check, which was not present when launching a local action from a case. An enhancement has now been added to the handleMenuAction js function in pypega_ui_harnessactions.js which will perform a dirty form check with a prompt.

SR-D23723 · Issue 503090

pxGenerateExcelFile updated for handling blank dates

Resolved in Pega Version 8.1.7

When using a custom template for exporting to Excel, blank DateTime property column values defaulted to the current date. To resolve this, the pxGenerateExcelFile activity has been updated to ensure that an empty date will be exported as blank and that given dates will appear in the correct datetime format.

SR-D24950 · Issue 494566

Added explicit step page to resolve null-pointer exception with custom error message

Resolved in Pega Version 8.1.7

A null pointer exception was generated during case run time harness refresh after a custom error message was inserted. This was traced to a blank step page related to the custom message, and has been resolved by adding a primary step page at step 10 of the New(Work-) activity to prevent the null-pointer exception on harness reload.

SR-D42679 · Issue 509565

oLog.infoForced has been replaced with oLog.debug in GetAssignmentDetailsInternal to reduce excessive logging

Resolved in Pega Version 8.1.7

The Rest API used by Robotics was generating excessive logging on the application server due toPzGetAssignmentDetailsInternal generating several lines of logs with each REST call. In a high volume system, this can make the logs difficult to utilize. To resolve this, oLog.infoForced has been replaced with oLog.debug.

SR-D42670 · Issue 510185

Force order added to inner join when running a Rules Resolution filter

Resolved in Pega Version 8.1.7

After upgrade, D_getResolvedWorkStatuses was not loading properly due to a Report Definition that used a Filter by Rule Resolution option timing out on the SQL Server. When the Filter by Rule Resolution option is selected in RD, it will generate a rule resolution query with an inner join which can cause a time out on the SQL Server while it tries to find out the join order for tables with multiple joins. To resolve this, the SQL server will provide a Force order, merge inner join hint option by way of an added DSS reporting/useForceOrderHint. Additionally, reporting/useMergeHintForRRquery should be set on Pega-Reporting to set things up for using the Merge Inner join hint in the query.

SR-D21555 · Issue 501107

Resolved command line BIX/PRPCUtils creating unreachable nodes

Resolved in Pega Version 8.1.7

BIX and PRPCUtils scripts were creating nodes that showed as unreachable or that were never cleared. This was traced to a code change that resulted in nodes starting as stream nodes unless given a node type or DSS settings, and has been resolved by setting the asyncExecutor/enable setting value as false in the prconfig.xml. The BIX command line JVM argument should also be set to NodeType=BIX.

SR-D46159 · Issue 510973

Reinitializing Full Text Search will shut down Elastic Search regardless of search initialization status

Resolved in Pega Version 8.1.7

Pega search was only sporadically working after converting from standard sandbox-marketing to largesandbox-marketing. This was traced to the Full-Text Search initialization having failed on the app-tier node during re-initialization. As part of re-initialization, the existing node is shut down and the Elastic Search node is started. The shutdown process relied on a boolean flag which indicated if the current status of full-text search initialization was successful. In this case, ES was trying to validate all the cluster level settings, for every save of one of the cluster level settings, but could not due to topology changes in the Util Tier node. The boolean flag indicated initialization had failed so the shutdown process was not invoked, yet the system was attempting to start the second instance of an ES node on the same machine. To resolve this, the shutdown FTS code has been modified to shutdown ES regardless of the search initialization status.

SR-D45600 · Issue 510385

pzIsACoverageSessionActiveForThisRequestor moved to @baseclass

Resolved in Pega Version 8.1.7

When logging out, the error " Failed to find a 'RULE-OBJ-WHEN' with the name 'PZISACOVERAGESESSIONACTIVEFORTHISREQUESTOR' that applies to 'Code-Pega-List' appeared. This was a log errors issue caused by a 'when' rule not being found due to the temporary Pega step page matching with a locally created page, causing the rule resolution of the 'when' rule to fail. To resolve this, the 'when' rule pzIsACoverageSessionActiveForThisRequestor has been moved to @baseclass.

SR-D25753 · Issue 499269

Added WebSphere Liberty Profile to BaseEnvironment.guessServerEnvironment

Resolved in Pega Version 8.1.7

While trying to add a node to Decision data store nodes via Designer Studio > Decisioning > Infrastructure > Service, the error "Service DDS:** java.lang.NullPointerException" was seen, and it was not possible to add a node or save any configuration. This was caused by an incomplete profile for Websphere Liberty, causing the com.pega.pegarules.priv.context.BaseEnvironment.guessServerEnvironment() API to return 'unknown' as the answer when WLP was used. This has been fixed, and the API will return "Websphere" for Websphere liberty profile as well.

SR-D29034 · Issue 500682

Added support for JSON mapping of deep nested pagelist objects

Resolved in Pega Version 8.1.7

An exception occurred when using a JSON data transform in the service activity to map the clipboard data to JSON on the third level of a structure formed as Pagelist-->page-->pagelist. To resolve this, support has been added for nested pagelist mapping with deep nesting of objects (configured for one sided actions) and arrays.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us