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 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.
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.
PEGA0056 alert monitors PR_SYS_LOCKS defragmentation performance
Valid from Pega Version 7.1.8
The System-Locks class contains information about locks, and the PR_SYS_LOCKS table can now be periodically de-fragmented. Accordingly, any increase in the time taken to defragment the table associated with this class results in an increase in the time taken by a requestor to acquire or release a lock.
The PEGA0056 alert indicates that the defragmentation exceeds the time threshold that is configured in the prconfig.xml file. When the alert is triggered, you can modify the defragmentation interval or disable defragmentation.
For more information, see PEGA0056 alert: Defragmentation of the table associated with class System-Locks exceeded the configured time threshold.
Enhanced interoperability with enterprise content management products
Valid from Pega Version 7.1.8
The Content Management Interoperability service (CMIS) capabilities of the Pega 7 platform now provide enhanced interoperability with enterprise content management products. This improvement uses modern web services components that require a Pega platform running Java 7 or higher when CMIS connectivity through SOAP web services are utilized.
Schema not found error when importing a Rule-Admin-Product file
Valid from Pega Version 7.1.8
If you import a Rule-Admin-Product file (RAP) file that includes a schema that has a view, grammar parsing changes can mean that the Pega 7 Platform is unable to find the schema.
To enable the Pega 7 Platform to find the schema:
- Review the error message that indicates that the schema was not found and identify the following items:
- The name of the schema that is causing the error
- The table name in the format: wrong_schema_name.table_name...
- The DDL that the Pega 7 Platform is trying to apply
- Use the table name to identify the correct schema name in your system. This schema is usually your data schema, but might also be an external database.
- Download the DDL.
- Correct the schema name and save the DDL.
- Manually apply the DDL.
Identify, install, and manage hotfixes with the Hotfix Manager
Valid from Pega Version 7.1.8
Hotfixes are packages of files that address issues in Pega 7 and in participating Industry Applications. With Hotfix Manager, you can:
- Scan your system for installed and missing critical hotfixes and create a report that you can provide to Pegasystems Support for diagnostic purposes.
- Review the descriptions and contents of hotfixes.
- Install, rollback, and commit hotfixes.
- Manage hotfixes that include schema changes or require other special handling.
The Hotfix Manager replaces the Update Manager Hotfix Installer and System Scanner, both of which are deprecated. For more information, see Hotfix Manager identifies, installs, and manages hotfixes to Pega 7 and participating Industry Applications.
End of support for Netscape Plugin API in Google Chrome 45
Valid from Pega Version 7.1.8
Beginning with Chrome 45, which is expected to be available in September 2015, Google is ending support for browser plug-ins that rely on the Netscape Plugin API (NPAPI) architecture. These plug-ins include Microsoft Silverlight, Adobe Flash Player, and Java.
The Pega 7 Platform includes several optional features that use these plug-ins. For a detailed overview of these features, see Client-side technologies.
Updates to the Business Intelligence Exchange (BIX) product
Valid from Pega Version 7.1.8
The Business Intelligence Exchange (BIX) add-on has been updated with several new features. BIX 7.1.8 fully supports extraction of data from a Pega 7 multi-tenant instance. BIX can also now be run on Pega Cloud instances. Additionally, the new pxExtractDataWithArgs activity can be used by on-premises customers to schedule BIX runs by using Pega Platform agents.
For more information, see the BIX 7.1 User Guide.