Deprecated rule types
Valid from Pega Version 7.1.8
The following rule types have been deprecated as of the Pega 7.1.8 release:
- Form
- Hierarchy
- Service COM
- Service BPEL
- Connect BPEL
- Parse Transform
- Parse Transform Collection
- Parse Infer
For more information, including suggested alternate rule types, see the help topic Deprecated features.
Simplified Adaptive Decision Manager Deployment
Valid from Pega Version 7.1.6
The Adaptive Decision Manager (ADM) server relies on automatic detection of the database dialect. This simplifies the number of deployable archives used to set up the ADM service.
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.
Simplified process for JMS MDB listener deployment
Valid from Pega Version 7.1.8
The process for deploying a JMS message-driven bean (MDB) that represents a JMS MDB listener has been streamlined for new enterprise applications. It is now less complicated and can be performed in fewer steps.
For more information on deploying to WebSphere, WebLogic, and JBoss, refer to the PDN article Deploying a JMS message-driven bean (MDB) that represents a JMS MDB listener in Pega 7.
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 |
Fixed portal type deprecated
Valid from Pega Version 7.1.6
Existing portals configured as fixed still work, but there is no longer an option to create a new fixed portal type.
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.
Pega Connect-CMIS support for NTLM authentication
Valid from Pega Version 7.1.8
Support is now available for using Connect-CMIS rules and NTLMv1 authentication with enterprise content management (ECM) systems such as Microsoft Sharepoint. This capability is provided by the underlying Apache Chemistry OpenCMIS libraries that impose the following restrictions:
- Only a single NTLM-enabled CMIS connector can be used per node (JVM).
- Only Basic Authentication and NTLMv1 are supported as authentication methods with Connect-CMIS.
PEGA0055 alert detects clock drift in a multi-node clustered environment
Valid from Pega Version 7.1.8
Clocks in most of the hardware platforms run at different rates, and the PEGA0055 alert detects the clock drift on any of the nodes in a multi-node cluster. The alert is triggered when the clock drifts from the average time of the clocks in the cluster by an amount that exceeds the time threshold configured in the prconfig.xml file. You can use a network time protocol service or daemon to correct the clocks by referring to a standard external Internet time service, for example, nist.gov.
For more information, see PEGA0055 alert: Clock drift exceeded the configured time threshold.