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.

Stage-related audit notes

Valid from Pega Version 7.1.6

History notes for the following stage-related process steps appear on the user form's Audit tab:

  • Automatic Stage Transition
  • Manual Stage Transition
  • Process Stage Transition
  • Stage Skipped
  • Stage Started

You can select the ones you want to turn off for a given case type by copying the standard decision tree Work-.FilterHistory to your application ruleset and updating the above parameter entries.

Redesigned Process Modeler property panels

Valid from Pega Version 7.1.6

Process Modeler property panels have been reorganized so that it's easier to find the properties and fields you're likely to want, and quickly create the configuration you need. To enhance ease of use:

  • Tabs were eliminated.
  • All fields are located on a single panel and are grouped by their function.
  • The most commonly used fields appear at the top of the panel and are clearly visible.
  • Field and functionality of interest to advanced users are organized into an expandable Advanced section positioned at the bottom of the panel.
  • Business-friendly labels and headings, and instructional text make it easier for non-technical users to quickly understand the meaning and purpose of each field.

113786_assignmentpanel.png

Flexible inputs in strategies

Valid from Pega Version 7.1.6

Decision parameters allow business users to influence the decision through flexible inputs that do not require changing strategies. System architects use extension points to configure the data model and user interface supporting decision parameters. Decision parameters are used in strategies, and changes to the values of decision parameters become immediately available without requiring any changes to the strategy.

The rule pxRunDecisionParameters supports the use of decision parameters through activities.

Enable business users to own parts of an enterprise application

Valid from Pega Version 7.1.6

Decision Manager functionality allows business users to own parts of an enterprise application within the boundaries defined by IT. PegaDM includes the Pega-DecisionManager ruleset that supports this functionality.

System architects define the boundaries for business users in the Decision Manager portal using revision management and proposition authorization facilities in Designer Studio. Access control is provided through custom roles, which system architects can create based on granular privileges. The Decision Manager portal provides business users with a controlled environment for the workflow, and the activities necessary to address the objectives of a revision.

Predefined inputs when designing and testing strategies

Valid from Pega Version 7.1.6

External input settings allow for propagating results to other strategies, providing strategy designers with a mechanism to reuse strategies and test strategies with predefined inputs.

Design segmentation trees in strategies

Valid from Pega Version 7.1.6

You can include the traditional segmentation tree pattern in your strategies using the following features:

  • Exclusion components to conditionally stop the propagation of decision results.
  • Split components to branch the decision results according to the percentage of cases covered by the result.
  • The Otherwise label for component connections where one of the outgoing connections has a defined label.

Simplified Adaptive Decision Manager Deployment

Valid from Pega Version 7.1.6

The Adaptive Decision Manager (ADM) server relies on automatic detection of the database dialect. This simplifies the number of deployable archives used to set up the ADM service.

Cumulative calculation in strategies

Valid from Pega Version 7.1.6

Iteration components provide strategies with a mechanism to perform cumulative calculations.

Quickly add an attachment step to your processes

Valid from Pega Version 7.1.6

The Attachment step allows you to quickly add an Attach Content subprocess to your flow. Once added, choose the attachment type and instructions to present to users:

113931_attachment.png

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