top of page

Pega Platform '24.2: Understanding Feature Removals and Deprecations

Changes in Pega Platform: Removed and Deprecated Features 

  

Pega has announced significant changes regarding feature removals and deprecations in the Pega Platform, effective October 2024, particularly starting with Pega Platform '24.2. This article outlines the key updates that users and administrators need to be aware of as they prepare for these changes. 

  

Removed Features 

  1. Adaptive Model FACTORY_KEY_SYNC Event 

Pega Platform will no longer log the FACTORY_KEY_SYNC events associated with Adaptive Models.  

  

  1. Embedded Third-Party Services 

Effective with Pega Platform '24.2, the platform will no longer support embedded versions of Elasticsearch, Kafka, and Cassandra. Only externalized modes for these services will be supported moving forward. Additionally, the legacy externalized Elasticsearch provided by Pega will also be discontinued. However, embedded Hazelcast remains available in '24.2, but it is marked for deprecation and will be unsupported in Pega Platform '25. 

  

Organizations implementing new client-managed deployments of the Pega Platform must utilize externalized Search and Reporting Services (SRS) and Kafka. For Pega Customer Decision Hub™ and Pega Process AI™, external Cassandra is required. Clients using earlier releases must externalize these services prior to updating. 

  

  1. Java Support 

Starting with Pega Platform '24.2, Java 8 and Java 11 will no longer be supported. Java 17 is now the only supported version. Users should follow the standard update process to transition to Java 17. Some earlier application server versions that do not support Java 17 will also be unsupported in this release. For more details, please refer to the Platform Support Guide. 

  

Deprecated Features 

 1) Agents for Background Processing 

Pega initiated the deprecation of Agents for running background processes beginning with Pega Platform '24.2. While existing Agents will continue to function, Pega encourages clients to transition to using Job Schedulers and Queue Processor Rules instead. New Agents can no longer be created from relevant menus in Dev Studio and Admin Studio. 

  

2) Security Features 

Several security features are also deprecated in Pega Platform '24.2: 

- The basic credentials authentication service type. 

- The option to use a custom key management service for creating an external master key for data encryption. 

  

3) Rich Text Editor Security 

The `enableSVGForRTE` Data Stream Setting (DSS) is now deprecated and has no effect. Users can still enable SVG tags through the `rteCustomAllowedTags` setting. 

  

4) Federated Case Management Repository (FCMR) 

The Federated Case Management Repository has been deprecated and will be replaced by Pega Process Fabric Hub™. The Federated Case Management feature remains unaffected by this change. 

  

Additional Changes in Pega Platform '24.1 

  

Several features were also removed starting in Pega Platform '24.1, effective April 2024: 

  

Data Engine API for External Cassandra Databases 

The Data Engine API will no longer support Classes mapped to external Cassandra databases. Methods such as Obj-* and RDB-* for record operations will be unavailable for this configuration. 

  

 IBM Db2 for LUW 

Support for IBM Db2 for LUW databases has been completely removed, following its deprecation in Pega Platform '23. 

  

Installation and Update Assistant Tool 

The Installation and Update Assistant tool will not be included in Pega Platform '24.1 and future versions. Users must now rely on command-line tools for software installations, patches, and updates. 

  

Java 11 Deprecation 

Java 11 was deprecated in Pega Platform '24.1 and will be completely unsupported in the subsequent release. 

  

 

Conclusion 

These changes reflect Pega's commitment to evolving its platform and encouraging the adoption of modern technologies and practices. Users should prepare for these removals and deprecations to ensure a smooth transition and continued functionality within their environments. For further details, refer to the Pega Platform technology support roadmap and the Platform Support Guide. 




--TEAM ENIGMA

3 views0 comments

Comments


bottom of page