Skip to main content

What's new in low-code application development 8.7

Suggest edit Updated on February 24, 2022

Application development tools help you create high-quality, efficient, and flexible applications. Key enhancements in this release of Pega Platform focus on expanding App Studio functionality to further support the Pega Express methodology, improve application performance, and expand a variety of low-code tools to meet more needs of citizen developers.

More detailed and efficient debugging of autopopulated properties

Tracer results now include more detailed information about autopopulated properties, for example the metadata of autopopulated properties, which can help you debug your application faster. Also, a new logger category pxAutoPopulate is available in Admin Studio by default, so that you can capture metadata that the autopopulated properties hold at run time, and better target your troubleshooting process.

For more information, see Application debugging by using the Tracer tool.

Fine-tuning configuration settings with different values for each production level

You can now create a configuration setting with different values for each production level. With this enhancement, you get more flexibility in your configuration. For example, you can differentiate the configuration values for:

  • Service endpoint and access tokens for integration
  • Email configuration, port, and server address specifications.
  • Authentication profiles for integrations.

For more information, see Creating configurations.

Unsupported prjsr166*.jar library removed

For improved security and performance, Pega Platform version 8.7 no longer includes the prjsr166*.jar library, as Static Application Security Testing (SAST) scanners skip this unsupported library. Additionally, current Java versions starting with Java 6 include the content of the prjsr166*.jar library by default in a safer and improved manner. The prjsr166*.jar library includes the following .jar files:

  • prjsr166:3.0
  • prjsr166java5:3.0
  • prjsr166java6:3.0
Upgrade impact
The prjsr166*.jar library is no longer present in Pega Platform. If any of your rules reference classes from these .jar files, you might face issues.
What steps are required to update the application to be compatible with this change?
Exclude usage of classes from removed .jar files. For example, if you use an Arrays class from these .jar files, such as com.pega.jsr166backport.java.util.Arrays, use java.util.Arrays instead.
Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

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