SR-B45960 · Issue 303751
Request & Response logs include POST method submits
Resolved in Pega Version 7.3.1
When using the POST method to send a request, request & response data was not showing up the in DEBUG logs of the Connect-REST execution. This has been corrected, and request & response data is now being added to DEBUG logs in Connect-REST execution.
SR-B49398 · Issue 306482
Request & Response logs include POST method submits
Resolved in Pega Version 7.3.1
When using the POST method to send a request, request & response data was not showing up the in DEBUG logs of the Connect-REST execution. This has been corrected, and request & response data is now being added to DEBUG logs in Connect-REST execution.
SR-B43400 · Issue 307258
Localization added for field value used in 'Enter a Short Description' validation message
Resolved in Pega Version 7.3.1
Localization was failing for the 'Enter a Short Description' validation message when using a Field Value due to the message rule containing spaces. To fix this, a new message rule has been created without spaces in the same ruleset so that it is available for override use in the ruleset.
SR-B48904 · Issue 309328
Localization added to Pega Marketing components
Resolved in Pega Version 7.3.1
Localization support for German, Japanese, Spanish, Italian, French and Chinese simplified has been added for the Pega Marketing application for these components: Proposition Management Landing pages - Issue, Group creation, Un Versioned and Versioned Proposition Creation, Conversion from UnVersioned to Versioned proposition, Decision Data Form, Interaction History Data Set & IH Landing Page, VBD & KPI navigation links from Designer Studio and its Landing Pages. Note : out-of-the-box properties/property values, controls, and pop-ups, can not be localized in these functionalities.
SR-B48904 · Issue 315159
Localization added to Pega Marketing components
Resolved in Pega Version 7.3.1
Localization support for German, Japanese, Spanish, Italian, French and Chinese simplified has been added for the Pega Marketing application for these components: Proposition Management Landing pages - Issue, Group creation, Un Versioned and Versioned Proposition Creation, Conversion from UnVersioned to Versioned proposition, Decision Data Form, Interaction History Data Set & IH Landing Page, VBD & KPI navigation links from Designer Studio and its Landing Pages. Note : out-of-the-box properties/property values, controls, and pop-ups, can not be localized in these functionalities.
SR-B44184 · Issue 309658
Property filter execution updated for better backward chaining
Resolved in Pega Version 7.3.1
in cases where the strategy is cyclically called and backward chaining is enabled, the declarative network was looking to load the value of a property which did not exist, leading to an error. The evaluateWhen function in the proposition filter rule execution has been modified to reset backward chaining.
SR-B48902 · Issue 318395
PegaMarketing localization tuned
Resolved in Pega Version 7.3.1
While localizing the Pega Marketing application, English strings were found in several places from Decisioning in particular, but also in the Platform in general. The localization for these has been fixed.
SR-B50813 · Issue 315070
Improved performance for Proposition updates
Resolved in Pega Version 7.3.1
While updating propositions through DSM portal it was observed that the thread count got very high while overall performance became degraded. This happened in Pega versions where the propositions are data instances and not rules. The issue was traced to the Proposition cache getting reloaded from the database table in a synchronized block; all of the strategy execution threads were waiting until the reloading completed despite strategy reading the propositions from the cache. To resolve this, the system will reload the proposition cache from the database table in the thread where the pulse message is being processed when the node receives the pulse notification. Thus other strategy execution threads will not be blocked and continue reading propositions from the cache.
SR-B66858 · Issue 315685
Cassandra fixes for AIX systems
Resolved in Pega Version 7.3.1
A Cassandra node start failure on some AIX environments was traced to a condition for checking whether Java version 1.7 and 1.8 in file cassandra-env-AIX.sh were present in the dnode-7.2.1.jar. This check is not necessary as the same check is already performed in Cassandra.java class, and it has been removed from the cassandra-env-AIX.sh script. Additionally a new system setting dnode/overwrite_cassandra_env has been introduced to allow disabling replacing cassandra-env.sh script with cassandra-env-AIX.sh (which is normally done on AIX systems).
SR-B66892 · Issue 315757
Cassandra support enhanced for CQL 3 data types
Resolved in Pega Version 7.3.1
The connector was unable to read a date-filed value from Cassandra to Pega Dateonly or varchar datatype, instead failing with an exception. As a result, data was not readable via connect-Cassandra if that table had new column types like (date,time,tinyint,smallint). To resolve this, data type support has been added for the new types in CQL 3.3 (smallint,tinyint,date,time).