SR-D77580 · Issue 550093
Corrected Survey button refresh issue
Resolved in Pega Version 8.2.7
After implementing a Pega Survey question page with dynamic / reflexive questions (Answer to Question 1 determines Question 2 and so on) where every answer pick caused a refresh, picking various radio buttons quickly caused an unexpected busy indicator. Investigation showed that on click, both refresh section and run activity were executed asynchronously, triggering the property mapping refresh before answers were clicked. To correct this, the clearSelection function call in pzsurvey_ui_userscript JS file has been modified, and questionPageName has an added 'if' condition.
INC-173436 · Issue 648820
Performance improvement for Application Save: Node Level Data Pages
Resolved in Pega Version 8.5.5
As part of new functionality introduced in 8.3, data types defined in the application record will be turned into data objects on Application save. As part of this process node level pages are invalidated and reloaded and there is an explicit commit that marks the Application record as dirty and sends any calls for the application record to the database for fresh records. In a multi-node environment, the number of queries to get the application record being saved became exponentially higher and performance impacts were seen. This has been resolved by updating the system to skip eager loading of the data page definition when an access rule or application definition is saved.
SR-C58201 · Issue 402953
Hazelcast thread locking improved
Resolved in Pega Version 8.1.1
The system was hanging after attempting Hazelcast locking. Tracing showed threads that seemed to be waiting for the system lock to become available so that they could acquire a database lock. This was caused by an implementation issue in LockUtils that did not wait to ensure that the distributed map's lock was released if it wasn't yet available. To correct this, debug logging has been added to the "LockUtils" class which will print when the lock is acquired or released along with the associated stacktrace. In addition, a wait function has been added to the Distributed Map lock to improve the timing between release and grab.
INC-173436 · Issue 648821
Performance improvement for Application Save: Node Level Data Pages
Resolved in Pega Version 8.7
As part of new functionality introduced in 8.3, data types defined in the application record will be turned into data objects on Application save. As part of this process node level pages are invalidated and reloaded and there is an explicit commit that marks the Application record as dirty and sends any calls for the application record to the database for fresh records. In a multi-node environment, the number of queries to get the application record being saved became exponentially higher and performance impacts were seen. This has been resolved by updating the system to skip eager loading of the data page definition when an access rule or application definition is saved.
INC-192979 · Issue 678361
Performance improvement for Application Save: Node Level Data Pages
Resolved in Pega Version 8.7
As part of new functionality introduced in 8.3, data types defined in the application record will be turned into data objects on Application save. As part of this process node level pages are invalidated and reloaded and there is an explicit commit that marks the Application record as dirty and sends any calls for the application record to the database for fresh records. In a multi-node environment, the number of queries to get the application record being saved became exponentially higher and performance impacts were seen. This has been resolved by updating the system to skip eager loading of the data page definition when an access rule or application definition is saved.
SR-113384 · Issue 162788
Explicit schema mapping could cause migration script errors
Resolved in Pega Version 7.1.7
While running the migration script, the presence of a custom rule table that explicitly mapped the Data-Admin-DB-Table schema could cause the script to fail. This was caused by the GRANT statements in the SQL script not having the proper assignment for the user name with the "USER" keyword; a group name that is the same as the user name that we are trying to GRANT rights to was ambiguous. The workaround was to temporarily map the custom table to an empty schema, then manually copy this table to the RULES schema afterward, but this issue has been addressed by updating how privileges are granted for the table, procedure and function elements in a split schema.
SR-133681 · Issue 206951
Added handling for two declare index rules on two pagelist properties in the same work class
Resolved in Pega Version 7.1.9
Given two declare index rules on two pagelist properties in the same work class, the second declare index was working while the first declare index was behaving inconsistently. It was found that even though there were two records for the property, at run time only the second record was getting inserted because only one insert command fired for Accounts Pagelist and the Declare index did not update even after using pzReindex is true. To ensure proper function firing, the system has been updated so when pzReindex is true, the existing pzIndexes page group value will not be considered.
SR-B66561 · Issue 316940
Empty grid check added to Add Item (Before) action
Resolved in Pega Version 7.3.1
Using "Add Item -> Before" to add the first row in an empty grid configured with page list as a source showed the following issues: 1. Focus was gone and not set on the first row. 2. The grid header disappeared, and the first row added appeared. 3. It was not possible to delete the first row. Even when manually clicking to set focus on the row, the system still asked for selection of the row to delete. This was traced to the "add before" function using updateHandlesAfterInsert even though the grid was empty. The postUpdate API in ui_grid.jshas been updated with a check to resolve this.
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.