Data Designer lets you explore, develop, and manage the data your application uses
Valid from Pega Version 7.1.7
The Data Designer, new in Pega 7.1.7, is the lens through which you create and manage your application data types, and create properties within the selected data type. The Create Properties wizard is retired, and you now create and manage properties in the Definition tab of the data type you are viewing. You can track how your application uses your data types, and which case types use which data, on the Usage tab. Review the sources for your data types on the Sources tab, and create and manage local data storage for records on the Records tab.
For more information, see About Data Types.
Explore the relationships between data types with the Data Visualizer
Valid from Pega Version 7.1.7
The Data Visualizer, new in Pega 7.1.7, provides a graphical display of the relationships among your application's data types and class types. The map view can help clarify how your application's data works together. When you hover the mouse pointer over an entity in the display, the Data Visualizer highlights the entities with which that entity has a direct relationship.
For more information, see About the Data Visualizer.
New Cassandra connector rules allow applications to use data in BigData stores
Valid from Pega Version 7.1.7
The new Connect Cassandra rule type provides the interface to leverage data in Cassandra data stores. This means that your applications can use large data sets stored in Cassandra data stores. For more information on this connector type, see About Connect Cassandra rules.
New Hbase connector rules allow applications to use data in BigData stores
Valid from Pega Version 7.1.7
The new Connect HBase rule type provides the interface to leverage data in HBase data stores. This means that your applications can use large data sets stored in HBase data stores. For more information on this new rule type, see About Connect HBase rules.
Your application can be a SAML service provider
Valid from Pega Version 7.1.7
You can quickly establish your application as a SAML service provider, with a web SSO profile, SOAP binding, and HTTP redirect binding to support single logout binding. The service is interoperable with Ping Identity, Tivoli Federated Identity Manager, and many other leading identity service providers (ISPs).
Adaptive Decision Manager installation changes to support delayed learning
Valid from Pega Version 7.1.7
To support delayed adaptive learning, Adaptive Decision Manager (ADM) has been enhanced with database schema changes and no longer relies on Hibernate. This change has an impact in the way ADM is set up in the Decision Management service layer: the jdbc/admDataSource resource is now superseded by jdbc/adm7DataSource.
Additionally, Pega 7.1.7 further simplifies the ADM deployment by providing a single enterprise application or web archive:
- Single EAR deployment archive that can used when deploying ADM on IBM WebSphere and Oracle WebLogic
- Single WAR deployment archive that can be used when deploying ADM on Tomcat and JBoss
Improved full text search
Valid from Pega Version 7.1.7
In Pega 7.1.7, Elasticsearch is used to provide full-text search functionality for rules, work, and data content, replacing the existing Lucene search functionality. In addition to providing search results two to five times more quickly than with Lucene Search, Elasticsearch is more scalable: with multi-threaded bulk and incremental indexing, it provides enhanced information about the search queue, the ability to host index files on multiple nodes, a more robust and expressive search parser, the ability to configure thresholds for alerts and search query time-outs, and automatic handling of replication and failover.
The search management user interface, where you can see length of queue and age of entries, which node hosts the search index, and where it is located.
After upgrading to Pega 7.1.7, the system administrator must manually migrate search functionality from Lucene Search to Elasticsearch. Note that during the switch-over and until the indexes are rebuilt, Lucene search continues to function and there is no interruption in search functions. For more information, see the Pega 7.1.7 Upgrade Guide.
Use JDBC 4 compliant drivers for better performance
Valid from Pega Version 7.1.7
For better performance, ensure that you are using JDBC 4-compliant drivers. For more information on supported and non-supported JDBC drivers, please reference the Platform Support Guide.
Use Tomcat 7 for better performance
Valid from Pega Version 7.1.7
For better performance with a Tomcat web server, use Tomcat 7.
Tomcat 6 has a limitation that causes the server to treat the JDBC driver as if it were a JDBC 3-compliant driver, even if the system is using a JDBC 4-compliant driver. Customers using Tomcat will see better performance if they upgrade to Tomcat 7 and use a JDBC 4-compliant driver.
Engine will not start if the incorrect JDBC driver is used
Valid from Pega Version 7.1.7
The engine will not start up if the incorrect JDBC driver is used. The following configurations are unsupported:
- Using a Multi-tenant Oracle system with one of the Oracle JDBC drivers with issues (see the chart in the Platform Support Guide)
- Using a Multi-tenant system with a JDBC 3 compliant driver, OR with Tomcat 6 (for more information on using tomcat with Pega 7.1.7, see Use Tomcat 7 for best performance)
- Using Microsoft SQL Server with a JDBC 3 compliant driver, OR with Tomcat 6 (for more information on using tomcat with Pega 7.1.7, see Use Tomcat 7 for best performance)
When any of these unsupported configurations are encountered, Pega 7 will not start. Before this change, the engine would appear to start up properly, but would encounter issues during other parts of the engine startup or during actual use of the system.