Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

Split schema upgrade instructions missing properties

Valid from Pega Version 7.1.3

If you upgraded from 5.x, 6.x, or 7.x using the instructions in previous versions of the upgrade guide, you may have neglected to set the properties below in your migrateSystem.properties file when you migrated your upgraded schema to the source system:

 

pega.rules.objects.generate=true

pega.rules.objects.apply=true

 

If these properties were not set during an upgrade that splits the schema, your environment does not have the indexes, triggers, and primary keys on the rules tables.

 

To check for this issue, see if the pr4_base and pr4_rule rules tables in your existing rules schema are missing primary keys. If they are, use the SQL scripts in the ResourceKit\MigrationRecoveryScripts directory of the release to cleanup duplicate rules that were created due to this issue. Follow the steps below to run the scripts.

To run the scripts on Microsoft SQL, Oracle, or PostgreSLQ

  1. Take down any app servers using the affected schema.
  2. Backup your database.
  3. Replace all instances of @RULES_SCHEMA in <database>_cleanDups.sql with the name of the schema that contains the pr4_base table.
  4. Run the <database>_cleanDups.sql script on the database with vendor tools (sqlPlus, SQL Server Management Studio, etc).
  5. Replace all instances of @RULES_SCHEMA in <database>_fix_vw_table.sql with the name of the schema that contains the pr4_base table.
  6. Run the <database>_fix_vw_table.sql script on the database with vendor tools (sqlPlus, SQL Server Management Studio, etc).
  7. Generate and apply the ddl using the command line generateDDL command. Check the installation guide for your database or the upgrade guide for details about how to use the generateDDL command line script.
  8. Rebuild the indexes for the tables in your rules schema using vendor tools. This is necessary so that your system runs at an optimum speed.
  9. Optionally upgrade to the latest release, at this point your database is ready to be upgraded or used depending on your needs.

      

To run the scripts on DB2 for LUW or z/OS

  1. Take down any app servers using the affected schema.
  2. Backup your database.
  3. Run the <database>_cleanDups.sql script on the database with vendor tools (UDB CLP, Data Studio, etc) to create the CLEANSE_RULES_DUPS stored procedure.
  4. Run the query Call CLEANSE_RULES_DUPS(‘<rulesSchema>’); where <rulesSchema> is the name of schema that contains the pr4_base table.
  5. After the previous step is complete drop the CLEANSE_RULES_DUPS procedure.
  6. Replace all instances of @RULES_SCHEMA in <database>_fix_vw_table.sql with the name of the schema that contains the pr4_base table.
  7. Run the <database>_fix_vw_table.sql script on the database with vendor tools (UDB CLP, Data Studio, etc).
  8. Generate and apply the ddl using the command line generateDDL command. Check the installation guide for your database or the upgrade guide for details about how to use the generateDDL command line script.
  9. Rebuild the indexes for the tables in your rules schema using vendor tools. This is necessary so that your system runs at an optimum speed.
  10. Optionally upgrade to the latest release. At this point your database is ready to be upgraded or used depending on your needs.

Batch database processing improvements

Valid from Pega Version 7.3

Batch database processing has been enhanced to ensure that a constraint violation does not occur when you save transactions to a table with a foreign key dependency. Because batch processing changes the order of save operations, it is disabled for transactions with foreign key dependencies. Disabling batch processing ensures that a record with a foreign key dependency on another record will not be written before the record on which it is dependent.

For more information about how batch database processing works and how to enable and disable it, see Batch processing during database write operations.

Improve cluster security by limiting concurrent operator sessions

Valid from Pega Version 7.3

You can increase the security of a Pega® Platform cluster by limiting the number of concurrent sessions allowed for each operator. Because operators typically do not require multiple concurrent sessions for performing their work, limiting the number of sessions reduces the chance that an unknown or untrusted person could access systems in the cluster. Use the new setting Number of concurrent sessions allowed for each operator on the Production tab of the System Data Instance form to configure the number of concurrent sessions for operators. You must restart your system when you change this setting. You can also create a list of operators by using the presence/maxsessions/operators/whitelist Dynamic System Setting, to which the maximum number of concurrent sessions setting will not apply.

