Security fields in JFrog Artifactory repository rule form removed
Valid from Pega Version 8.1
The fields in the Security section of the JFrog Artifactory repository rule form, including the Secure protocol field, the Truststore field, and the Keystore field, were not functional in Pega Platform™ 7.3, 7.3.1, and 7.4. This section has been removed from the JFrog Artifactory repository rule form in Pega Platform 8.1.
REST APIs added for management of agents and requestors
Valid from Pega Version 8.1
You can use new REST APIs to download a module version report or manage requestors and agents in Pega Platform™. For example, you can use a requestor REST API to end a requestor process, and you can use an agent REST API to start or stop an agent. These APIs allow external systems to report and manage Pega resources.
For more information, see Pega API for Pega Platform and Pega API.
MBeans deprecated in favor of Pega API
Valid from Pega Version 8.1
The use of MBeans for cluster management has been deprecated, although MBeans will continue to function for legacy deployments. The recommended best practice for automating system management is to use the Pega API. For more information, see Pega API.
DCO Compatibility tool is deprecated
Valid from Pega Version 8.1
The DCO Compatibility tool has been deprecated. Use the Application Guardrails landing page to see the compliance score and any warnings for your application.
For more information, see Application Guardrails landing page.
Identify team members working on a rule
Valid from Pega Version 8.1
By using the team collaboration widget, you can see who on your development team is working on the rule that you are viewing. This widget is displayed in the section header when you are using the Case Designer, Data Designer, or Channels and interfaces configuration pages. When you update a page, a notification is sent to other collaborators stating that the content has been updated and prompting them to refresh to see the latest content.
Apache Ignite is no longer supported
Valid from Pega Version 8.1
Apache Ignite is no longer supported and has been replaced by Hazelcast Enterprise Edition 3.10 in embedded mode. If you used encryption with Apache Ignite, you can configure encryption on Hazelcast Enterprise Edition in the same way that you configured it for Apache Ignite.
For more information about encrypting nodes, see Enabling encrypted communication between nodes.
Troubleshooting offline-enabled applications in a browser
Valid from Pega Version 8.1
You can now troubleshoot offline-enabled applications by using the Tracer tool and developer tools that are available in a web browser. You can troubleshoot scripts that are running when the application is running, without having to use additional debugging tools.
For more information, see Application debugging using the Tracer tool, Troubleshooting offline-enabled applications with the Tracer tool in a browser, and Offline capability.
@java and locatable pages no longer supported
Valid from Pega Version 8.1
@java and locatable pages are no longer supported. Existing rules that use @java and locatable pages will continue to work; however, changes to these rules cannot be saved unless @java and locatable pages are replaced by supported functionality. Use a rule utility function (RUF) instead of an @java page, and use a data page instead of a locatable page. In addition, Pega Platform™ displays a guardrail warning when you open a rule that uses an @java page or a locatable page.
Automatically populate columns on import
Valid from Pega Version 8.1
If an imported archive file adds columns to existing tables, Pega Platform ™ can automatically expose and populate the new columns during the import. For more information, see Import wizard.
Automatically revalidate and save classes after upgrade
Valid from Pega Version 8.1
To automatically revalidate and save classes after an upgrade, edit the product rule definition. After you upgrade the application, the classes you specify are revalidated and saved under the application version context you provide. If the application version exists on the target system before the upgrade, the revalidate and save process is not called.
For more information about editing the product rule, see Specifying product rule deployment options.