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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

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-D50161 · Issue 514875

Auto populate disabled during redux page conversion to prevent concurrent modification exception

Resolved in Pega Version 8.1.7

Running a standalone data page sourced from a look up of a class was failing sporadically with a concurrent modification exception. The Data page was backed by redux pages: this meant that when the page fetched from data source was converted to redux page, it was iterating through all properties in the mContent of the page and trying to convert those to redux properties. During this process, when any auto populate property was encountered it was getting triggered and modifying the mContent, resulting in a change in iterator. As a result, when the Iterator was trying to fetch the next element, the concurrent modification exception was thrown. To resolve this issue, auto populate has been disabled during redux page conversion to avoid unnecessary problem during data page load.

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.

SR-D38931 · Issue 507058

Support added for Multiple Set-Cookies in Connect REST

Resolved in Pega Version 8.1.7

When using a REST connector, the service returned multiple cookies as separate Set-Cookie response headers, but only the last header value received was stored when using pzResponseHeaderMap on the parameter page. In order to support this use, changes have been made to store multiple header values from Connect-REST responses.

SR-D18853 · Issue 503274

Visibility on client check removed to enable Pulse on click

Resolved in Pega Version 8.1.7

When Pulse was configured on click of a icon, the comment section was not visible. Investigation showed that at the time of DOM load, pyMessage property was not available in the DOM because 'Run visibility condition on client' was checked by default. Visibility on client checks have been removed to resolve this issue.

SR-D26976 · Issue 507215

Filter added to ensure correct context for proposition strategy rules

Resolved in Pega Version 8.1.7

Given two applications (ex App1 and App2) hosted on the same domain where App2 was built on App1, trying to create a strategy rule in App1 and do a test run strategy using the propositional data component which internally uses App2 propositions generated the error: Failed to find a 'RULE-DECISION-DECISIONPARAMETERS' with the name 'GROUP_2'. There were 1 rules with this name in the rulebase, but none matched this request." Investigation showed the strategy was using the PropositionNoCacheUtils and PropositionTools java classes to load the propositions during run time. In these classes, the group classes were browsed from the db irrespective of the application context, causing the strategy run to fail as it was not able to access the decision data rules in other applications which shared the same SR class as the current application. To resolve this, a filter has been added to the PropositionNoCacheUtils and PropositionTools java classes to filter out the groups that are not in the current application context.

SR-D31103 · Issue 502980

VBD insert process updated for better retry handling

Resolved in Pega Version 8.1.7

When restarting Data Flow and VBD nodes, the VBD client can encounter some exceptions indicating components in the stack are temporarily unavailable. In most cases the VBD client retries, but there are some cases where it did not and data flow failures occurred. To resolve this, the code has been updated to remove logging of the VBD cluster status during a retry, and the retry duration has been made configurable.

SR-D37163 · Issue 505479

Corrected Decision Data import filter behavior

Resolved in Pega Version 8.1.7

After upgrade, if a Decision data import referred another component to filter out the import, it did not work. This has been corrected.

SR-D38492 · Issue 505491

Batching now enabled when using IH Summary shape in substrategies

Resolved in Pega Version 8.1.7

Batching was not being enabled when using IH Summary shape in substrategies. This was traced to the IH_SUMMARY_CACHE field not automatically being passed to sub-strategies, and has been corrected.

SR-D39956 · Issue 511639

Corrected method IF use with shortcut function

Resolved in Pega Version 8.1.7

After upgrade, method IF was not working as expected when used in an expression like "@if(.totalorders_120days>0,(.remakeorders_120days/.totalorders_120days)<0.3,false)". This was caused by a missed use case for the combination of an exception-generating function in combination with a shortcut function (i.e. ternary, and, or), and has been resolved.

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