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.
New mobile capabilities in Pega Express
Valid from Pega Version 7.2
In Pega Express, you can now configure offline case types and quickly build a custom mobile app from the Mobile app tab in the settings. You can apply branding, use certificates, and take advantage of device capabilities such as geolocation tracking. If you set up signing certificates (Android, iOS) and provisioning profiles (iOS) for the custom mobile app in the Designer Studio, you can also access them in Pega Express.
For more information, see Building mobile apps.
Relevant records to define reusable assets
Valid from Pega Version 7.2
Relevant records describe the collection of rules that refine the behavior, presentation, and definition of a case or data type. They are commonly used to designate records from an inherited class as important or reusable in a child class.
Use relevant records to define information displayed in certain Pega 7 Platform application screens and fields. The Pega 7 Platform provides a number of items marked as relevant records, and you can further manage relevant records for your own case and data types.
For more information, see Relevant records.
Use multiple built-on applications to enhance ruleset reuse
Valid from Pega Version 7.2
Applications can now have multiple built-on applications, allowing rules to be reused as a part of a built-on application at run time while being developed independently at design time.
Previously, applications built in Pega 7.1 and earlier versions were assembled in a single linear application stack--one application built on top of another application, and so on. Attempting to reuse rulesets and frameworks across applications resulted in having to splice applications together, creating challenges when attempting to support the use of these custom created applications. Starting in Pega 7.2, applications are built on to other applications by using a hierarchical tree structure, and the Pega 7 Platform automatically converts this tree into a linear application stack.
For more information, see Using multiple built-on applications and the Ruleset behavior at design time section in Application stack hierarchy for multiple built-on applications.
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.
Descendant class instances now included in reports
Valid from Pega Version 7.2
The Report on descendant class instances option on the Data Access tab of the Report Definition rule has a new option to now include data from all descendant classes of the report's primary class. If descendant classes are mapped to multiple class tables, the generated SQL query performs UNIONs to include this data. Previously, only a single class was included in the report.
You can select a subset of descendant classes to include or exclude by adding a filter condition on pxObjClass.
Existing reports retain the older behavior for this option after an upgrade or update. To use the new option, you must set it for each existing report. New reports created in Designer Studio and out-of-the-box Pega 7 Platform template reports from which new reports are created in the Report Browser (pyDefaultReport and pyDefaultSummaryReport) default to the new option. If you have created custom template reports for some application classes, you must change them to enable the new option in reports that are created in the Report Browser for these classes.
See Reporting on data in multiple class tables.
Import specifications
Valid from Pega Version 7.2
In Pega Express, you can now import specifications from an Excel spreadsheet. Keeping specifications up-to-date helps you to generate a meaningful application profile document to share information about your project with stakeholders.
For more information, see Importing specifications.
Create and edit reports
Valid from Pega Version 7.2
In Pega Express, you can now create and edit reports for the case types in your application. You can use the new reporting features to modify the way information is displayed in a report and to sort and filter the data for different audiences.
For more information, see Creating reports and Editing reports.
Enhanced data modeling
Valid from Pega Version 7.2
You can now create data types quickly in Pega Express. Use the enhanced Data Designer user interface to define the data model for your data types. More field types have been added, and they are categorized as simple, fancy, and complex to meet your data modeling needs.
For more information, see Data Designer enhancements.
Generate an application profile document
Valid from Pega Version 7.2
In Pega Express, you can now generate an application profile document to share information about your project with stakeholders. An application profile document contains business-related information that is associated with the implementation of a project, such as sizing estimates.
For more information, see Generating an application profile document and Enhancements to the Direct Capture of Objectives.