SR-D9242 · Issue 483171
Security improved for DownloadFromServiceExport
Resolved in Pega Version 8.3
In order to improve security, the activity “DownloadFromServiceExport” now requires authentication and explicitly blocks attempts to traverse up directories.
SR-D10867 · Issue 483199
Security improved for DownloadFromServiceExport
Resolved in Pega Version 8.3
In order to improve security, the activity “DownloadFromServiceExport” now requires authentication and explicitly blocks attempts to traverse up directories.
SR-D13880 · Issue 483330
Support added for using WorkPage class for FieldValue evaluation
Resolved in Pega Version 8.3
The Instructions provided under the Assignment details section of an assignment shape were not evaluating the FieldValue for the work object's audit history entries unless the field value was defined only at @baseclass. This was due to WorkPage class not being considered while evaluating a FieldValue, and has been resolved by modifying the InstructionsLookup control to use work class instead of the hard coded @baseclass.
SR-D26642 · Issue 483436
Layout Refresh on Value Change works with Property Empty
Resolved in Pega Version 8.3
Layout refresh on value change was working when changed from "Yes" -> "No" or "No" -> "Yes", but was not triggering the refresh when the first change was from Empty to "Yes" or "No". To resolve this, the pre-replacement event validationType attribute on this function has been removed so an empty value will be processed.
SR-C95857 · Issue 483547
JSON parsing added for identifier data type
Resolved in Pega Version 8.3
After upgrade, Service-REST was no longer mapping data as expected when the property was of type "identifier". Handling has now been added for mapping where property type is identifier and the incoming type is any valid value for identifier.
SR-D7114 · Issue 483623
Corrected grid column header misalignment
Resolved in Pega Version 8.3
After upgrade, a grid's first column heading was misaligned when using the Microsoft Internet Explorer browser. This was traced to Quirks mode related CSS not being removed after support for Quirks mode ended, and has been corrected.
SR-D10545 · Issue 483627
Minimum width set for stage names to ensure all are properly displayed
Resolved in Pega Version 8.3
The chevron displaying stage names was not showing the complete stage name in Microsoft Internet Explorer and Google Chrome when there were more stages due to each stage not having its own width set. This has been resolved by adding a minimum width for the stages.
SR-C96680 · Issue 483763
Reject changes in approvalRuleChanges flow will clear cache and reassemble rules
Resolved in Pega Version 8.3
When a paragraph rule with "need approval" checked in the ruleset version was delegated, previewing the data in the paragraph rule via a button and making changes worked as expected. However, after the changes were made and sent to the approver to accept or reject the changes and the private copy was deleted, it was observed that rejected changes still showed in the paragraph rule and the cache was not cleared. The Rule Approval process allows checkouts to be approved or rejected: when not using rule approval process, a Checkin from the personal ruleset results in a Delete operation (from WBCheckIn & RuleCheckIn) that will remove the rule from the personal ruleset. However, with Rule Approval process setup, the rule in the personal ruleset is not deleted. Instead it is simply moved to the CheckInCandidates ruleset. The pyRuleset on the rule page changes, but the Inskey remains the same. Because there was no delete operation, there was no noteChange event and the cache was not cleared. To resolve this, the system has been updated to now enable NoteChangeInternal to invalidate rules that are part of the personal ruleset only if they have the correct setting in their prconfig.xml. This fix also forces re-assembly of rules after check-in and approve/reject so that pressing preview will ensure the correct rule gets displayed.
SR-D11289 · Issue 484053
Mobile support added for Report Definition chart slider
Resolved in Pega Version 8.3
Because the report definition ruleform chart slider was historically not supported on mobile devices, enabling the touch API in Google Chrome resulted in confusing behavior where the slider worked in mobile mode on a laptop but not on a mobile device. This was due to the chart slider being a jQuery UI slider component (ui-slider) that was built without support for mobile devices. An enhancement has now been added to utilize the jQuery UI Touch Punch library, which makes jQuery UI components mobile-friendly, by loading it at the start of pzRRChart.
SR-D5413 · Issue 484328
Enhanced returned value handling for using Expand when in collapsible dynamic layout
Resolved in Pega Version 8.3
After configuring an 'expand when' condition with the intention that the dynamic layout expands when the user doesn't enter the required field(@hasMessages(Primary)), the dynamic layout was expanded by default even though the "Expanded on load" was not enabled. This was traced to 'expand when' not getting set on refresh due to a different returned value for the condition, and has been corrected.