Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

WSDL generation error prevents invocation of SOAP services

Valid from Pega Version 8.4.2

Status

A Known Issue was introduced in the 8.4.2 Pega Platform patch release, which impacts both upgrades and new installations of that version.

Description

Due to changes introduced in the SOAP functionality for the case-mismatch error in SR-D98509/INC-119725, the WSDL is being generated for SOAP services with an incorrectly-capitalized element, which prevents the service from being invoked.  The element should be “name” instead of “Name”.

Workaround

Clients must perform the following workaround after they define a new SOAP connector in Pega Platform:

  1. To download the WSDL from Pega Platform:
    1. After using the SOAP Wizard (Dev Studio > Configure > Integration > Services > Service Wizard) the WSDL URL is shown at the bottom right of the Dev Studio screen.
    2. Click the URL to display the XML.
    3. Save the WSDL file to your local system.
  2. In the text editor of your choice, modify "Name" to "name" in every <element “name” = … > tag in the WDSL.
  3. Save your changes to the local file.
  4. To reload the WSDL into Pega Platform:
    1. In Dev Studio, open the Configure menu.
    2. Select Integration > Connectors > Create SOAP Integration.
    3. In the New SOAP integration wizard, select Upload WSDL from File.
    4. Complete the upload using the wizard prompts.

This is a design-time issue, not a run-time issue; therefore, clients only have to perform this workaround process once. Existing SOAP services should not be impacted; however, if clients modify an existing SOAP service definition by re-running the wizard, clients must reapply the workaround for Pega Platform to recognize the SOAP definition changes.  

Resolution

This issue will be addressed in the Pega Platform Patch Release 8.4.3.  Clients who upgrade to that version or later should not see this issue.

Search and Reporting does not index large items

Valid from Pega Version 8.5

When using the Search and Reporting (SRS) microservice in Pega Platform™ 8.5, you might encounter problems with indexing large out-of-the-box rules. The issue is not visible in Queue Processors, but you can access logs to verify which items the system does not index.

DCO and PMF integration is unavailable

Valid from Pega Version 7.1.5

DCO and PMF integration functionality is not available in this release. Related project management controls have been removed from the following:

  • System Settings landing page (Designer Studio > System > Settings > Project Management)
  • Application Profile landing page (Designer Studio > Application > Profile > Specifications)
  • Add/Edit Specification dialog

Restricted SMA access

Valid from Pega Version 7.1.5

System Management Application (SMA) remote connections are not supported on JBoss EAP 6.x. This means SMA users may only monitor locally connected systems. Ensure that the "Local JVM Connection..." option is selected when configuring PRPC nodes:

Stages and Steps may not appear as expected

Valid from Pega Version 7.1.5

There are some unique configurations of the newly enhanced pxDisplayStages gadget that can lead to case type "Stages and Steps" appearing more than once or not at all.  In the event that your application experiences one of these scenarios, the recommended work around is to relocate the gadget:

  • Add pxDisplayStages to the pyCaseContainer section (or equivalent)
  • Remove pxDisplayStages from the pyCaseActionArea section (or equivalent).

Geolocation tracking requires browser permission

Valid from Pega Version 7.1.6

When the geolocation tracking feature is enabled, a Map it link appears next to each requestor entry in the audit trail. When you click a link for the first time, the browser displays a notification asking whether you want to permit tracking. Make your yes/no selection in the prompt. Do not click "X" to close it, as doing so may render the session unresponsive. Refresh the browser if necessary and make your selection.

Geolocation tracking Map it links do not appear

Valid from Pega Version 7.1.6

If geolocation tracking is enabled, the first time you create a case in the first browser session, the Map it links do not appear next to the initial audit trail entries. When you submit the first flow action, the links appear next to all subsequent entries.

Cannot copy final section rules in UI Kit ruleset

Valid from Pega Version 7.1.6

You cannot copy section rules in the UI Kit ruleset (UI-Kit-71) that start with pz or px (final rules in the base PRPC rulesets).

Instead, to customize these rules, use the Copy/Merge Ruleset tool, available at Designer Studio >System > Tools > Refactor Rulesets, to copy all rules from the UI Kit into your application ruleset. You can then check the section rules in and out.

User interface distortions in the Decision Manager portal

Valid from Pega Version 7.1.6

By default, the New Application wizard in Pega 7.1.6 configures new applications to include UI-Kit-7 in the list of application rulesets. This ruleset causes user interface distortions in the Decision Manager portal. Both applications created in previous maintenance level updates and applications created in Pega 7.1.6 that do not include the UI-Kit-7 dependency are not impacted by this known issue.

Workaround:

  1. Open the application record.
  2. In Application Rulesets, remove UI-Kit-7.
  3. Save the application record.

Text Input control number type does not validate

Valid from Pega Version 7.1.5

When a Text Input control type is set to "Number" in the Presentation tab:

  • Validation does not trigger and the field is blanked out when a user submits the form.
  • If a value other than a number is entered, the browser sends an empty value, and the value is not validated.
  • In the Clipboard, the field value displays as empty.
  • If the field is required, the validation displays.

This issue occurs when using both the Chrome and Safari web browsers, and is a result of browser behavior for the HTML5 type=“number”. To fix this issue when using these browsers, do not use the "Number" type in Presentation tab of a Text Input control. Instead, the type should be set to "Text".

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