SR-D47975 · Issue 514012
OpenRuleAdvanced updated
Resolved in Pega Version 8.3.2
After upgrade, the Update Page and Append and Map to step in Data transform was generating the error "No Server connection while giving page name to Target and Source". This was traced to the OpenRuleAdvanced_OverLabel control, and investigation showed that a variable was not being resolved when invoking pzEncryptURLActionString. This has been resolved by updating OpenRuleAdvanced and reimplementing two parameters as well as moving the call of these variables to the beginning of the script. Security has also been improved by moving some of the encryption to SafeUrls.
SR-D48248 · Issue 517237
cross-site scripting filtering added to URLs
Resolved in Pega Version 8.3.2
Cross-site scripting filtering has been added to prevent the injection of a script into a URL using ViewXML.
SR-D48751 · Issue 515537
Pega unit for case type records user inputs
Resolved in Pega Version 8.3.2
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-D52138 · Issue 537504
Property setting corrected for On Join and Exclusion shapes in Expression Builder
Resolved in Pega Version 8.3.2
The properties for the defined page did not appear when using the type-ahead feature to select properties for the On Data Join and Exclusion shapes in Expression Builder. This was an issue related to the property being referenced for setting the context in the expression builder, and has been corrected.
SR-D54984 · Issue 529796
Resolved ruleset save issue for Google Chrome/IE
Resolved in Pega Version 8.3.2
When using particular versions of Google Chrome or Microsoft Internet Explorer, 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-D55841 · Issue 522694
isAvailable calendar instance will include time zones
Resolved in Pega Version 8.3.2
When using a custom configuration to route assignments, if today was configured as unavailablefrom date, assignments were still routed to the current operator even though they were not available. Analysis showed that the same Calendar was not used to compare date objStartDate, opUnavailableFrom and opUnavailableTo in the function, isAvailable. The isAvailable FUA calculates objStartDate by getting the calendar instance and setting the time by calculating it from the next business day. However, the calendar instance was created from Calendar.getInstance(), which does not use a time zone, and this resulted in a mis-match of time. To resolve this, instead of creating a calendar instance objStartDate will be formatted to YYYYMMDD format and then converted to the requestor time zone timings using Data Time Utils parseDateTimeString.
SR-D60636 · Issue 533046
Check added for empty RelevantRecords parameter to improve performance
Resolved in Pega Version 8.3.2
When there were no relevant properties in given class context, i.e the Param.RelevantRecords value was empty at step#3 of the pxLoadPegaExpressFields activity, the pzGetFieldsDetailsForClass RD tried to fetch all the properties available for that particular class and its hierarchy, causing system performance issues. To resolve this, a jump condition has been added at step#4 of the pxLoadPegaExpressFields activity to avoid further processing when there are no relevant properties in given class, and the "Use null if empty" option for filter condition A in pzGetFieldsDetailsForClass is now checked to avoid fetching all results when the RelevantRecords parameter value is empty.
SR-D61681 · Issue 532559
Handling added for different access groups updating a case
Resolved in Pega Version 8.3.2
When a parent flow was configured with a Wait shape to wait until any AccessChild case reached Pending-Authentication and then the “Update a case” shape was used to update the case status of child cases using a Data Transform, the Wait shape was being processed successfully but the child cases were not always updated as expected. This issue occurred when the cases were processed by users with different access groups, so the ProcessFlowDependencies agent processed the dependency. In this scenario, findPageByHandle returned an incorrect WorkPage because of the different access groups. To resolve this, pyLoadMyCasesNested Step-5 and pzProcessIndividualDepAssignment Step -13 now make additional checks to verify whether the page found by findPageByHandle API is a valid WorkPage or not.
SR-D63031 · Issue 526587
Reusable assets default option populated correctly for new application
Resolved in Pega Version 8.3.2
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-D63307 · Issue 542769
Unneeded class name filter removed from GetRelevantPropertiesForDataType
Resolved in Pega Version 8.3.2
Given one class with a set of properties and another class inherited from the first class containing a relevant records set for class 2, then a new harness did not show the base class fields. Investigation showed that the fields present in the parent class and marked relevant in the case were not being fetched due to pzGetRelevantPropertiesForDataType having a class name filter along with filter by rule resolution. To resolve this, the class name filter has been removed as it is not required due to the report already filtering by rule resolution and relevant class through a join.