Simultaneous editing of propositions in revision management
Valid from Pega Version 7.2.1
When you refine proposition data in Decision Strategy Manager, you can now delegate various propositions that belong to a single decision data rule (for example, multiple propositions from a specific issue or group) to different users. These users can simultaneously edit the proposition data that was assigned to them (the same proposition cannot be part of two open change requests). With this solution, users can modify the proposition data independently, without locking the entire decision data rule for other users while the proposition data is being revised. The ability to view and select all proposition-related data makes it possible to consistently revise not only propositions themselves, but also all associated rules.
For more information, see Proposition-centric revision management functionality.
Easy access to proposition-related rules when creating change requests in revision management
Valid from Pega Version 7.2.1
When selecting propositions for change requests in Decision Strategy Manager, you can view the proposition filter, strategy, and when rules that are associated with the decision data the selected propositions belong to. In addition, you can include those rules in change requests. To view and add any associated rules to a change request, the rules must be part of the application overlay. With the ability to view and select all proposition-related data, you can consistently revise not only propositions themselves but also all associated rules.
For more information, see Proposition-centric revision management functionality.
Dynamic System Setting for selecting clipboard pages implementation
Valid from Pega Version 7.2.1
Create the dsm/clipboard/optimize Dynamic System Setting to select which clipboard pages to use for strategies and data flows in all contexts. Without this setting or with its value set to true, strategies and data flows work on DSM clipboard pages. When you set the value to false, strategies and data flows work on the conventional Pega 7 Platform clipboard pages. This Dynamic System Setting allows you to configure run strategies consistently and obtain consistent results.
For more information, see DSM clipboard pages implementation.
Enhanced Expression Builder for certain rule types
Valid from Pega Version 7.2.1
For certain rule types, several enhancements to the Expression Builder help you to efficiently build expressions in a user-friendly environment. Enhancements include:
- The ability to use single-line or multi-line comments to explain the purpose of the expression.
- Formatting, such as tab characters and carriage returns, that is preserved the next time you open the Expression Builder after closing it.
- Real-time validation of expressions so that you receive immediate feedback about the syntax in your expression.
- The ability to test the input value of a property for a portion or all of the expression.
These enhancements apply to the Expression Builder for the following types of rules:
- Data Transform
- When
- Map Value
- Decision Tree
- Decision Table
- Strategy
For more information, see Expression Builder enhancements for certain rule types.
Pega Composite Gateway not required for Pega Web Mashup
Valid from Pega Version 7.2.1
The Pega Composite Gateway servlet (prgateway.rar file) is no longer required for Pega Web Mashup gadgets. You can now use web mashups without deploying the Gateway. Support for the Gateway will continue, but it is a best practice not to use it for the Pega Web Mashup in Pega 7.2.1 and later versions.
Extract marker file not created at startup
Valid from Pega Version 7.2.1
The extract marker file (PegaRULES_Extract_Marker.txt) is not created at startup, because the rule utility libraries no longer need it. If you used to use the extract marker file to clear the static content file-based cache, to look up lists, or to control starting activities with web nodes, you can delete the contents of the PegaRULES temporary directory instead.
The UpdateAdaptiveModels agent causes an exception after Pega 7.2 to 7.2.1 upgrade
Valid from Pega Version 7.2.1
After the Pega 7 Platform is upgraded from version 7.2 to 7.2.1, the log files might show an error that is caused by the UpdateAdaptiveModels agent. This agent is enabled by default and is responsible for updating scoring models in the Pega 7 Platform. If you use adaptive models in your solution, you can avoid this error by configuring the Adaptive Decision Manager service. If you do not use adaptive models, disable the UpdateAdaptiveModels agent.
For more information, see Configuring the Adaptive Decision Manager service and Pega-DecisionEngine agents.
Reconfiguration of the Adaptive Decision Manager service after upgrade to Pega 7.2.1
Valid from Pega Version 7.2.1
After you upgrade the Pega 7 Platform to version 7.2.1, you need to reconfigure the Adaptive Decision Manager service. Beginning with Pega 7.2.1, the Adaptive Decision Management (ADM) service is native to the Pega 7 Platform and is supported by the Decision data node infrastructure.
For more information, see Services landing page.
Upgrade/update fails if PostGIS is applied to PegaRULES or PegaDATA schema
Valid from Pega Version 7.2.1
If you use the PostGIS extension to a PostgreSQL database, upgrading or updating the Pega 7 Platform fails if the extension has been applied to either the PegaRULES or PegaDATA schema. PostGIS can be applied to any other schema.
Email listeners no longer copy the email subject text to the email body
Valid from Pega Version 7.2.1
As of Pega® 7.2.1, email listeners no longer copy the email subject text to the email body when the body is empty. If your customer application expects text in the body of the email, the application might fail. You can configure email listeners to copy the subject text to the body by using the following Dynamic System Setting:
Owning Ruleset: Pega-IntSvcs
Purpose: email/copyBodyNoContent
Value: true
For more information, see Creating Dynamic System Settings.