Custom search indexes are special purpose indexes that are created and managed outside of Pega Platform™. You can view the status of custom search indexes on the Search landing page to see whether they are complete. This information is useful for troubleshooting and can help you determine whether to rebuild the index.
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.
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.
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.
Valid from Pega Version 8.1
In the rare case in which a step page context is null, or the pxObjClass associated with the step page is empty, the system no longer attempts to resolve the when rule against @baseclass. As a result, you might see more rule not found errors. Check the step page context and class and ensure that they are not null or empty. In all other cases, if a when rule is not found in any other part of the class hierarchy, the system attempts to resolve it against @baseclass.
Valid from Pega Version 8.1
You can generate a dedicated search index for a case type. Using a dedicated index makes reporting faster without putting additional requirements on the database.
You can now define integration systems that you can use when you create data pages, integration connectors, and databases. Integration systems are associated with an icon that is displayed on the Integration Designer so that you can quickly view the systems that are used by your data types. This information is useful for assessing the effect of migrating to a new system of record and for understanding your data model.
You can now manage data views, called data pages in Dev Studio, in the Data Designer in App Studio. You can change a data view's data source without switching to Dev Studio. You can create a JSON mapping using a visual, drag-and-drop mapper.
You can now access a visual depiction of the relationships among data types from the Data Designer in App Studio. By understanding how data types depend on properties and other data types, you can extend your data model more quickly.
The Report Browser now displays available reports in a tile view, in addition to the list view. You can toggle between the two display formats. The report tiles provide a thumbnail preview of each report, which makes it easier for you to identify reports at a glance, without having to open each report.