SR-B47342 · Issue 303997
Fixed page reference error when copying
Resolved in Pega Version 7.3
An error stating reference pyWorkPage.ProductLines were not valid was generated during deferredSave while copying embedded reference type auto populate properties. This was caused by operations that added references from the data page before the current auto populate's reference information was added to duplicator. To resolve this, if the copy target is auto populate the system will skip adding references, and if the target is any other page the references will be copied.
INC-175630 · Issue 653864
Application selections only announced when visible
Resolved in Pega Version 8.6.1
The elements of the application switcher were being announced by the NVDA screen reader even when toggled off, i.e. not visible. The issue was occurring because the focus was remaining at the search bar even after closing the app switcher window, and has been resolved by adding the necessary logic to switch the focus.
SR-D53176 · Issue 541793
Error when adding function filter will persist
Resolved in Pega Version 8.1.8
When an exception occurred while adding a filter in the report viewer, the error was shown but cleared due to an immediate refresh of the parent section. Analysis found that step2 of pzGetFiltersFromContent was failing, after which the error was shown, the section reload happened, and the error disappeared. To resolve the error being cleared prematurely, the pzOnLoadReloadReport control has been modified so that when there are messages on the top level page (pyReportContentPage), a parameter will be set on HarnessContextMgr to not to clear them during the next refresh call.
SR-D60447 · Issue 522751
Corrected unexpected save warning when switching tabs
Resolved in Pega Version 8.1.8
When using the Interaction Portal, entering case data on one open tab and then switching to another open tab caused the system to display a Save warning message as though the Tab has been closed instead of switched. This has been resolved by updating the system to skip the dirty alert when bPrompt is false in the Ajax Container container case.
SR-B4768 · Issue 276160
Global DB Trace timestamp uses UTC
Resolved in Pega Version 7.3
When running Global DB trace, recorded timestamps were not following the 'set timestamp' setting. Timestamps instead corresponded to the requestor context. DB Tracer logging has been updated to ensure appended timestamps are passed as "UTC".
INC-166048 · Issue 641956
Navigation icons added for use in offline mobile
Resolved in Pega Version 8.6.1
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
SR-D76134 · Issue 542160
"Offline" icon shows when simulating offline mode
Resolved in Pega Version 8.1.8
When simulating offline mode by selecting "Settings->SystemInfo->Simulate Offline checkbox" and moving to MyWork, "Offline" did not appear in the header. This has been corrected.
SR-B31631 · Issue 289775
Installation documentation updated re: postgis use
Resolved in Pega Version 7.3
To avoid confusion, the documentation for the installation process has been explicitly updated to indicate that data and rules schema cannot have postgis extension applied.
SR-B34135 · Issue 291962
Existing Org Names used in new layer
Resolved in Pega Version 7.3
In the Advanced configuration section, existing Organization Names were not being used while creating a new framework on top of an existing framework/application. This was an issue with the framework ruleset prerequisite preparation logic incorrectly setting the ruleset version for the dependency of the framework integration ruleset, and has been fixed.
INC-173162 · Issue 650793
Certificate match will use Subject Distinguished Name
Resolved in Pega Version 8.6.1
Signature verification was failing due to the system not finding the matching root certificate for the chain. The root certificate was in the trust store, but the system found a different certificate first and that other certificate (an intermediate certificate) was not considered a valid certificate for validating the whole certificate chain. This was traced to filtering on the Issuer Distinguished Name (DN) instead of the Subject DN and was due to intermediate certificates potentially having the same Issuer as a root certificate (e.g. if that root certificate was used to create the intermediate certificate). To resolve this, an update has been made to check the Subject DN instead of Issuer DN.