For more information, see System form - Completing the Production tab.

New System Queue Management landing page

Valid from Pega Version 7.3

You can manage your system queues from the new System Queue Management landing page. You can use this landing page to quickly and efficiently debug applications without exiting Designer Studio. In addition to viewing items in a queue, you can defer, remove, and requeue items in a queue, stop items in progress, and view an item's XML.

As a result of this enhancement, the Broken Queue landing page has been removed.

For more information, see System Queue Management landing page.

Data encryption across search nodes

Valid from Pega Version 7.3

You can now encrypt communication among search nodes. Encryption secures the data that is transferred across nodes so that it cannot be accessed by unauthorized hosts. Encryption is enabled by default for new installations and upgrades from Pega® 7.1.6 or earlier to Pega 7.3. Encryption is not enabled by default for upgrades from Pega 7.1.7 or later to Pega 7.3. You can enable and disable search encryption from the Search landing page or by using the indexing/distributed/enable_inter_node_encryption Dynamic System Setting.

For more information, see Enabling and disabling encryption for communication among search nodes.

Node classification

Valid from Pega Version 7.3

By using the node classification feature, which segregates nodes by their purpose, you can now configure one node with multiple node types. When you start a node with multiple node types, the node runs a set of agents and listeners that are associated with the specified node types. From the Node Classification landing page, you can view and configure the agents associated with node types, view listeners associated with node types, and open Agent rule forms, agent schedules, and Listener rule forms.

For more information, see Node Classification, Configuring node types for agents and listener and Node classification.

Support for Couchbase Server NoSQL database

Valid from Pega Version 7.3

Pega® Platform can now read data from and write data to a Couchbase Server database. Couchbase is a NoSQL database that you can use when a NoSQL database better meets your scalability and processing requirements.

For a list of supported and unsupported features, see Couchbase Server support.

Node types renamed after upgrade from Pega 7.2.2 to Pega Platform 7.3

Valid from Pega Version 7.3

If you used node classification in Pega® 7.2.2, when you upgrade to Pega 7.3, node type names are automatically changed to a new name when you start a node with a node type.

  • UniversalNode becomes Universal
  • WebUserNode becomes WebUser
  • BackgroundProcessingNode becomes BackgroundProcessing
  • BIXNode becomes BIX
  • SearchNode becomes Search

If you created agents in Pega 7.2.2, agent schedules are also automatically updated with a new name during the upgrade. For more information, see Customized agent schedules for standard Pega Platform agents must be updated after Pega 7.2.2 to Pega Platform 7.3 upgrade and the appropriate Deployment Guide.

SystemCleaner agent is split into node-level and cluster-level agents

Valid from Pega Version 7.3

The Pega-RULES:SystemCleaner agent has been split into node-level and cluster-level agents to avoid database performance issues. The new node-level agent, Pega-RulesEngine:NodeCleaner, runs on all the nodes in the cluster, while the new cluster-level agent, Pega-RulesEngine:ClusterAndDBCleaner, runs on only one node in the cluster. If you customized the agent schedules of the Pega-RULES:SystemCleaner agent, you must manually update the agent schedules of the new agents because customized schedules are not retained.

For more information, see Agent schedule data instances – Completing the Schedule tab.

Greater cluster stability with client-server clustering topology

Valid from Pega Version 7.3

You can now deploy Pega® Platform in the new client-server clustering topology that uses Apache Ignite, which increases stability in large clusters and provides independent scalability for both servers and clients. This technology separates the client nodes, which are responsible for Pega Platform processes, from the server nodes, which are responsible for cluster communication and distributed features. If your production environment consists of more than five nodes in the cluster, it is recommended that you switch to the new client-server topology.

For more information, see Apache Ignite client-server clustering topology and the appropriate Deployment Guide.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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