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).
Cannot create new data tables after update
Valid from Pega Version 7.1.7
Data tables have been replaced by a new local data storage format. You can upgrade old-style data tables to use the new local data storage format, but the new format is not compatible with earlier versions of Pega 7 in which data tables could be created.
You can still edit legacy data tables by using the old data table functionality. However, to create new data tables, you must use the Data Explorer and Data Designer.
Service responses in HTTP and REST connectors are no longer modified
Valid from Pega Version 7.1.7
The Pega 7.1.8 release correctly leaves form service responses for HTTP and REST connectors unmodified. Upgrade to this release if you experience a problem in Pega 7.1.7 where service responses for HTTP and REST connectors are modified when the declared type in the Content-Type header is application/x-www-form-urlencoded. In this case, the responses were modified to a base 64 representation of the bytes in the string. In Pega 7.1.8, responses of type application/x-www-form-urlencoded are mapped to the property designated on the Connector record.
Data pages can source information from a robotic desktop automation
Valid from Pega Version 8.1
You can now configure data pages to source information from robotic desktop automations (RDA). Using an RDA to source a data page allows you to connect your Pega Platform™ application to any application that is accessible from an end-user's desktop. By using automations to retrieve data and load it into a data page, you can use data virtualization to separate your Pega Platform data model from the physical interface of a legacy system against which the automation is running.
For more information, see Obtaining information from robotic automations.
Supported artifacts section removed from repository rule form
Valid from Pega Version 8.1
The Supported artifacts check box has been removed from the repository rule form. Developers can use repositories to provide centralized storage, versioning, and metadata support for application artifacts.
For information about repository connections, see Creating a repository for file storage and knowledge management.
Support for character data type on local variables in activities deprecated
Valid from Pega Version 8.1
Support for the character data type for local variables in activities is deprecated. Use the string data type instead.
For more information about activities, see Activities.