SR-118884 · Issue 172536
Create Work correctly encodes Japanese characters
Resolved in Pega Version 7.1.7
When Japanese characters are passed as parameter to Create Work action, the newly created work item was registering cryptic characters instead of the expected Japanese characters. This was traced to a deprecated API, and has been corrected.
SR-119130 · Issue 173876
"?" character allowed in URLs with get requests
Resolved in Pega Version 7.1.7
When specifying an Alternate Domain URL for a link, if the URL contained a GET request followed by parameters ("?get&p1"), the URL was modified by SafeURL to include an "=%26" between the "?" and "get" ("?=%26get&p1") (%26 is url encoding for an ampersand & ). In order to ensure alternate URLs are properly processed when they contain "?", a check has been added.
SR-119158 · Issue 175351
Amended login caching to be compatible with new versions of Firefox
Resolved in Pega Version 7.1.7
When using the latest versions of FireFox browser (32+), there was a problem with logging in again after logging out. This was caused by a change in the cache engine for Firefox, and the system has been updated to compensate for the difference in caching.
SR-119239 · Issue 173898
Max limit error localized and variable added for unsaved work items
Resolved in Pega Version 7.1.7
In order to allow a local value for the number of unsaved work items, a new Field value has been created : MAXIMUMTABSALERT. In addition, the error message text "You have reached the maximum limit for pending changes. Please commit/cancel one or more changes to continue" is now available for localization.
SR-119537 · Issue 174774
Improved speed for deleting repeat grid rows with Dynamic Select
Resolved in Pega Version 7.1.7
When deleting rows from a repeat grid with Dynamic Select and heavy HTML, deleting the first one was very fast but a delay appeared when there was one row left in the repeat grid. The browser message "Pegacloud not responding due to a long-running script" would also be displayed. This was found to be caused by a list-to-list control function being invoked for each processOnBeforeSubmit call which generated an increased number of input elements in the form. This has been corrected.
SR-112935 · Issue 166182
Repeating grids enhanced to allow the '&' character as text
Resolved in Pega Version 7.1.7
When values in a repeating grid contained the character "&", the ReloadSection activity failed with an illegal argument tracer and no values were passed to a second Repeating Grid Page List. This was traced to '&' being used by the system to perform a split of value string. In order to allow use of the '&' character in the list values field, it will now be encoded so it is passed without evaluation.
SR-115387 · Issue 164437
Flow Action support tuned for MenuBar keyboard navigation
Resolved in Pega Version 7.1.7
Using the' MenuBar' setting to display the flow actions for pyActionArea was not working as expected with keyboard navigation within the "other actions" menu: the Up/Down keys moved the cursor, but pressing the Enter key did not fire any actions because a mouse click was expected. An enhancement has been added to the logic to support an enter key event for menu items. In addition, the "other actions" menu was not accessible with keyboard navigation from the Resolve Flow action. This has been corrected.
INC-136969 · Issue 585546
Section and Paragraph rule types added to Revision Manager
Resolved in Pega Version 8.5.1
An enhancement has been made to add support for section and paragraph rule types in revision management. With this change, the sections and paragraph rule types can be added to overlay and can be added to change requests and modified.
INC-138103 · Issue 585639
Enhancement added for node heartbeat recovery process
Resolved in Pega Version 8.5.1
Nodes were not showing up in the admin portal even though they were up and running and could be seen in the pr_sys_statusnodes table. The exception "An exception was encountered while invoking the cluster membership listener callback" was seen. All nodes became visible again after multiple restarts. The root cause was traced back to a temporary database connectivity problem. The database itself was fine according to database monitoring reports, but a network problem, a slow database query, or another issue prevented Pega from establishing a connection for more than a minute. An enhancement has been made to resolve this: if a node becomes unhealthy due to the service registry missing due to a failed heartbeat, the heartbeat will try to recover after 60 seconds and keep trying every 30 seconds until it succeeds.
INC-136128 · Issue 580227
Data Transform added to support Kafka custom serialization/deserialization
Resolved in Pega Version 8.5.1
Previously in a Kafka DataSet it was possible to either serialize or deserialize messages as mapped objects to JSON, or to implement some other mechanism to achieve the expected results. An enhancement has now been added to the Pega platform functionality: DataTransformSerde will be available to be used as custom serialization/deserialization mechanism in Kafka DataSet.