SR-D26785 · Issue 495892
Corrected error when persisting temporary work object
Resolved in Pega Version 8.2.4
When persisting a temporary work object using the Persist case shape, the internal assignment handle was not updated to include the work object's ID. Subsequent attempts to access the internal assignment (such as the "Edit" button on the Review Harness) resulted in errors. Investigation showed that when a temporary case was persisted, pyInternalAssignmentHandle was not getting recalculated after pzInsKey was updated. To resolve this, the configuration on the edit button has been modified to use .pxFlow(pzInternalCaseFlow).pxAssignmentKey which is what pyInternalAssignmentHandle declare expression was also returning.
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.
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.
INC-185847 · Issue 669526
Handling added for disabling weekends when no weekends are available
Resolved in Pega Version 8.7
A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance.
SR-D29809 · Issue 505256
Extra <p> tag removed when not needed in RTE generation
Resolved in Pega Version 8.2.4
The RTE was generating an extra <p> tag in the Review harness or when the RTE was non-editable, causing alignment issues in the UI when RTE was displayed using inline dynamic layout with a textarea. This has been corrected.
INC-177323 · Issue 672420
Search string wildcard use documentation updated
Resolved in Pega Version 8.7
The support article for the search API has been updated to clarify the ability to use the wildcard character "*" by manually adding it to the prefix of each term in the search string.
INC-173162 · Issue 650795
Certificate match will use Subject Distinguished Name
Resolved in Pega Version 8.7
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.