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.

Geolocation tracking for the latest mobile client

Valid from Pega Version 8

The latest version of Pega Mobile Client™ now supports geolocation tracking for offline-enabled mobile apps. You can enable constant tracking when users work on specific cases from their worklists. This enhancement helps audit the trail of the case and increase the efficiency of your mobile users. For example, dispatchers at headquarters can track the routes of field workers and more effectively assign them tasks based on their current location.

For more information, see Tracking mobile users based on geolocation data.

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.

Default value of the threadpoolsize agent affects batch indexing

Valid from Pega Version 8.5.2

After you patch Pega Platform to version 8.5.2 or higher, the system changes the default value of the threadpoolsize agent, which controls the number of concurrent activities (threads) in the system, from 5 to 15. Batch indexing in Pega Platform does not require all 15 threads, so you can change the agent value to increase system performance by managing the indexing/distributed/batch/numworkers dynamic system setting.
If your deployment does not support that setting, and batch indexing does not use Queue Processors, the system uses the threadpoolsize value for batch indexing instead.

For more information, see Editing a dynamic system setting.

Use "alternate database" as report source

Valid from Pega Version 7.1.6

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

Valid from Pega Version 7.1.6

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

Valid from Pega Version 7.1.6

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

Valid from Pega Version 7.1.6

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.

Only classes that do not belong to a class group can be deprecated.

Designer Studio responds to deprecated rules

Valid from Pega Version 7.1.6

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

Valid from Pega Version 7.1.6

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

Rule type (class)Replacement

Rule-Connect-BPEL

 Service SOAP rules

Rule-Define-Hierarchy 

Navigation rules

Rule-File-Form 

Harnesses and Sections

Rule-Parse-Infer 

@pxReplaceAllViaRegex function

Rule-Parse-Transform

@pxReplaceAllViaRegex function

Rule-Parse-TransformCollection

@pxReplaceAllViaRegex function

Rule-Service-BPEL 

Service SOAP rules

Rule-Service-COM

Service dotNet rules

Retired Six R's

Valid from Pega Version 7.1.6

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

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