Published Release Notes

Value list and value group properties are not supported inside data flows

Value list and value group properties are not supported inside data flows, and you need to instead use other property types.

See the Pega 7 developer help to check all available property types.

Data flow preview size is fixed to 10

The Preview option for each shape in data flows returns the first 10 records. This value is fixed and currently cannot be changed.

Data Flow transformation shapes cannot be used in combination with the Compose or Merge shapes

When you reference another data flow from a data flow that contains the Compose or Merge shape, the referenced data flow cannot contain transformation shapes (EventStrategy, Decision strategy, Convert).

Data flow validation does not currently prevent you from designing a data flow that goes against this design pattern. Make sure that your data flows follow this design pattern by checking the referenced and referencing data flows.

Data flow destination is resolved at assembly time

Data flow execution always uses the design-time destination data sets or destination data flows, regardless of the input records at run time.

Example:

You create a data flow and set the destination to a specific data set. In the data flow, you use a strategy that produces some results. Regardless of these results, the execution of your data flow always uses the destination data set that you specified when you designed the data flow.    

The same applies when you set the destination to a data flow.

Offline configuration limitation

When enabling the offline capability for a case type, do not select the Enable offline check box in Case Designer because it incorrectly sets the locking strategy. Instead, select the Enable offline mode check box on the Advanced tab of the Case Type form.

To open the Case Type form from Case Designer, click Open on the Actions menu.

Creating data page unit tests in Internet Explorer 8

When creating data page unit tests, selecting a parent property does not automatically select the child properties when using Internet Explorer 8.

Page and page list properties to be included in a data page unit test are selected on the Create test screen by selecting a check box next to the property name. Normally, selecting the check box of a parent property automatically selects all subsequent child properties as well. When using Internet Explorer 8, child properties are not automatically selected when the parent property's check box is selected.

The solution requires selecting all of the desired child properties individually. Select the check box next to each child property to include it in the data page unit test.

End of support for Microsoft Internet Explorer 8 and quirks mode applications in Pega 7.1.9

In accordance with Microsoft’s announcement to discontinue support for Internet Explorer 8 in January 2016, Pega 7.1.9 does not support Internet Explorer 8, nor does it support non-HTML5 standard user interfaces.

You must upgrade to Microsoft Internet Explorer 9 or later or use Google Chrome, Apple Safari, or Mozilla Firefox. If you are using Internet Explorer 9 or later, you must turn off compatibility mode by accessing the Compatibility View settings.

Note the following:

• Pega 7.1.9 does not support user interface rules that are not based on HTML5 standards (rules in quirks mode).
• If you use applications that are rendered in quirks mode, which enables Pega 7 to correctly display and render non-HTML5 standard user interfaces, you must update them to standards-based HTML5 user interfaces when you upgrade to Pega 7.1.9 or later. Pega 7 provides automated tools to help you migrate your applications.
• Pegasystems Global Customer Support will not investigate or fix any Pega 7.1.9 bugs or support requests that are exclusive to Internet Explorer 8 or quirks mode user interfaces.

You can quickly identify which components of your application user interface are not HTML5 standards-based by clicking Designer Studio > User Interface > HTML5 Application Readiness.

Upgrading to Pega 7.1.9 and a newer browser offers the following benefits:

• These browsers are HTML5 and CSS3 compliant.
• New features are supported and existing features work as intended.
• The Pega 7 Platform user interface is displayed and rendered as intended.
• Browser security is enhanced.

If you have additional questions about browser support, see the Platform Support Guide or contact Pegasystems Global Customer Support.

Upgrades from PRPC 5.4 or earlier fail if index/data enabled = true

Upgrades from PRPC 5.4 or earlier fail if the index/data enabled Data Admin System Setting (DASS) is set to true. To upgrade from versions prior to PRPC 5.5:

1. Set the index/data enabled DASS to false.
2. Perform the upgrade.
3. Set index/data enabled to true.

Schema not found error when importing a Rule-Admin-Product file

If you import a Rule-Admin-Product file (RAP) file that includes a schema that has a view, grammar parsing changes can mean that the Pega 7 Platform is unable to find the schema.

To enable the Pega 7 Platform to find the schema:

1. Review the error message that indicates that the schema was not found and identify the following items:
   • The name of the schema that is causing the error
   • The table name in the format: wrong_schema_name.table_name...
   • The DDL that the Pega 7 Platform is trying to apply
2. Use the table name to identify the correct schema name in your system. This schema is usually your data schema, but might also be an external database.
3. Download the DDL.
4. Correct the schema name and save the DDL.
5. Manually apply the DDL.

Configuration required for data operations on external schema when using a Postgres database

When you use the API for data operations on external schema in the Postgres database, you must update the prconfig.xml file. No other platform requires a prconfig.xml update.

To update the prconfig.xml file:

1. Stop the server and add the following entry to the prconfig.xml file:
   env name="database/databases/postgres_ext/defaultSchema"
   value="externalschema"
   where postgres_ext is the external database that uses the external schema “externalschema”.
2. Restart the server.