SR-D85551 · Issue 548075
Resolved touch events issue with updated Google Chrome
Resolved in Pega Version 8.3.3
After upgrading Google Chrome, touch events on a flow action under the Action Button in a case or on the application under "Launch web interface" were not reacting and the flow actions were not accessed. Investigation showed that Google Chrome's latest upgrade (79.0.3945.130) removed the ontouchstart property in the window, causing the isTouchable capability identification method to fail. This has been resolved by adding a check for navigator.maxTouchPoints to identify for Google Chrome whether the device involved has a touchscreen.
SR-D82882 · Issue 544165
Special characters excluded in the create tag activity
Resolved in Pega Version 8.3.3
The system was allowing the creation of a tag with special characters at the case level from the Actions tab. This was traced to the pxCreateTag activity 3rd step, which passed the current page parameter without invoking the pyValidateTagName activity. This has been corrected by updating the logic.
INC-159836 · Issue 631205
Resolved unnecessary Apache UIMA Ruta logging
Resolved in Pega Version 8.5.5
A high level of exception logging related to Apache UIMA Ruta was seen under high loads due to annotations in the standard Ruta scripts; this did not impact execution, and has been resolved so only relevant events are logged.
INC-169412 · Issue 648881
Cross-site scripting protections updated for Graph Models
Resolved in Pega Version 8.5.5
Cross-site scripting protections have been updated for Graph Models.
INC-170721 · Issue 658959
Stricter criteria set for reusing an SSAExecutionContext
Resolved in Pega Version 8.5.5
After a Strategy was configured with an existing Proposition Filter and the Explain Results box was unchecked, executing the strategy resulted in the error "Stack is empty, cannot pop any more frames". Investigation showed that the SSAExecutionContext object was reused across the two criteria evaluation in Proposition Filter rule: this works well as long as the input is the same across the two evaluations. However, the SSAExecutionContext object also stashed a reference to a PublicAPI object which became stale in the second evaluation and caused the empty stack issue for the given scenario. This has been resolved by providing stricter criteria in deciding when an SSAExecutionContext can be reused or not in the case of Proposition Filter rule.
INC-171594 · Issue 656182
Spell check correctly applied to email body
Resolved in Pega Version 8.5.5
Spell check was not being applied to email body for text analysis in Email Channel. This has been resolved to work irrespective of case.
INC-173859 · Issue 652639
Corrected compilation error for Decision Data component in Strategy
Resolved in Pega Version 8.5.5
After update, a Decision data component defined in Strategy generated an assembly error when looking for class properties. This was traced to the use of "applies to" Instead of SR class, and has been resolved.
INC-174550 · Issue 658392
Alternative pyLabel source for Auto-generated Proposition Filter added as fall back
Resolved in Pega Version 8.5.5
After using save-as to move an offer/action rule containing eligibility criteria into a new ruleset /branch, the criteria disappeared. Proposition Filter has an explicit dependency on relevant records, and in this scenario investigation revealed all of the relevant records had been previously deliberately deleted. Using save-as on auto-generated CDH rules like actions is also not a best practice. To better handle unexpected actions like these and avoid the hard dependency on Relevant Records, when creating the Proposition Filter via the programatic API the system will fall back to reading the label from the sourcePage if is not possible to get the label from Relevant Record.
INC-175707 · Issue 655346
Multi-level strategy gives correct rules during Batch run
Resolved in Pega Version 8.5.5
When using a nested page structure with multi-level strategies that loop through each page and process the customer, a customer with two linked customers A and B had the results of A overridden by B during Batch Processing while single case canvas testing showed the correct results. This was caused by the DSM clipboard page method of carrying the parent page info not supporting the re-use of pages, and has been resolved by adding an enhancement that will sanitize the strategy stage processor to ensure the correct page reference is used.
INC-176757 · Issue 657784
Running strategy on a different data flow
Resolved in Pega Version 8.5.5
Customized Interaction History properties that had been added to pyInteractionHistoryConfiguration and pyDefaultWorkingSet and saved into the PR_DATA_IH_FACT table were not being saved properly after upgrading from 7.3 to 8.3. This was a missed use case and has been resolved.