INC-164439 · Issue 657995
Setting added to customize using blank Map values
Resolved in Pega Version 8.7
After upgrade to from Pega 6 to Pega 8 some of the Map Value rules were not working. This was due to the handling for blank default values which was changed in Pega 7. In order to support backwards compatibility, a new 'when' rule has been added which allows customizing whether or not blank values are allowed for the Map value default columns. pyAllowBlankValues will default to "false".
INC-185950 · Issue 669195
Withdraw task notification uses correct email sender
Resolved in Pega Version 8.7
When withdrawing a Task, the withdraw email was sent from the default email box instead of the expected Application default email box. This was traced to the 'pyTaskDeleted' (notification name for withdraw task) value not being present, which meant the system fell back to the task 'pyTaskAssigned' notification name. To resolve this, an update has been made to have pyIsPulseNotificationDefinition return true for a pyTaskDeleted notification.
INC-216490 · Issue 713633
pxIdentifier dynamically set for DecisionData while using GOS
Resolved in Pega Version 8.7.2
When using a Decision Data component in a strategy which was wrapped with Globally Optimized Strategy (GOS), no results were generated from the DataJoin shape under optimized execution. Investigation showed this was caused by a missing .pxIdentifier for the DecisionData shape during GOS execution. There was a workaround of unselecting the checkbox on the Advanced tab in the Decision Data component, but this has been resolved by updating the strategy kernel service so it will dynamically construct the pxIdentifier based on the skills assignment module (SSA).
INC-197530 · Issue 686027
Value Finder updated for use with external Cassandra nodes
Resolved in Pega Version 8.7
Attempting to use the Value Finder feature resulted in the error "Running Simulation is not possible because the required services are not available. Contact your System Administrator to enable the data flow and decisioning data store services." Analysis traced this to a check which identifies whether there is more than one internal node available for CDH/ DSS node. Since there were only external nodes available in this scenario and no internal nodes, the method returned false and returned the error when the CDH / VF page was launched. To resolve this, the check has been modified to allow for external Cassandra.
INC-168254 · Issue 659297
Documentation updated for accents and special characters used in search
Resolved in Pega Version 8.7
The "Pega search API" article has been updated to reflect that the search functionality in Pega Platform does not match accented words with unaccented. For example, searching for santé and sante will retrieve different results. In addition, Domain Specific Language (DSL) includes special characters for use when searching, for example '-', '_', '!', '@'. However, the system retrieves various results depending on the way the special characters are used in the search query. If the query contains special characters that are not escaped, the system may retrieve incorrect results. For example, not escaping the slash mark in the 25/02 query may cause the system to ignore the special character.
INC-164947 · Issue 639862
Handling added for missing div when opening work object
Resolved in Pega Version 8.7
In mobile offline app, opening a work object in a specific scenario for the second time resulted in an endless busy indicator. It was not possible to navigate away, and the app had to be closed and reopened to continue. Investigation showed that some app sections had an action that tried to load a harness section where one specific div was missing, and this has been resolved by updating reloadSectionOSCOHandler to handle the missing div in the failure callback. Additionally a console.error() will appear for the missing section.
SR-108805 · Issue 149539
Help updated to explain When Rule "ALL" Evaluation behavior
Resolved in Pega Version 7.1.7
A 'when' rule evaluating all pages in page list will only evaluate the properties on pages in the list that contain that property. This may cause a "true" result that does not match customer expectations. The hover help has been clarified to explicitly state that the evaluation results apply only for those pagelist entries where the property exists and not for all the page list entries.
SR-116805 · Issue 175879
Focus highlighting added to sub-tabs when they receive focus
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
Focus highlighting was not appearing around sub-tabs when they received focus. There was a CSS workaround for this, but it has been resolved.
SR-117428 · Issue 169351
Resolved performance issues when R-D-E referenced a data page
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
If a declare expression referenced a data page, loading or refreshing a section in update mode caused Rule-Declare-Expression to check whether inputs had changed. The R-D-E then loaded the data page (but didn't pass any parameters), causing the data page to load the max number of pages allowed. Subequently, a series of other R-D-Es fired on that data page as inputs had changed, ending up with a large number of R-D-E's firing that weren't required for a section. As a result, the elapsed time was higher than expected for every screen where this was happening and CPU consumption was high. Auto Population should only trigger on reference to a non-key and non-param property, and this has been implemented.
SR-117428 · Issue 170976
Resolved performance issues when R-D-E referenced a data page
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
If a declare expression referenced a data page, loading or refreshing a section in update mode caused Rule-Declare-Expression to check whether inputs had changed. The R-D-E then loaded the data page (but didn't pass any parameters), causing the data page to load the max number of pages allowed. Subequently, a series of other R-D-Es fired on that data page as inputs had changed, ending up with a large number of R-D-E's firing that weren't required for a section. As a result, the elapsed time was higher than expected for every screen where this was happening and CPU consumption was high. Auto Population should only trigger on reference to a non-key and non-param property, and this has been implemented.