Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Data synchronization does not resume after mobile app restart

Valid from Pega Version 8.3

If an offline-enabled mobile app that you build with Pega Infinity Mobile Client is stopped during an initial data synchronization session, the data synchronization does not resume when the mobile app is restarted. Users must not stop the mobile app before initial data synchronization finishes.

For more information about data synchronization, see Offline capability and Guidelines for creating an offline-enabled application.

Source field not displaying in data transform

Valid from Pega Version 7.1.4

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.
    DataTransform1.jpg
  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.
    DataTransform2.jpg
  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.
    DataTransform3.jpg
  4. Once the field has appeared, the Source page value can be provided, and the form can be saved successfully.
    DataTransform4.jpg

Both Transfer and Transfer Assignment flow actions are displayed in the Bulk Actions tool

Valid from Pega Version 7.1.7

Both the deprecated Transfer flow action and its Pega 7.1.7 replacement Transfer Assignment (pyTransferAssignment) might appear in the Select Action menu on the Bulk Actions tool.

Either of the following situations can cause this behavior:

  • The original application did not contain the UI-Kit-7 ruleset, for example, the application was built on Pega 7.1.5.
    • The default flow actions are based on BulkProcessTransferFlowAction system settings.
    • If you add pyTransferAssignment as a local action in a case type rule, users will see both old and new actions.
    • The flow actions are still available unless you override the settings.
  • The upgraded application uses the UI Kit ruleset, but the Transfer local action was defined in the original case type rule and copied to the application.
    • The original is explicitly defined in the application.
    • pyTransferAssignment is available through the system settings in the UI Kit.

As a best practice, upgrade Transfer flow actions to Transfer Assignment in your flows and local actions. The UI Kit ruleset ensures that the new flow actions are optimized for mobile interfaces. In addition, Transfer Assignment provides multiple transfer functions (to manager, workbasket, advanced options) in a single form.

Alternatively, keep the original system settings so that the existing flow actions are still available.

ShowWarningOnForm is no longer processed

Valid from Pega Version 7.1.7

Rule forms now display all warnings, independent of category or type. The standard decision tree Embed-Warning.ShowWarningOnForm is no longer used to determine which warnings are visible.

You can safely remove any specialized versions of this rule in your application.

Use JDBC 4 compliant drivers for better performance

Valid from Pega Version 7.1.7

For better performance, ensure that you are using JDBC 4-compliant drivers.  For more information on supported and non-supported JDBC drivers, please reference the Platform Support Guide.

Use Tomcat 7 for better performance

Valid from Pega Version 7.1.7

For better performance with a Tomcat web server, use Tomcat 7.

Tomcat 6 has a limitation that causes the server to treat the JDBC driver as if it were a JDBC 3-compliant driver, even if the system is using a JDBC 4-compliant driver. Customers using Tomcat will see better performance if they upgrade to Tomcat 7 and use a JDBC 4-compliant driver.

Engine will not start if the incorrect JDBC driver is used

Valid from Pega Version 7.1.7

The engine will not start up if the incorrect JDBC driver is used. The following configurations are unsupported:

  • Using a Multi-tenant Oracle system with one of the Oracle JDBC drivers with issues (see the chart in the Platform Support Guide)
  • Using a Multi-tenant system with a JDBC 3 compliant driver, OR with Tomcat 6 (for more information on using tomcat with Pega 7.1.7, see Use Tomcat 7 for best performance)
  • Using Microsoft SQL Server with a JDBC 3 compliant driver, OR with Tomcat 6 (for more information on using tomcat with Pega 7.1.7, see Use Tomcat 7 for best performance)

When any of these unsupported configurations are encountered, Pega 7 will not start. Before this change, the engine would appear to start up properly, but would encounter issues during other parts of the engine startup or during actual use of the system.

List view and summary view reports might not display in HTML5-compliant browsers

Valid from Pega Version 7.1.7

List view and summary view reports use framesets to provide a view of drill-down reports. HTML5 does not support framesets, so these reports might not display well, or at all, in versions of browsers that are compliant with HTML5.

To prevent display issues, re-create the custom list view and summary view reports that you need as report definition reports. Standard management reports are already available as report definition reports.

As of Pega 7.2, list view and summary view rules are deprecated. For more information, see Discontinued support for list view and summary view rules.

Noticeable differences between work objects created in the Decision Manager portal when compared to Designer Studio

Valid from Pega Version 7.1.7

In the Decision Manager portal, you create work objects by running flows in the enterprise application that serves as the base application for the application overlay. If the enterprise application does not include the UI-Kit-7 in its application rulesets, work objects can display differently in the Decision Manager portal when compared to Designer Studio because an application overlay is always configured to include the UI-Kit-7 ruleset.

Recommendation:

  1. Add the UI-Kit-7 ruleset dependency to the enterprise application.
  2. Redesign the user interface to comply with the UI-Kit-7 ruleset.

Offline mobile apps require Dynamic Container to use frameless Single Document mode

Valid from Pega Version 7.1.7

You can add a Dynamic Container (DC) directly into a Dynamic Layout cell. When creating a custom mobile app with offline capability, you must use the frameless Single Document mode of DC.

Note that mobile offline capability does not support using a framed Single Document mode.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us