SR-D41636 · Issue 509432
Route to configuration in the approval flow accepts Specific User parameters
Resolved in Pega Version 8.4
Route to configuration in the approval flow was not accepting a parameter value/property value when select Specific User option from drop down was chosen. This was traced to unique ID change work done in the 8.2 release: the pzSimpleApproval section has two controls (DropDown for Participant & AutoComplete for Operator) configured on same property pyOperatorToAssign with "run visibility on client configuration), and when the control value was being changed in the AutoComplete control, the empty value of DropDown control was being posted to the clipboard. To correct this, the section Work-.pzSimpleApproval has been modified to remove performing run-visibility conditions at client side. Instead, the system will use the ".pyApproverType Changes" condition to refresh the wrapper DL which contains the routeTo type Operator/WB/Participant property controls.
SR-D43783 · Issue 509909
Comments explicitly excluded from generated ruleset under localization
Resolved in Pega Version 8.4
A generated URL link from Correspondence Fragment (WorkLink) which was saved in Pega-ProCom_ja was incorrect due to an incomplete URL. The ruleset Pega-ProCom_ja is not provided from the platform, but is generated when using localization. In this case, a comment fragment was included in the rule when it was generated, causing the issue. To resolve this, comment handling has been updated to ensure it's not included when generating the rule.
SR-D44942 · Issue 518355
Guided tour popups handling added for right-to-left language locales
Resolved in Pega Version 8.4
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-D56347 · Issue 523276
Pega unit for case type records user inputs
Resolved in Pega Version 8.4
When creating a Pega unit for the case type by selecting Actions -> Record test case for Case, the user inputs were not recorded for embedded page properties. This has been corrected.
SR-D63031 · Issue 526244
Reusable assets default option populated correctly for new application
Resolved in Pega Version 8.4
When creating an application with at least two case types where each case type belonged to different class groups and pointed to different tables but were configured to have only one work pool, operator work pool values for pxThread and pxRequestor did not correctly reflect the different access group settings. This was traced to the inheritance of default values when the portal pyPortal.pyDesktopType was set to Composite, which caused the system to always take the value from the work pools in the application whether or not it was the same value as specified. A check has now been added so that the system will only default to using the value from the work pool if no value has been specified.
SR-C78603 · Issue 417128
Expression Builder will flag local variables
Resolved in Pega Version 8.4
An enhancement has been added to Expression builder which will display a warning in the test panel evaluation if there are any local variables in the given expression.
SR-D16433 · Issue 499297
Exception handling added for upgraded custom decision tables
Resolved in Pega Version 8.4
After upgrade, the status fail message "There has been an issue; please consult your system administrator" appeared with a blue screen in the Run window when attempting to run a Decision table from Actions-> Run option. This impacted the ability to create unit test cases. Analysis showed the issue occurred for any decision table where "Evaluate All rows" was enabled and list properties were used in Actions if there was no value for the list property after the execution of decision table. This was traced to a NullPointerException in a RunRuleFromPage activity in a customized in PUnit ruleset, and was caused by having list properties in the actions of a decision table that had not been populated during rule execution. Exception handling has been added to resolve this.
SR-D18726 · Issue 501390
Application quality page retains info on reopen
Resolved in Pega Version 8.4
When the application quality page was accessed for the first time the page displayed all the data properly, but if it was closed and then opened again all the counts were blank. This was traced to an issue with converting the date from the client to the database, and was seen when the Oracle database had date filed as key and type date. The issue did not occur if the type was varchar2. To resolve this, the system will use obj-open-by-handle instead of obj-open while fetching the details of AQD.
SR-D26334 · Issue 495322
Restore delegated rules short description header
Resolved in Pega Version 8.4
For delegated rules like SLA/Correspondence, the short description was not getting displayed in the header. This was an unintended side effect of work done on automation rule capabilities, and has been resolved by restoring the layout visibility condition pzDelegateHeader in pzRuleFormKeysAndDescription.
SR-D27041 · Issue 499048
Manual value group addition support available
Resolved in Pega Version 8.4
In a test case created for a data transform containing a value group property, that value group property could be added by clicking the + sign in the left pane of the test case, but a value group property could not be added manually by clicking the add row button. This has been resolved by adding support for manually adding value list/value groups. The activity steps which were using @java function have also now been replaced with a getproperty function.