Published Release Notes

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.

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.

Exporting charts in scheduled reports to a PDF file

When a scheduled report with a chart is exported to a PDF file, the chart is not automatically included in the PDF file. This behavior is different from when you export reports from the Report Viewer. When you export a report with a chart from the Report Viewer, the chart is included in the PDF file.

For scheduled reports, you can use the pyEmbedChartUsingPhantomJS HTML rule and the pyCallPhantomJS activity rule to implement a solution that exports a chart to a PDF file.

For more information, see Exporting a chart in a scheduled report to a PDF file.

Context-specific documentation is not available in express mode

Help topics that are opened from express mode display content that is specific to Designer Studio.

If your system is dedicated to applications that are developed in express mode exclusively, and you do not need Designer Studio help topics, you can set the Online Help URL field on the System Settings landing page to: https://pdn.pega.com/sites/default/files/help_p7e/procomhelpmain.htm. Alternatively, you can view the contextual help system for Pega 7 Express in a separate browser tab.

Design-time limitations in express mode

Some limitations apply when you develop an enterprise application in express mode. At design time, some features are disabled or have limited options when you configure them in Designer Studio and switch to express mode. The use of these features does not restrict the run-time behavior of your application; however, you cannot change the configuration of these features unless you switch from express mode to Designer Studio.

For more information about each limitation and the recommended action to take, see the following information:

• Pega 7.2.2 Design-time limitations in express mode
• Pega 7.2.1 Design-time limitations in express mode
• Pega 7.2 Design-time limitations in express mode
• Pega 7.1.9 Design-time limitations in express mode

Problem with truncating Decision Data Store data set

The Truncate operation for the Decision Data Store data set may cause timeout exceptions. This problem is caused by the Apache Cassandra database that waits until compaction tasks finish before it can truncate the data set.

Recommendation:

Repeat the Truncate operation until it is successful.