Published Release Notes

WSDL generation error prevents invocation of SOAP services

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.

Support for building apps as Android App Bundles

As of August 2021, Google Play Store requires that you submit new apps in the Android App Bundle publishing format instead of the APK format. You can now build Pega mobile apps in the Android App Bundle format so that they comply with this new requirement.

For more information about generating installation packages for Pega mobile apps, see Generating installation packages. For more information about the Android App Bundle publishing format, see the Android for Developers documentation.

Use "alternate database" as report source

You can opt to use the the "alternate database" identified in the Reports Database field of the Data-Admin-DB-Table instance that supports the Applies To class of a report as the source for the report. This reduces the load on the database that serves your application when you run the report.

Pinned classes in Application Explorer

The Application Explorer now includes a Pinned Classes section. This feature allows you to interact with a customized list of classes without having to explicitly switch context in the explorer.

Ability to deprecate a rule

You can deprecate any Rule- instance to indicate that it is no longer supported.

Users are warned when they open or reference a deprecated rule instance.

Ability to deprecate a class

You can deprecate any Rule- class to block users from creating new rule instances.

Users are warned when they open the class rule form or any instance of the class.

Designer Studio responds to deprecated rules

Deprecated classes and rule instances in Pega- rulesets are excluded from:

• Search results
• Application Explorer results
• Lists launched from the Records Explorer
• +Create menus

These restrictions do not apply to classes and rule instances deprecated in your application rulesets.

Formally deprecated rule types

The following rule types have been deprecated. Migrate to alternatives as appropriate:

Retired Six R's

The Designer Studio > Application > Inventory > Six R's landing page has been retired.

Integration landing page updates

The following features and wizards now launch as landing pages in the Designer Studio:

Designer Studio > Integration > Tools > Wizard cleanup

Designer Studio > Integration > Email > Email Accounts

Designer Studio > Integration > Email > Email Listeners