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.
Enhancements to the AJAX container
Valid from Pega Version 8.2
It is now possible to set a document limit for an AJAX container, between 2 and 16 to control the number of documents opened by users. To reduce development time, you can also choose a new option to have no default view. The multidocument mode features tabbed navigation so that users can switch between open documents. A tabless container, on the other hand, includes an out-of-the-box navigation action for Home, which helps application users move within the portal.
For more information, see Configuring the AJAX container.
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.
Elasticsearch reports support string comparison operators
Valid from Pega Version 8.2
To improve performance, reports that use string comparison operators in filters can now run queries against Elasticsearch instead of querying the database. The following operators are now supported for Elasticsearch queries.
- Starts with, Ends with, Does not start with, and Does not end with
- Contains and Does not contain
- Greater than, Less than, Greater than or equal, and Less than or equal
In cases where a query cannot be run against Elasticsearch, the query is run against the database, for example, if the query includes a join. To determine if a query was run against Elasticsearch, use the Tracer and enable the Query resolution event type. For more information, see Tracer event types to trace.