Method for specifying custom search properties has changed
Valid from Pega Version Pega Platform
The method for specifying a custom set of properties that are stored in the Elasticsearch indexes and that can be referenced later in filter conditions or returned in a set or results has changed. Previously, the pySearchModel Data Transform rule was used to specify a custom search property list within a class. The new method is to specify a Data instance of the Data-CustomProperties-Search class.
After upgrading to Pega 7.2, make these changes:
- Reenter existing pySearchModel Data Transform rules as instances of Data-CustomProperties-Search data instances.
- Enable the
indexing/useDataInstancesData Admin system setting by clicking .
After you change the set of custom search properties for a class, rebuild the Elasticsearch index for that class on the System Settings Search landing page.
Case Manager option for searching only attachments
Valid from Pega Version 7.2
Case Manager search now has an option to search only case attachments. When you search attachments, a new column in the search results displays a paperclip icon with the number of attachments that match the search string. You can click the number to display a list of matching attachments for the selected case.
WriteHistory parameter has been removed from Link-Objects method
Valid from Pega Version Pega Platform
The WriteHistory check box has been removed as a parameter to the Link-Objects method on the Activity form. Users who are upgrading from versions prior to Pega 7.2 do not have to take any action because history details rely on the "linked from" object and this option stored results in the "linked to" object.
To correctly capture a link event in the history of an object, call the History-Add method.
The Declarative Network display is now cross-browser compatible
Valid from Pega Version 7.2
The Declarative Network display can now be displayed on all browsers.
BIX extracts can be scheduled and run from the Pega 7 Platform by using agents
Valid from Pega Version 7.2
You can create an agent that periodically invokes the new pxExtractDataWithArgs activity to run a BIX Extract rule. The activity takes the class and extract rule name, as well as an additional input string with a list of BIX command-line parameters, as input parameters to use for the run.
Discontinued support for list view and summary view rules
Valid from Pega Version 7.2
The list view rule and the summary view rule are deprecated, and support for these rules has been discontinued. Existing list view and summary view reports will continue to work on supported browsers. However, the last version of Internet Explorer that list view and summary view rules support is Internet Explorer 11.
You cannot create new list view or summary view reports. Instead, create list reports and summarized reports by using the report definition rule. To prevent display issues, re-create the custom list view and summary view reports that you need as report definition reports.
Report Definitions can query tables in multiple schemas
Valid from Pega Version 7.2
You can create a Report Definition that queries class tables in multiple schemas in the same database. Previously, queries on tables that were mapped to PegaRULES and PegaDATA schemas could not include tables that were mapped to other schemas, because other schemas were assumed to be in a different database. The schemas to which queried class tables belong are no longer validated when you save the Report Definition, so you can now query tables in schemas other than PegaRULES and PegaDATA. However, Report Definitions that query tables that are in more than one database fail when run.
Label changes to field types in Case Designer
Valid from Pega Version 7.2
The following field types have been renamed in Case Designer to be consistent with Data Designer and other areas of the Pega 7 Platform.
| Label in previous versions | Label in Pega 7.2 |
|---|---|
| Text | Text (single line) |
| Text (multiple lines) | Text (paragraph) |
| Check box | Boolean |
| Date and time | Date & time |
| Date | Date only |
| Drop down | Picklist |
| Number (integer) | Integer |
| Number (decimal) | Decimal |
Users who upgrade from versions prior to Pega 7.2 do not have to take any action because the label changes are cosmetic and do not affect the underlying controls or property types that support form building.
For more information about the field types that you can use when building a form, see Storage and display of single-value fields.
New Pulse gadgets for developers
Valid from Pega Version 7.2
Pulse for the Pega 7 Platform provides two new gadgets: pxContextFeed and pxActivityFeed.
The pxContextFeed gadget is a section that you can integrate with your application. Users can use this gadget to communicate with other users by creating and sharing posts within a given context. You can also customize the gadget or build your own Pulse interface by using a number of APIs.
The pxActivityFeed gadget aggregates all the activity feeds for the cases that a user follows without requiring that individual cases for posts be viewed.
For more information, see the help topic Pulse gadgets and custom APIs.
New Pulse gadget for users
Valid from Pega Version 7.2
You can use Pulse to communicate and collaborate with other users. For example, in Pulse you can post messages, share files, select cases for which you want to receive emails, search for content, and view an activity feed in your dashboard that aggregates your Pulse posts.
For more information, see Pulse for social collaboration.