SR-D22468 · Issue 502036
Bix extract performance improved by only checking cipher type for encrypted properties
Resolved in Pega Version 8.2.3
Previously, if no cipher was configured in extract Rules the cipher type defaulted to null and wasn't cached. This caused performance issues when running against the database. In order to improve performance, the code has been modified to only check for cipher type if the property is encrypted.
SR-D28538 · Issue 502057
Corrected requestor status flag for direct map
Resolved in Pega Version 8.2.3
Numerous "Unable to create requestor" alerts were logged. This was traced to an error in HttpAPI where after retrieving the requestor from the internal requestor map directly, the requestor creation status flag was not set properly. This caused last action to post that alert instead of the correct notice of "existing requestor retrieved". This has been resolved so the flag reflects the correct status.
SR-D33052 · Issue 502062
Blank space removed in email reply
Resolved in Pega Version 8.2.3
An issue with blank space being added between the CSR icon and the email content for the first customer mail has been resolved by setting the window width to 100%.
SR-D25711 · Issue 502135
Updated dependent role validation during rule deletion
Resolved in Pega Version 8.2.3
After checking out and attempting to private-edit the "PegaRULES:WorkMgr4" AR, the rule was still shown as checked out after the edit was discarded. This was a missed use case, as Private checkouts are generally not enabled for most of the customer rulesets. To resolve this, roles in private checkout and branch rulesets will be excluded from going through dependent role validation during rule deletion.
SR-D31066 · Issue 502253
Improved performance for "Show-HTML" in a grid with numerous controls
Resolved in Pega Version 8.2.3
‘Show-HTML’ was taking an excessive amount of time to render a UI for grid with a large number of controls. This was traced to the handling for generating and clearing markup creating an exponential growth situation, and has been resolved by modifying the system to remove redundant copies of a string in the markup string buffer.
SR-D33096 · Issue 502741
pzGetURLHashes returns proper content-type
Resolved in Pega Version 8.2.3
When using an environment set with X-Content-Type-Options:nosniff, the response from pzGetURLHashes was returned with text/html response type and the mashup would not load due to browser exception "MIME Type ('text/html')is not excutable, and strict MIME type checking is enabled." In order to support CORB mitigation in the browser, the javascript content type will be set in the response header for pzGetURLHashes call.
SR-D47018 · Issue 517032
Corrected parameter being encrypted during change portal configuration
Resolved in Pega Version 8.2.5
After configuring a changePortalLayout control using .pyDescription as property, trying to switch the portal was throwing a error page. The same configuration worked in earlier platform versions. This was traced to recent updates where the activity parameter ended up being encrypted along with the activity name, and has been resolved by removing the parameter from encryption input and adding it to encryption output.
SR-D5904 · Issue 511600
Discard changes dialog now showing for local actions
Resolved in Pega Version 8.2.5
After having modified case data without saving and clicking on a menu entry (left menu, search, ...), the system shows a dialog box to ask the user to confirm it is ok to discard changes. However, this confirmation dialog did not work with local actions, leading users to lose their work without any warning nor any way to step back. This was traced to a difference in the dirty form check, which was not present when launching a local action from a case. An enhancement has now been added to the handleMenuAction js function in pypega_ui_harnessactions.js which will perform a dirty form check with a prompt.
SR-D24527 · Issue 504402
Improved requestor cleanup
Resolved in Pega Version 8.2.5
Batch- and Browser-type Requestors were building up over time in both the Admin Studio and in the PegaRULES log and not removed until the system was restarted. This has been resolved by adding two extra cleanupRequestor calls to the Email Listener implementation.
SR-D29034 · Issue 500681
Added support for JSON mapping of deep nested pagelist objects
Resolved in Pega Version 8.2.5
An exception occurred when using a JSON data transform in the service activity to map the clipboard data to JSON on the third level of a structure formed as Pagelist-->page-->pagelist. To resolve this, support has been added for nested pagelist mapping with deep nesting of objects (configured for one sided actions) and arrays.