Support for building apps as Android App Bundles
Valid from Pega Version 8.6.1
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.
New dynamic setting to manage validation of hidden fields
Valid from Pega Version 8.6.4
Pega Platform™ version 8.6.4 introduces a new DSS setting for Theme Cosmos and other section-based applications. The validateHiddenField setting controls whether the application validates fields that you hide through visibility rules. By default, validateHiddenField is set to true
, which means that the application fields are validated for completeness even if they are not displayed in the form. You can also switch off this functionality by changing the setting value to false
.
For more information, see Managing field validation in hidden sections.
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.
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.
Integration landing page updates
Valid from Pega Version 7.1.6
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