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.
INC-164002 · Issue 639914
Decision table null input handling updated for backward compatibility
Resolved in Pega Version 8.7
After upgrade, any null values as inputs in the decision tables were skipped if "Allow Missing properties" was not checked. This behavior was different from previous versions. In order to improve backward compatibility, the new function pxEvaluateDecisionTable has been added which has an additional parameter to set AllowMissingProperties, and the older function logic has been modified to take the parameter value from the parameter page.
INC-164171 · Issue 644707
Support added for connect-SOAP run in parallel mode
Resolved in Pega Version 8.7
When connect-SOAP was configured to use the “run in parallel” mode, application settings derived through a datapage had incorrect values. While running the connect-SOAP through an activity, all the values were derived incorrectly. This has been resolved by adding a synchronization enhancement to support parallel run connect.SOAP.
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-165256 · Issue 657037
Improvements for Offer Eligibility rules loading time
Resolved in Pega Version 8.7
After opening the Proposition filter/Action rule and clicking on Add Criteria, the pxAnyPicker drop down load was taking an excessive amount of time. Performance improvements have been made by adding a precondition at step 2 to avoid data page refresh for specific scenarios when it is not required.
INC-167037 · Issue 650991
SmartpromptType classes shown in Rule-Admin-Skill
Resolved in Pega Version 8.7
Some class instances were not showing in SmartpromptType list. This was traced to the activity LookUpList, which is called from Rule- class in Rule-Admin-Skill, using pyClassName as one of the filter criteria in Java Step1. Therefore Rule-Admin-Skills did not show in SmartpromptType list. This has been resolved by overriding LookUpList for Rule-Admin-Skill class so it will not consider pyClassName as a filter criteria.