Run cleanup.bat/sh script only before upgrading
Valid from Pega Version 7.1.1
Prior to upgrading the rulebase, you can optionally run the cleanup.bat/sh script to remove older rules from the database.
Run this script before you upgrade your rulebase, or the script may delete needed rulesets. For more information about running the cleanup.bat/sh script, refer to the Upgrade Guide specific to your release version.
When using Oracle 12.1.0.1, left outer joins in reports may return incorrect results
Valid from Pega Version 7.1.1
When using Pega 7 with Oracle 12.1.0.1 , reports that use left outer joins may return incorrect results.
This is an Oracle known issue. To resolve this behavior, upgrade to Oracle 12.1.0.2, apply the Oracle patch 16726638 by requesting it directly from Oracle, or, for Microsoft Windows installations, apply Windows Bundle patch 12.1.0.1.15 or later.
For more information in this behavior, see: https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=392085808201943&id=1957943.1
Node description cannot match application server node name
Valid from Pega Version 6.3 SP1
A node's Short Description should not be the same value as the application server node name. If the node's Short Description is changed to be the same value as the application server node name, then the node description is automatically changed back to the original value after a system restart.
Support for Data streaming service for Pega Cloud Marketing 7.4 applications
Valid from Pega Version 2.1
Pega Cloud Marketing 7.4 applications support the Kafka-based Stream service featured in Pega Platform 7.4.
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:
- To download the WSDL from Pega Platform:
- 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.
- Click the URL to display the XML.
- Save the WSDL file to your local system.
- In the text editor of your choice, modify "Name" to "name" in every <element “name” = … > tag in the WDSL.
- Save your changes to the local file.
- To reload the WSDL into Pega Platform:
- In Dev Studio, open the Configure menu.
- Select Integration > Connectors > Create SOAP Integration.
- In the New SOAP integration wizard, select Upload WSDL from File.
- 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.