SR-119538 · Issue 177397
Detection added for custom work history tables
Resolved in Pega Version 7.1.7
In order to fully embrace mobile capabilities, columns were added to the work history tables to allow actions to be tracked as a geographical map where each history event is a numbered locale indicator on a map instead of a row of entries. From lat/long it is also possible to call a Google service and get the street address as well. However, this functionality caused some issues post-migration with if there were customized pc_history_work tables mapped to custom classes. To remedy this, a check has been added to only query for pxlatitude/pxlongitude if columns are exposed and shown, and that will detect if the columns aren't present.
SR-119869 · Issue 176176
Access Role Editor link errors fixed
Resolved in Pega Version 7.1.7
When using IE11 or Google Chrome, clicking on the hyperlink to a privilege associated with a class in Access Role Editor created issues that prevented changes from being made or saved. In some cases, after clicking 'Remove Checked' in the popup dialog, the developer portal loaded in the popup. This was caused by the forms-based role selection not being converted for cross-browser support, and has been fixed.
SR-117114 · Issue 171740
Added localization formatting for date values (YYYY-MM-DD)
Resolved in Pega Version 7.1.7
In Sweden, dates are given with a hyphen "-" and not slash "/" as the date separator as per ISO-8601. The SV localization has been changed to follow this style.
SR-118567 · Issue 167257
Enhanced task queue handling for custom applications
Resolved in Pega Version 7.1.7
In some situations, a custom agent would periodically fall over when processing a large backlog of queued items. This was caused by an exception thrown when placing a task in the queue when it is already present. The system has been updated to better handle this situation and allow agents to continue to execute with the present schedule when a duplicate task is found.
INC-146098 · Issue 633721
Keyboard shortcuts work in Decision Trees
Resolved in Pega Version 8.4.5
Keyboard short cuts in Decision Trees used to copy/paste by holding ctrl button in Decision Trees were not working. This was an unintended side effect related to changing non-auto grid to an auto-generated hierarchical table to make the Decision tree rule form multi-browser compatible, and has been resolved by adding cut/copy/paste/insert-after/insert-before functionality to the decision tree context menu.
INC-151662 · Issue 626575
Handling added for application which includes production ruleset
Resolved in Pega Version 8.4.5
When creating the Email channel or Webchat channel, the Text Analyzer and its respective class (Data-Decision-Request-MCP-WebChat-xxxxx) was being saved in the ruleset of the built-on application while there were rulesets open in the top application. This was a missed use case, and has been resolved byupdating the logic to account for the scenario where an application includes a production ruleset.
INC-153697 · Issue 625982
Dragon successfully navigates to user profile icon
Resolved in Pega Version 8.4.5
Attempting to navigate to the user profile icon when using Dragon software was not working. This is an issue with how Dragon interacts with the "< i >" element operator icon, and has been resolved by replacing "< i >" with a button and appropriate aria label.
INC-155401 · Issue 630447
Circumstance Definition rules save correctly
Resolved in Pega Version 8.4.5
After upgrade, attempting to save any circumstance definition that used multiple "or" conditions consistently failed during conflict detection. This was an inadvertent side effect of work done to resolve an out of memory error and has been resolved by modifying the Rule-Declare-!testConsistency java step:"int numRows = numOrs;" to"int numRows = numSubRows;".
INC-159238 · Issue 624302
Handling added for identical property and page names in test case recording
Resolved in Pega Version 8.4.5
When trying to record a test case, the error "WrongModeException: The property PostProsSnapOfWorkpage.Name was of mode String while com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl.getPageValue() was expecting Page mode" was generated. This was an edge case caused by property and page names being the same on the "PostProsSanpOfWorkPage" page, and has been resolved by accessing the page with the full path so it has the proper prefix.
INC-161609 · Issue 628996
Unneeded configuration window close icon removed
Resolved in Pega Version 8.4.5
JAWS was not reading the configuration window close icon. This was an outdated control that should have previously been removed from this section, and has now been withdrawn.