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.

Change logic does not work in Report Editor

Valid from Pega Version 7.1.2

The Report Editor​ change logic button does not work. As a workaround, use the rule form to change the logic.

Tomcat log files moved to work directory

Valid from Pega Version 7.1.2

For Tomcat application server users, the default path for PRPC logs has been changed to the "work" directory for Catalina. For example:

<tomcat>\work\Catalina\localhost\prweb

This directory can be cleaned up during administration. To avoid loss of files, you can redirect logging to a different directory after installation:

  1. Navigate to the <tomcat-home>\webapps\prweb\WEB-INF\classes directory.
  2. Open the prlogging.xml file.
  3. Locate the "appender" definitions section that contains the "@{web.tmpdir}" string
  4. Update the FileNamePattern values to point to the new directory.

For more details, refer to the “Change the default path to PRPC logs” section in the Tomcat installation guide for your database.

Slow WebSphere performance on Mac platforms

Valid from Pega Version 7.1.2

Use the following JVM setting to improve WebSphere performance on Mac platforms:

-Djava.net.preferIPv4Stack=true

Split schema systems require additional privileges

Valid from Pega Version 7.1.2

On Oracle split schema systems, add the following database privileges:

  • Grant DROP ANY INDEX to the Admin User.
  • Grant UNLIMITED TABLESPACE to the Rules User.

Use the Oracle Enterprise Manager to add these privileges or refer to the 7.1.3 Upgrade and Installation guides for Oracle.

Support for encrypted traffic in a cluster

Valid from Pega Version 7.3

The Pega 7 Platform includes the Ignite platform, which supports encryption for intra-cluster communications. You can now configure encryption for intra-cluster traffic for compliance with regulatory or organizational security requirements.

For more information, see Enabling encrypted traffic between nodes.

Deploy revisions directly in target environments

Valid from Pega Version 7.3

As a revision manager, you can now directly deploy or migrate completed revisions to multiple Pega 7 Platform environments that were configured as targets by the system architect. The revision management process is faster because you do not need to package a revision as a JAR file, and then manually import that file to the Pega 7 Platform. Additionally, this solution gives business users more control over application rulesets and enables them to act more independently.

For more information, see Direct deployment of revisions.

Batch database processing improvements

Valid from Pega Version 7.3

Batch database processing has been enhanced to ensure that a constraint violation does not occur when you save transactions to a table with a foreign key dependency. Because batch processing changes the order of save operations, it is disabled for transactions with foreign key dependencies. Disabling batch processing ensures that a record with a foreign key dependency on another record will not be written before the record on which it is dependent.

For more information about how batch database processing works and how to enable and disable it, see Batch processing during database write operations.

Operator presence record tracks disconnected status of operators

Valid from Pega Version 7.3

The state attribute in the operator presence record now tracks the operator connection status of DISCONNECTED, in addition to tracking the operator connection status of ACTIVE, AWAY, or OFFLINE. Operators are disconnected if their browser crashes, if they close a browser session without logging out of the system, or if the network connection is down. The DISCONNECTED status helps prevent work from being routed to operators who are not online or not available.

When the operator restores the browser session or the network connection is restored, the Pega® Platform updates the operator connection status to ACTIVE.

For more information, see Tracking the online presence of operators.

Chart drilldown capabilities extended to dashboard widgets

Valid from Pega Version 7.3

When the chart for a report is displayed in a dashboard widget, you now can click any part of the chart to drill down and view the subset of data for that part. This enhancement provides you with an accurate view of the data that determines the report results. Previously, this capability was provided only in the Report Viewer.

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