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.

SR-123945 · Issue 185036

Corrected symbol handling in ToolTips

Resolved in Pega Version 7.1.8

In the ToolTips, the '@' character was being replaced with '@'. This was an issue with the character being parsed instead of being treated as literal text, and has been fixed.

SR-123945 · Issue 186241

Corrected symbol handling in ToolTips

Resolved in Pega Version 7.1.8

In the ToolTips, the '@' character was being replaced with '@'. This was an issue with the character being parsed instead of being treated as literal text, and has been fixed.

SR-123961 · Issue 184528

New Stylesheets save to harness correctly

Resolved in Pega Version 7.1.8

Stylesheets added to the StyleSheetName pageList were not getting saved in Harness rule. This was traced to the process not updating the primary page on clipboard, and has been corrected.

SR-124004 · Issue 186135

Timing improved for delegated strategy rule editing

Resolved in Pega Version 7.1.8

After saving a strategy rule to an unlocked production ruleset and adding that version to My Favorites, it was not possible to checkout the rule. When the refresh/reload button (only button displayed on the rule toolbar) was clicked, a StringIndexOutOfBoundsException message was generated. The root cause was a timing issue due to system slowness that prevented the display of the toolbar icons, and code has been implemented to increase the timeout for 'openRuleINprogress'.

SR-124005 · Issue 185470

Fix inserted for CaseWorker portals using Microsoft Internet Explorer 8

Resolved in Pega Version 7.1.8

CaseWorker portal links to open and interact with cases were not working in the Microsoft Internet Explorer 8 browser. This was caused by the method used to get the dynamic container not being supported by Microsoft Internet Explorer 8, and has been resolved by changing the querySelector to get the proper class names.

SR-124007 · Issue 187210

Added handling for NPEs on mobile devices

Resolved in Pega Version 7.1.8

Answering a questionnaire on a mobile device was generating the error "NullPointer in SafeURL.put()" due to the source element being a radiobutton div and not sending the request for postvalue. This was a missing condition in the initiatepost method of pega_ui_events for handling NPEs on mobile and the system has been modified to correct this.

SR-124007 · Issue 187611

Added handling for NPEs on mobile devices

Resolved in Pega Version 7.1.8

Answering a questionnaire on a mobile device was generating the error "NullPointer in SafeURL.put()" due to the source element being a radiobutton div and not sending the request for postvalue. This was a missing condition in the initiatepost method of pega_ui_events for handling NPEs on mobile and the system has been modified to correct this.

SR-124011 · Issue 184792

Repaired Case Designer rendering for Microsoft Internet Explorer 8

Resolved in Pega Version 7.1.8

When using the Microsoft Internet Explorer 8 browser, opening a case type in Case Designer which has steps in the stages did not render the steps. This was caused by a CSS file fragment that was not picking up the proper base styles, and has been fixed.

SR-124027 · Issue 190234

BPEL rule types deprecated

Resolved in Pega Version 7.1.8

BPEL is a flow format that makes SOAP calls to other systems. Previously, Rule-Connect-BPEL and Rule-Service-BPEL were supported types not as callable rules, but as summaries of the rules involved with interacting with a particular BPEL flow. This usage originated before the advent of landing pages, and summarized the connector or service rules, respectively, that were in the system for a given BPEL-related service package. It has been found that the BPEL-specific standard in version 1.1 and higher does not carry enough information in its schema to do an import and requires limitations and post-import work to make the flows usable. In addition, BPEL import was supported only with Visio. In Pega 7 there is no Visio view for flows, so these flows cannot be viewed or edited. Therefore the following rule types have been deprecated as of this release: -------------------------------------------------- Form Hierarchy Service COM Service BPEL+D249 Connect BPEL Parse Transform Parse Transform Collection Parse Infer Attempting to use these rule types will present the following messages: -- Service BPEL: "The rule type Service BPEL is deprecated and should no longer be used. Please use Service SOAP instead." -- Connect BPEL: "The rule type Connect BPEL is deprecated and should no longer be used. Please use Connect SOAP instead."

SR-124028 · Issue 189200

BPEL rule types deprecated

Resolved in Pega Version 7.1.8

BPEL is a flow format that makes SOAP calls to other systems. Previously, Rule-Connect-BPEL and Rule-Service-BPEL were supported types not as callable rules, but as summaries of the rules involved with interacting with a particular BPEL flow. This usage originated before the advent of landing pages, and summarized the connector or service rules, respectively, that were in the system for a given BPEL-related service package. It has been found that the BPEL-specific standard in version 1.1 and higher does not carry enough information in its schema to do an import and requires limitations and post-import work to make the flows usable. In addition, BPEL import was supported only with Visio. In Pega 7 there is no Visio view for flows, so these flows cannot be viewed or edited. Therefore the following rule types have been deprecated as of this release: -------------------------------------------------- Form Hierarchy Service COM Service BPEL Connect BPEL Parse Transform Parse Transform Collection Parse Infer Attempting to use these rule types will present the following messages: -- Service BPEL: "The rule type Service BPEL is deprecated and should no longer be used. Please use Service SOAP instead." -- Connect BPEL: "The rule type Connect BPEL is deprecated and should no longer be used. Please use Connect SOAP instead."

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