Data flow preview size is fixed to 10
Valid from Pega Version 7.1.8
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
Valid from Pega Version 7.1.8
When you reference another data flow from a data flow that contains the Compose or shape, the referenced data flow cannot contain transformation shapes ( , , ).
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
Valid from Pega Version 7.1.8
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
Valid from Pega Version 7.1.8
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 menu.
Creating data page unit tests in Internet Explorer 8
Valid from Pega Version 7.1.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
Valid from Pega Version 7.1.8
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:
- 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
- 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.
- Download the DDL.
- Correct the schema name and save the DDL.
- Manually apply the DDL.
Configuration required for data operations on external schema when using a Postgres database
Valid from Pega Version 7.1.8
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:
- Stop the server and add the following entry to the prconfig.xml file:
env name="database/databases/postgres_ext/defaultSchema"
value="externalschema"
wherepostgres_ext
is the external database that uses the external schema “externalschema”. - Restart the server.
End of support for Netscape Plugin API in Google Chrome 45
Valid from Pega Version 7.1.8
Beginning with Chrome 45, which is expected to be available in September 2015, Google is ending support for browser plug-ins that rely on the Netscape Plugin API (NPAPI) architecture. These plug-ins include Microsoft Silverlight, Adobe Flash Player, and Java.
The Pega 7 Platform includes several optional features that use these plug-ins. For a detailed overview of these features, see Client-side technologies.
New property pxSaveDateTime
Valid from Pega Version 7.1.8
A new property, pxSaveDateTime, records the date and the time that an instance was saved with business changes to the database. This property is always used when an instance is saved, whether you are creating an instance or updating an existing instance. This property is not updated when an instance is moved from one system to another, and it is not updated during certain system management operations that do not change the content of the instance, such as column exposure.
WebSphere log error with Java 8 for Enterprise JavaBeans
Valid from Pega Version 7.1.8
For environments that are deployed by using Java 8 on IBM WebSphere Application Server version 8.5.5.9 through the last 8.5.5.x fix pack, the log might report that a class was not found when the application server attempts to start Enterprise JavaBeans. If Java EE functionality is not needed, no further action is required. However, to use Enterprise JavaBeans, see WebSphere log error with Java 8 for Enterprise JavaBeans.