SR-C15546 · Issue 362398
'Close' button hidden when browser doesn't support it
Resolved in Pega Version 8.1
Attempting to access an external NPS survey assignment a second time generates an Access Denied / Logon Denied window; the resulting window was not closeable by using the 'close' button in Google Chrome and Firefox. This was traced to browser security restrictions imposed by Firefox and Google Chrome that disable Window.close()for URLs launched directly by hitting the URL. To avoid confusion, the DenyExternal HTML rule has been modified to avoid showing the 'close' button for browsers that do not support it in this case.
INC-180184 · Issue 665091
Assistance and diagnostics added for issue with opening imported 'when'
Resolved in Pega Version 8.7
After upgrade, attempting to open rules that were developed on lower environments and then imported resulted in unknown errors. A workaround has been added to skip and log any corrupted property that might be interfering with the rule opening: enable Skip-Corrupt-Property to put this in place. To improve diagnostics, the new logger NBA-WME-DEBUG has been added. If the error continues after using Skip-Corrupt-Property, Skip-Corrupt-Property should be disabled and NBA-WME-DEBUG should be enabled and kept active until the issue occurs again.
INC-165992 · Issue 657691
Table Filter save uses correct harness
Resolved in Pega Version 8.7
After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.
INC-173760 · Issue 658069
Table Filter save uses correct harness
Resolved in Pega Version 8.7
After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.
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-C30344 · Issue 372318
Activity pzCreatePage correctly uses parameter dataTransform
Resolved in Pega Version 8.1
When trying to use the out-of-the-box activity pzCreatePage to create a new page using Run Activity action on click of a button, the page was getting created but the data transform (pyDefault) that was passed as a parameter was not getting applied. This is because the Page-New step in that activity does not use the parameter dataTransform: due to development error, an extra parameter was added that wasn't supported. This extraneous parameter has bene removed, and the page-new method in pzCreatePage is now using the dataTransform parameter.
INC-166048 · Issue 659534
Navigation icons added for use in offline mobile
Resolved in Pega Version 8.7
When using an offline mobile app, clicking on an image / link on the home page for navigation resulted in the error “Resource missing. See client logs.” This was traced to a missed use case that resulted in some icons not being available in the package, and has been corrected by including the following: webwb/py-menu-toggle.png webwb/pzgrid_downarrow.png webwb/pymenuleftarrow.png webwb/pymenurightarrow.png webwb/pymodal_mask_img.png webwb/py-grid-sort-down.svg
INC-192159 · Issue 691022
Handling added for designtime page used in runtime
Resolved in Pega Version 8.7
After creating a survey with branch Create survey cases routed to different actors, some cases missed the assignments and were left idle with no access to progress. Survey cases (with branches) having the 'when' conditions in flow connectors experienced this intermittently in production. This was traced to the use of D_pzSurveyPage data page called from the ProcessUpdate data transform while creating the survey: this data page is for design time and should not be used at runtime as it requires design time pages like CaseTypePage which will not be available at runtime. To resolve this issue for runtime, in Step 3 of pzGetAllConnectors, pyClassName will be copied from the step page and set for pzGetConnectorsForDecision.
SR-C18868 · Issue 362502
Improved performance and error handling for assembled 'when' rules
Resolved in Pega Version 8.1
This release features a major re-working of the assembled 'when' rules to improve performance. The vast majority of rule dispatch costs come from unnecessary work. By optimizing VTable dispatch, eliminating unnecessary validation, increasing intrinsic usage, and optimizing dispatch routines, rule dispatch has been made 5-100x faster for IL-Assembled rules. In addition there is improved error handling for exceptions.
SR-C36622 · Issue 379749
Smartinfo fires correctly when URL encryption is enabled
Resolved in Pega Version 8.1
If Smartinfo was enabled, running a report definition worked as expected. If URL encryption was enabled, Smartinfo did not display. This has been corrected with an added check in pega_ui_smartinfo.js.