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.
Decision Management
Valid from Pega Version 7.1.4
This release contains a number of fixes that improve the configuration and execution of Batch decisions – specifically, a number of usability improvements and addresses some issues when creating strategies on IE8.
- Batch Decision functionality has been enhanced in the NBAM environment.
- In NBAM, users can run the strategy execution batch based on the Seed list class instead of the customer class.
- Interaction data will now work even if Action or Organization dimensions do not have values set.
- Running a strategy which includes a Data Import of a structured page reference will work in batch mode.
- Security was enhanced on the VBD Planner.
- The Access of Role to Object rules have been enhanced to allow users to create new Dimension Operator records.
- The NBAM Segment On Canvas will now fetch the SegMap data, even when the generated extended segment class has not been added to the Pages and Classes of the strategy. The SegMap property will (if it exists) be added to a list of properties to fetch, even if the strategy indicates that it is not used.
- When a strategy is defined on a customer class, users may now specify the list of required properties to fetch for the input definition.
- When creating a new strategy, there is now a section to add a Strategy Results class like Business Issue or Group.
Integration
Valid from Pega Version 7.1.4
Critical customer-driven product improvements were made to SOAP services, SOAP connectors and connector wizard, CMIS connectors, and the Pega Image Viewer. These fixes addressed a handful of functionality gaps discovered in PRPC 7.1 and earlier releases by internal and external customers.
- A Connect-CMIS instance which was created using a reference to an ATOM Server Instance may now use Global Resource Settings.
- The Execute Synchronously (one-way operation) has been enhanced for SOAP Services.
- The Silverlight version of PegaImageViewer has been enhanced to print ranges of multiple pages at once.
- The SOAP Wizard has been improved to show all the ports which are available in the WSDL file.
- Two way SSL has been enhanced for the Connect-REST rule.
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.
Performance improvement to BLOB support in Postgres databases
Valid from Pega Version 7.2.2
New tables that contain BLOB columns now use external storage instead of expanded storage for Postgres databases. This improvement applies to tables that are created during installation, upgrade, or during DDL and schema generation. Using external storage improves database performance.
For more information, see BLOB storage in Postgres databases.
Automatically manage nodes in a System Management Application cluster
Valid from Pega Version 7.2.2
Instead of manually adding and deleting nodes in a cluster by using the System Management Application (SMA), you can now automatically manage nodes. You can enable Auto Node Discovery and configure it to get information about all the nodes in a cluster, add new nodes, and update the node list.
For more information, see Managing nodes automatically in a System Management Application cluster.
Show multiple views of data in your application
Valid from Pega Version 7.2.2
You can now show multiple views of data in your application by adding the record editor (pxRecordsEditor) section to a layout, another section, or a cell in a layout. You can configure the section to customize the display and enable the search, import, and export capabilities of the record editor.
For more information, see Multiple views of data in the record editor section.
Support for additional rule types for PegaUnit test cases
Valid from Pega Version 7.2.2
To compare the expected results with the results that are returned by running a rule, you can now create PegaUnit test cases for the following rule types:
- Activities
- Data transforms
- Strategies
- Decision trees
- Decision tables
After you unit test these rules, you can convert them to test cases and configure assertions on the test cases. You can also set up the clipboard with data before tests are run, and clean up the clipboard after tests are run.
For more information, see PegaUnit testing.
Page assertions are supported for PegaUnit test cases
Valid from Pega Version 7.2.2
You can now create page assertions for PegaUnit test cases. Because data transforms and activities can create or remove pages, you can configure page assertions to determine whether a page exists after you run PegaUnit test cases.
For more information, see Configuring page assertions.