Published Release Notes

Tomcat log files moved to work directory

For Tomcat application server users, the default path for PRPC logs has been changed to the "work" directory for Catalina. For example:

<tomcat>\work\Catalina\localhost\prweb

This directory can be cleaned up during administration. To avoid loss of files, you can redirect logging to a different directory after installation:

1. Navigate to the <tomcat-home>\webapps\prweb\WEB-INF\classes directory.
2. Open the prlogging.xml file.
3. Locate the "appender" definitions section that contains the "@{web.tmpdir}" string
4. Update the FileNamePattern values to point to the new directory.

For more details, refer to the “Change the default path to PRPC logs” section in the Tomcat installation guide for your database.

Additional upgrade scripts for new columns

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

Source field not displaying in data transform

On the Data Transform rule form when using the Update Page action, if the Relation value is updated to “with values from”, the Source field will not be displayed.

(Note that for existing data transforms where the Source field has already been completed, this situation should not occur.)

Workaround

1. Below is a data transform that has been configured to use Update Page.
   
2. If a user were to choose an alternate source by updating the ‘with values from’ Relation value, they would not be prompted to provide a page name in the Source field.
   
3. At this point, to be able to enter the Source page value, the user has to save the rule, which results in an error because the source page value is blank. This causes the field to appear.
   
4. Once the field has appeared, the Source page value can be provided, and the form can be saved successfully.
   

Slow WebSphere performance on Mac platforms

Use the following JVM setting to improve WebSphere performance on Mac platforms:

-Djava.net.preferIPv4Stack=true

Split schema systems require additional privileges

On Oracle split schema systems, add the following database privileges:

• Grant DROP ANY INDEX to the Admin User.
• Grant UNLIMITED TABLESPACE to the Rules User.

Use the Oracle Enterprise Manager to add these privileges or refer to the 7.1.3 Upgrade and Installation guides for Oracle.

Core Engine

This release contains fixes related to clipboard and declarative features, including data pages and autopopulate.

• A rule may be changed using Private Checkout, and then checked into a higher RuleSet Version for that RuleSet.
• Agents may now use a 24-hour time period for scheduling, as well as a 12-hour time period (which required the selection of AM or PM).
• Caching and performance have been enhanced.
• Declare expressions will work with embedded page lists when creating forms.
• Mandatory parameters on a data page can handle blank values.
• Properties may be auto-populated using a reference property which is created with a Property-Ref method in an activity.
• System will use "private edit" rules in developer's personal RuleSet when that rule overrides the "standard" rule available to all.
• The Page-Remove method will now remove Data Pages at the Thread level and the Requestor Level.
• When copying a page using the "Set" action on a data transform, the Declare Indexes defined on that data will be updated.
• When creating a data page, the Reload Once per Interaction checkbox can be checked to set the refresh strategy. 

Database

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.

DCO

This release focused on improving the user experience of creating new rules and tightening up the use of specifications in the Case Designer.  The layout of the New and Save As forms were made more intuitive and intelligent.  Specification actions were made to be more consistent across various aspects of the Case Designer.

• After removing specification references, users can create and save a new specification.
• Developers may now choose either an existing specification or create a new one for subflows and Split-For-Each shapes.
• If a specification is not associated with flow shapes such as sub flows, Utilities, or Split-For-Each, it is possible to import speciications with the same names, and the flow shapes will default to using those imported specs.
• In the outline view, specification changes will be preserved when switching from tab to tab.
• The View Full Details functionality from either Configure Step or the Outline View will display all details, including the specification requirement links.

Decision Management

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.

Designer Studio

Many refinements to the Designer Studio were made around performance and user experience. Based on feedback, we have made a number of bug fixes and strategic improvements that improve the overall user experience.

• The Developer Portal connects to the PDN's RSS feed without needing a DigiCert certificate for validation. The RSS feed is just headlines; to open and read any of the articles, users will still have to log into the PDN.
• Expression Builder has been enhanced to work with IE8.
• New applications built in Version 7.1 will automatically redirect users to the PRPC login page upon logout. A new template has been added, to allow developers to customize their applications to redirect users to a logout page, if they wish.
• Performance improvements were made when saving and validating rules.
• Performance of the Guardrails Dashboard has been improved.
• The display of circumstanced rules in Application Explorer has been enhanced.