SR-D44942 · Issue 518353
Guided tour popups handling added for right-to-left language locales
Resolved in Pega Version 8.1.8
Guided Tour Popups were still appearing in the default EN location after switching to the ar_AR locale. This was traced to a missed use case for locales using a right-to-left mode such as Arabic or Hebrew, and has been resolved by updating the guided tour engine openPopOver function to account for the HTML tag dir attribute for value of "rtl". This will anchor the pop over to rightBottom / and display the arrow on the rightTop instead of leftBottom / leftTop.
SR-D79266 · Issue 544531
pyStatusWork for parent case correctly resolved
Resolved in Pega Version 8.1.8
pyStatusWork was not getting updated for the parent case even though the case passed through the resolution stage. This was an unintended side effect of work done regarding resolving a subcase if it was opened from the review harness, and has been resolved by updating the findPageByHandle activity to return the correct page when there are multiple pages with the same key.
SR-D54963 · Issue 524113
Updated Decision Table validation for multiple OR conditions
Resolved in Pega Version 8.1.8
When the Decision Table had multiple OR conditions, the table was verified as consistent even when two rows had the same value. Analysis showed that when Show Conflicts encountered multiple 'or' conditions in a row that matched the same conditions in other rows, it considered them to be different rows. This has been corrected.
SR-D54984 · Issue 529208
Resolved ruleset save issue for Google Chrome/IE
Resolved in Pega Version 8.1.8
When using particular versions of Google Chrome or IE, the intermittent error "pyComponentInterfaceClass: <user> does not exist or is not a valid entry for this ruleset and its prerequisites" appeared when attempting to validate an application, and the ruleset could not be saved. This was traced to changes made in the browser around password handling, and has been resolved by explicitly clearing out the pyComponentInterfaceClass if that value is not in use.
SR-D70447 · Issue 533598
SQL injection protection added to Circumstanced Search
Resolved in Pega Version 8.1.8
Parameters used by the PegaAccel-Task-CircumstanceSearch.pzGetCircumstancePropValues activity are now encoded to prevent SQL injection attacks.
SR-D72672 · Issue 536387
Security updated for CreateOperator
Resolved in Pega Version 8.1.8
In order to improve security, CreateOperator in Pega-ProCom will require authentication to run with pxCanManageUsers privilege.
SR-D75469 · Issue 538120
Resolved null-pointer exception in Expression Builder launch from activity rule
Resolved in Pega Version 8.1.8
A NullPointerException occurred in SafeURL when trying to launch the Expression Builder from an activity rule. This was trasced to a failure to get a value property in a target field due to the target element and its parent element containing the same value for name attribute. This caused the parent element to be considered instead of the target element. To resolve this, the search for the target element in parent tag will use '$p' along with 'target element name' in query selector.
SR-D87673 · Issue 548628
PegaCESvcsIntegrator security updated
Resolved in Pega Version 8.1.8
Security updates have been made which now require authentication to consume the services from the PegaCESvcsIntegrator package.
SR-D47795 · Issue 524674
Fallback to Pulse notification added for empty incoming account in CallEmailAutomation
Resolved in Pega Version 8.3.2
After upgrade, issues were seen with the sender receiving email notifications for sent messages when alias addresses were used for incoming emails. To resolve this, a fallback mechanism to use a Pulse notification has been added in cases where an incoming email account is not found in the pyCallEmailAutomation activity.
SR-D48246 · Issue 518689
TextAnalyzerClass will be populated during upgrade if not present
Resolved in Pega Version 8.3.2
After upgrading, the email channels were failing to process the emails and the error "Unable to load data page D_pyEntityClassMapping. Required parameters : ClassName cannot be blank" was seen in the tracer log. Analysis showed the email channels were failing to process the emails due to the pzUpgradeVersion property in Data-Channel-Email instances being inconsistent post-upgrade. To resolve this, the system has been updated so if the TextAnalyzerClass or name property is not present in old email channels (created in 7.4), it will populate that property in the upgrade activity with the default classname.