Published Release Notes

Report Browser removed from Designer Studio

The Report Browser and Access landing page have been removed from Designer Studio. In Designer Studio, developers can create, edit, and test reports by using the Report Definition rule form.

The Report Browser is still available in the Case Manager portal.

For Microsoft SQL Server deployments, change settings to create data types in Integration Designer

For on-premises deployments that use Microsoft SQL Server, set the Pega-Reporting/reporting/useMergeHintForRRquery dynamic system setting to true. If you do not configure this setting, you might not be able to create a new data type in Integration Designer that uses Pega as the system of record. Configure the setting as follows:

• Owning ruleset: Pega-Reporting
• Setting purpose: reporting/useMergeHintForRRquery
• Value: true

For more information about configuring dynamic system settings, see Creating a dynamic system setting.

Role-based workspaces improve productivity

You can now use workspaces to access role-based tools and features. By focusing on the tasks that align with your expertise, you can develop and manage your application more quickly.

For more information about the different types of workspaces, see Workspaces.

Upgrade changes system name

As of Pega 7.1.7, the following renaming behavior no longer occurs.

The upgrade process renames your system to “PRPC” and modifies any custom requestor rules in your application to use this name. After the upgrade completes, you must apply these changes to revert your system:

1. Identify all custom requestor rules (browser, batch, app, portal) with access groups that point to prior versions of PRPC.
2. Open the relevant access groups (for example, PRPC:Unauthenticated and PRPC:Agents) and update the name and version fields to point to the current PegaRULES application.
3. Reset your system name to its original value. You can set the Dynamic System Setting prconfig/identification/systemName/default or use the Designer Studio > System > Settings > System Name landing page.
4. Restart the system.

Conditional online and offline map display

The way an Address Map control behaves in a offline-enabled mobile app has changed. When a mobile app is online, a live Google map is loaded as expected. If the mobile app goes offline, a predefined image of a map is loaded instead.

Improved identification and handling of code assembly errors

Code assembly error logs are now more meaningful and help you identify root causes with better accuracy. Pega Platform™ now also invalidates erroneous assembly to facilitate successful reassembly when the code is accessed again. For example, if a section is not correctly assembled when a user first signs in to the system, the application attempts to reassemble that section the next time a user signs in. In this way, you can avoid lingering issues and improve stability.

IE8 limits expansion features

Internet Explorer 8 (IE8) does not support CSS media queries, which are used by re-expansion features in the Designer Studio. IE8 users with low screen resolution (800 x 600) and a small window size may find that the explorer area in the Designer Studio collapses but cannot re-expand. 

As a work around, access the Designer Studio from another supported browser version and use the recommended, minimum screen resolution width of 1280 pixels.

View data type relationships in Data Designer

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.

For more information, see Viewing data relationships.

Resolve Job Scheduler and Queue Processor rules with the AsyncProcessor requestor type

Use the new AsyncProcessor requestor type to define a default dynamic context to resolve background rules such as Job Scheduler and Queue Processor rules. Switch to an application-based context after you create your own access groups, to resolve only the rules that are included in your application.

For more information, see AsyncProcessor requestor type.

Enhanced tables in Cosmos React UI

The Pega Platform™ Cosmos React UI environment now includes improved tables. The updated tables use a revamped graphic design and support a number of new run-time behaviors, including column freezing and advanced filtering. The added features improve the user experience by giving case workers more control over data in tables, while the revised architecture enhances efficiency and reliability.