Case-insensitive filtering in reports
Valid from Pega Version 8.2
Filtering in reports is now case-insensitive, improving the reporting and searching experience. You can turn off case-insensitive filtering, for example, by using an activity. You might want to do this if your index is too big or if the length of time it takes for indexing impacts performance.
For more information on report filtering, see Editing filter conditions.
Improved search indexing performance
Valid from Pega Version 8.2
Search indexing now uses a queue processor to improve indexing performance. Indexing can automatically restart if the database goes down temporarily. This saves time and manual action. As a result of using the queue processor for indexing, the following changes have been made to the Search Landing page.
- You cannot cancel indexing from the Search landing page. Cancel indexing by stopping the queue processor from the Data flow landing page.
- The progress message is not shown. View progress on the Queue Processor landing page.
- Queue processor information has been added.
For more information, see Stopping or pausing search reindexing.
More visibility of your production level
Valid from Pega Version 8.2
You can now see the production level of your environment in a new gadget that is available in all Pega Platform™ workspaces. To ensure that you immediately recognize your current environment, you can give it a unique name that is displayed when you click the gadget. In addition to specifying your production level and environment name on the System form in Dev Studio, you can now specify those values on the page in Admin Studio.
For more information on Admin Studio, see Modifying your environment name and production level.
For more information on Dev Studio, see Specifying the production level.
More display options for charts
Valid from Pega Version 8.2
Display properties have been expanded for charts that you add to a report harness or section. In addition to setting general display properties, you can set visibility and color options, control hover highlight behavior for data points and legends, and define more presentation options for grids and tooltips. The additional presentation options enhance your chart design and provide a way for you to effectively highlight important data.
For more information about configuring charts, see Harness and section forms - Adding a chart.
Better navigation between pages
Valid from Pega Version 8.2
The navigation between landing pages and configuration pages in App Studio has changed so that only one tab at a time is displayed in the work area. This change eliminates the maximum tab limit message. Navigate to previous pages by clicking the back arrow at the top of the work area or click the button in the workspace header to open a page in the selected device preview.
Progress gauge and double donut charts
Valid from Pega Version 8.2
To better visualize data, use the new progress gauge chart and double donut pie charts. The progress gauge chart measures the progress made against a goal. The double donut pie chart shows two layers of data in a single chart. The progress gauge chart can be included in reports and dashboard widgets. The double donut chart can be added to dashboard widgets.
For more information about including charts in reports, see Harness and section forms - Adding a chart.
For more information about adding charts to dashboard widgets, see Adding a widget to your dashboard.
Rule revalidation after updating properties without restarting nodes
Valid from Pega Version 8.2
When you update certain property attributes, such as a property's maximum length, rule types that reference the property might not reflect the change. You do not always have to restart nodes to revalidate the referencing rules when they cannot be resaved, for example, when they are in a locked ruleset. For Pega Platform™ 8.1 and later, for non-stream rules, such as activities, data transforms, and so on, use the reassemble API in Admin Studio or truncate the assembled classes table.
For stream rules, such as sections, harnesses, paragraphs, and so on, reassemble the rules and restart the nodes. For more information, see More about properties.
For previous versions of Pega Platform, use the System Management Application (SMA) to revalidate stream and non-stream rules.
Changes in JSON results when checking the health of your system
Valid from Pega Version 8.2
Beginning with Pega Platform™ 8.2, the JSON results that are returned when you ping a Pega Platform instance have changed. JSON results now include node type and health information, including test name, status, state, and node ID. The following samples show JSON results from versions before 8.2 and as of 8.2.
JSON results for pre-Pega Platform 8.2:
{ "duration":"3954.448601", "count":"0" }
JSON results for Pega Platform 8.2 and later:
{"node_type":["WebUser"],"health":[{"last_reported_time":"2019-02-14T16:10:49.589Z","test_name":"Sample-Stream-Check","status":"success"}],"state":"healthy","node_id":"10.10.10_samplenode"}.