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 schema error on z/OS split schema upgrades from versions before Pega 7.1.8

Valid from Pega Version 4.1

When upgrading to a split schema on Pega 7.x with IBM DB2 for z/OS, you see an error during the data schema upgrade when the system tries to drop the PRPC_Updatescache procedure. Because triggers on rules tables use PRPC_Updatescache, you must use the ZOSDisableTriggerScripts to disable these triggers before you update the data schema.

  1. Follow the instructions in the Pega 7 Platform Upgrade Guide to upgrade the rules schema, but stop immediately before you upgrade the data schema with the upgrade.bat or upgrade.sh script. The Pega 7 Platform Upgrade Guide is on the Support > Deployment Guides page.
  2. Copy the contents of the <distribution>\ResourceKit\ZOSDisableTriggerScripts directory into the <distribution>\scripts\ directory.
  3. Run fixZosTriggers.bat or fixZosTriggers.sh with the following arguments:
    --action preupgrade
    --dataschema <data schema name>
    --oldrulesschema <old rules schema name. If you are upgrading from a single-schema system, this is the data schema name.>
    --newrulesschema <new rules schema name>
    --automaticddl <Optional. Set to true to automatically apply the disable trigger SQL scripts.>

    For example:
    fixZosTriggers --action preupgrade --dataschema pegadata --oldrulesschema pegarules --newrulesschema newrules --automaticddl false

  4. If you did not set --automaticddl to true in the previous step, run the <distribution>\schema/disable.sql script to manually disable the trigger SQL scripts.
  5. Run the data schema upgrade as described in the Pega 7 Platform Upgrade Guide.

Internet Explorer 11 support

Valid from Pega Version 7.1.5

7.1.5 now provides support for Internet Explorer 11 (IE11). For those customers interested in information about IE11 support in previous releases, refer to the Platform Support Guide.

Automatically remove all inline styles

Valid from Pega Version 7.1.5

To ensure reusability and ease of maintenance, you can remove inline styles from all sections in all unlocked ruleset versions in your application from the HTML Application Readiness landing page. In the Sections Using Inline Styles section, click the Remove inline styles from all sections button.

 

Automatically upgrade smart layouts to dynamic layouts

Valid from Pega Version 7.1.5

An automated command that upgrades from a smart layout to a dynamic layout is available in Designer Studio when creating new section layouts. Note that some smart layout configurations may not have a one-to-one correspondence with dynamic layouts, so these require some modification.

EAR support for JBoss EAP 6

Valid from Pega Version 7.1.5

PRPC deployment in JBoss EAP 6 as an EAR archive is now supported. 

If you need to deploy the JBoss EAR file, go to My Support Portal and submit a Support Request. GCS can assist you with the procedure.

Format options in DateTime control

Valid from Pega Version 7.1.5

Several updates were made to the section and harness DateTime control.

First, this control now allows selection of both the MM/DD/YYYY and the DD/MM/YYYY format from the Date format dropdown menu.

Second, the number of characters used when inputting a date will be the same regardless of the date. For example, 1/1/2014 displays as 01/01/2014. In a data grid, this ensures that the date text in a column is aligned.

Third, you can now create a custom date format using the Java-supported custom date formats for both the Date or Date/Time types.

Following is an example of the new dropdown when selecting the type Date:

108891_custom-date_date-only.png

Following is an example of the new dropdown when selecting the type Date/Time:

108891_custom-date_date-time.png

Finally, as an example of custom date and time formatting, entering EEE, MMM D, YY H:MM A in the "Custom" field displays as Sat, May 1, '99 2:00 PM, as shown below:

108891_customer-date_runtime.png

Specify control widths in the skin

Valid from Pega Version 7.1.5

This feature enables you to control the width of controls added to dynamic layouts instead of using the default 100% width of the dynamic layouts. You can now specify the widths as dynamic layout skin settings.

Access Manager portal

Valid from Pega Version 7.1.5

Changes to the Access Manager simplify the process of modifying the access rights of features for an application. The changes, including creation of an Access Manager portal, make it easier for non-technical users, such as business architects, to set access rights even if they may not have a deep understanding of Pega 7's security model and class inheritance structure.​

Service levels for case stages

Valid from Pega Version 7.1.5

Service levels are available for stages in stage-based case management applications.

The service level starts when a case enters a stage and stops when it exits. The service level is defined in the Service level for stage field on the "Stage Configuration" dialog, which is accessed on the Case Designer Stages and Processes tab.

108951_stagesla.png

Alternatively, you can add a stage service level on the case type record's Stages tab.

Customize your starting flow list

Valid from Pega Version 7.1.5

The Designer Studio Create menu now populates the list of starting flows by referencing the case types that you select (including case types in Create Menu checkbox) on the application form's Cases and Data tab. The order of the case types on the tab dictates the order of flows that appear on the menu.

108956_CreateCaseMenu.png

Previously, the Create menu displayed all starting flows in the current workpool. This new feature enables you to control which flows appear on the menu.

You can change the sort order by customizing the extension activity pySortStartingFlows. For example, you can sort the flows by their short descriptions.

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