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-179727 · Issue 704545
Modified batch requestor handling to ensure cleanup
Resolved in Pega Version 8.6.4
A large buildup of batch requestors was seen, and restarting the node did not clear it. Investigation showed that in the case of one class reading a DSS value, a Pega requestor was being created when it was unable to retrieve any Pega context, and this requestor was not cleaned up afterwards. To resolve this, an update has been made to the way the requestor and Pega context is being created along with ensuring it will be cleaned up properly after use.
INC-180246 · Issue 664947
Support for apostrophe added to keyword tokenization
Resolved in Pega Version 8.6.4
A keyword containing an apostrophe was not detected properly in Text extraction model. This has been resolved by updating the annotator used in the tokenization.
INC-192826 · Issue 685797
PMML updated for nested 'if'
Resolved in Pega Version 8.6.4
Running a model on the openscoring API and the Pega PMML model gave different results. This has been resolved by updating the handling for nested 'if' in PMML.