Additional upgrade scripts for new columns
Valid from Pega Version 7.1.4
In Version 6.2, additional columns (Major, Minor, and Patch) containing ruleset Version information were added to 15 tables in the PRPC database. When upgrading from a pre-Pega 7 release, scripts must be manually run after the upgrade to populate these columns.
These scripts are located in the Resource Kit, under Additional Upgrade Scripts.
- If upgrading to a single schema, run both scripts.
- If upgrading to a split schema, run the _data script against the data schema and run the _rules script against the rules schema.
Choose the scripts for your database type:
- db2zos_rulesetversion_columns_data.sql
- db2zos_rulesetversion_columns_rules.sql
- mssql_rulesetversion_columns_data.sql
- mssql_rulesetversion_columns_rules.sql
- oracle_rulesetversion_columns_data.sql
- oracle_rulesetversion_columns_rules.sql
- postgres_rulesetversion_columns_data.sql
- postgres_rulesetversion_columns_rules.sql
- udb_rulesetversion_columns_data.sql
- udb_rulesetversion_columns_rules.sql
Database
Valid from Pega Version 7.1.4
Improvements to data handling were made for search indexing, agent processing, and filtering. Scripts were provided for proper population of the database tables.
- Importing data from shared obj-external tables is now supported.
- A validation warning will now display when an unexposed property is used in filter or join conditions.
- A Global Search index may now be created across two databases.
- Agent processing on multiple nodes has been improved.
- Improvements were made to controls in Report Definition pages which are used in a dynamic grid.
- Filtering functionality involving special characters has been enhanced.
- Scripts have been provided to populate the RuleSetVersion Major, Minor, and Patch columns.
Reporting & Data
Valid from Pega Version 7.1.4
This release fixed many existing unlocalizable elements in 7.1 reporting interfaces (The Report Viewer, Report Editor, Chart Editor, and the Report Browser) and now they are fully localizable. Changes were made to make Listview, summaryview, and report viewer display possible WCAG 2.0 level A and AA support.
- Parameters may now be used in a sub-report join condition.
- Report Definition localization has been enhanced.
- Standalone ListViews with embedded SmartInfo have been improved to resize appropriately when the SmartInfo section is expanded.
- The data section of a report will now display in all of the available space when a fixed header option is selected.
- When localizing a listview with filters, tool tips are translated.
System Management
Valid from Pega Version 7.1.4
Refinements were made to out-of-place upgrade documentation and processes, as well as for how handling is performed for all of the database vendor specific nuances related to a deploying into a split schema environment.
- A script was created to run the data schema upgrade for z/OS systems.
- In a split-schema configuration, indexing has been enhanced.
- The product installer has been enhanced.
- The stand-alone Static Assembly Utility does not require a password for its process.
- The UpdateManager tool has been improved.
View status of custom search indexes
Valid from Pega Version 8.1
Custom search indexes are special purpose indexes that are created and managed outside of Pega Platform™. You can view the status of custom search indexes on the Search landing page to see whether they are complete. This information is useful for troubleshooting and can help you determine whether to rebuild the index.
For more information, see Checking search index status.
REST APIs added for management of agents and requestors
Valid from Pega Version 8.1
You can use new REST APIs to download a module version report or manage requestors and agents in Pega Platform™. For example, you can use a requestor REST API to end a requestor process, and you can use an agent REST API to start or stop an agent. These APIs allow external systems to report and manage Pega resources.
For more information, see Pega API for Pega Platform and Pega API.
MBeans deprecated in favor of Pega API
Valid from Pega Version 8.1
The use of MBeans for cluster management has been deprecated, although MBeans will continue to function for legacy deployments. The recommended best practice for automating system management is to use the Pega API. For more information, see Pega API.
Ability to generate a dedicated search index for a case type
Valid from Pega Version 8.1
You can generate a dedicated search index for a case type. Using a dedicated index makes reporting faster without putting additional requirements on the database.
For more information, see Including indexed data during case search.
Apache Ignite is no longer supported
Valid from Pega Version 8.1
Apache Ignite is no longer supported and has been replaced by Hazelcast Enterprise Edition 3.10 in embedded mode. If you used encryption with Apache Ignite, you can configure encryption on Hazelcast Enterprise Edition in the same way that you configured it for Apache Ignite.
For more information about encrypting nodes, see Enabling encrypted communication between nodes.
Automatically populate columns on import
Valid from Pega Version 8.1
If an imported archive file adds columns to existing tables, Pega Platform ™ can automatically expose and populate the new columns during the import. For more information, see Import wizard.