SR-C39879 · Issue 384006
Automations work using property with JSON string
Resolved in Pega Version 8.1
When using JSON to send complex data structures to an automation via a property, a special character ( ' ) used in the JSON string caused an error when trying to execute the automation from a flow action: "Uncaught SyntaxError: Unexpected end of JSON input". Analysis showed that if any relevant record had a single quote, the generated HTML of java tried to break the html data-automation-propData attribute, resulting in an exception. To fix this, the code has been updated to replace the single quote with ASCII HTML entity which will make the data-automation-propData attribute friendly.
SR-C3988 · Issue 358537
Launched portal remains open when navigating back to originating portal
Resolved in Pega Version 8.1
After logging into the 'Developer Portal' and then using the 'Launch' menu option to open the 'Manager' portal in a new tab, navigating to 'Manager' and changing the access role correctly caused the current tab to show the respective portal. However, after navigating back to the developer portal shown in first tab, the manager portal then closed and the developer portal was refreshed. This was a missed use case in the handling, and changes have been made in ApplicationSetup and RedirectAndRun activities to correct the issue.
SR-C39998 · Issue 387496
Fixed incorrect report background color with Microsoft Internet Explorer 11
Resolved in Pega Version 8.1
The background color of a report was gray instead of white when scrolled horizontally while using Microsoft Internet Explorer 11. This is a known issue with Microsoft Internet Explorer 11 when a flex layout is used inside a table: the harness width in flexresize is checking for 3000 width, and when it is more than 3000 there is a resize issue. If work area-based screen layouts are used instead of containers this issue is not seen. In order to handle the Microsoft Internet Explorer 11 issue, a flag has been added to disable the flexresize with Microsoft Internet Explorer 11.
SR-C40003 · Issue 391481
Custom filter section submit button fixed
Resolved in Pega Version 8.1
The Submit button in a Custom Filter section was not showing correctly in out-of-the-box report browsers. To resolve this, the pzRRDisplayCustomFilterSection harness has been updated with a new button control.
SR-C40010 · Issue 382499
Corrected URL formation problem when using Tomcat
Resolved in Pega Version 8.1
A blank screen was seen when trying to open Decision Table headers, and the color picker pop-up was blank when trying to choose a color for the skin. This was traced to an incorrect URL formed when using Tomcat, caused by the prweb/hash being appended twice in the URL. The root cause was unnecessary decoding of extURL in 'pzDisplayModalDialog' , and this has been fixed by adding the proper urlCrossScriptingFilter.
SR-C40033 · Issue 379079
Import of revision package fixed
Resolved in Pega Version 8.1
The importing of a Revision package was not working as expected, and the site was not able to import new revisions in revision management. This was an issue with incorrect property initialization causing a failure in the update of the access group when doing a rollback of the revision, and has been corrected by removing the Property Initialization in Activity pyRollOutToAllAGs.
SR-C40198 · Issue 384917
Non-English characters allowed in MQ message
Resolved in Pega Version 8.1
Connect-MQ was not allowing Russian characters for a message to the IBM MQ because non-English characters were not supported. To allow this use, the code has been updated to set headers first and then fall back to readChars method if an exception occurs.
SR-C40499 · Issue 378119
REST mobile sync updated with exception handling and more flexible page parameter
Resolved in Pega Version 8.1
Invoking REST service to do a mobile sync was failing with null pointer. Investigation showed this was caused by missing exception handling for scenarios where a hardcoded reference to pyworkpage in the function "pzHasOnlyClientPostProcessing" failed during sync. This has been corrected by modifying “pzHasOnlyClientPostProcessing” to add the needed handling as well as read the target page name from the parameter page and run the activity on it instead of using a hardcoded “pyWorkPage”.
SR-C40522 · Issue 378880
Null checks added to avoid spam with bad headers creating multiple duplicate cases
Resolved in Pega Version 8.1
Sporadically a spam email ended up creating hundreds of duplicate cases until it was removed from the inbox. This occurred when Auto Response was configured on the CITEmail listener and a case was created from the email: as the Listener failed to send out an auto response email due to the bad headers of the email, the message was not removed or marked as seen on mailbox and the Listener ended up processing it over and over. This has been resolved by adding null checks in handleStandardRequest method and sendResponseMessage method.
SR-C40574 · Issue 383240
ValidateMaxAge parameter added for MFA OTP expiry
Resolved in Pega Version 8.1
When trying to use the MFA feature via services, the max age was not honored. The Maximum age of a one-time password (OTP) token in seconds was given as '15' under security polices, but the system was allowing login to proceed without showing an expiry error when the OTP was input after the defined expiry time. To address this, the parameter ValidateMaxAge (Boolean) has been exposed as a parameter for sending OTP service to determine whether the token is short lived or long lived.