SR-118259 · Issue 173287
LookupList opened to unauthenticated requests
Resolved in Pega Version 7.1.7
When a list lookup was called from an unauthenticated service, it failed due to the lack of required authentication. The activity RULE-CIRCUMSTANCE-DEFINITION LOOKUPLIST has been modified to allow its execution by an unauthenticated requestor.
SR-118884 · Issue 172536
Create Work correctly encodes Japanese characters
Resolved in Pega Version 7.1.7
When Japanese characters are passed as parameter to Create Work action, the newly created work item was registering cryptic characters instead of the expected Japanese characters. This was traced to a deprecated API, and has been corrected.
INC-142660 · Issue 595390
Pega API system management launches correctly from Help
Resolved in Pega Version 8.5.2
The Pega System Management API did not work when launched from help window, although other APIs such as Case Management were working fine. This has been resolved by updating the basePath in pzSystemManagementDocumentation.
INC-139156 · Issue 592148
Pasting image lands in correct location
Resolved in Pega Version 8.5.2
When pasting an image in a user story or issue, the image did not land where the cursor was placed in the contents of the issue or story. This was traced to the insert element handling for rich-text editor, and has been resolved.
SR-120561 · Issue 176643
RedirectAndRun' enhanced to better handle thread passivation
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
Activity 'RedirectAndRun' is used to run processing on an existing thread page. If the target thread is passivated, it could not be found in the requestor's list of threads and a new thread was created which did not have the original thread context. The handling has been updated to load the existing passivated thread from the database so context is not lost.
INC-141099 · Issue 598131
Updated Cosmos confirm notification visibility conditions
Resolved in Pega Version 8.5.2
After routing an assignment to different operator, the current operator was still seeing the Go button in Cosmos for processing the assignment. Clicking on the button resulted in an error. To resolve this, the confirm notification section reload has been moved to a different context, and the visibility conditions have been updated to handle more use cases.
SR-116936 · Issue 167898
Discarded threads set to properly clear on refresh or tab close
Resolved in Pega Version 7.1.7
When the browser was refreshed or an inactive recent tab was closed on the client side, the discarded threads were not getting properly cleared at the server end. To remedy this, the JavaScript has been updated to cleanly remove the threads.
INC-135523 · Issue 590435
Tab panel read meaningfully by screen readers
Resolved in Pega Version 8.5.2
When the tabPanel received focus with accessibility, the entire tab content was read instead of the W3 standard of only reading "Edit ". This has been resolved by ensuring the Tabpanel has the proper aria-labelledby.
INC-135720 · Issue 594791
Case link shows in Social messages for the old cases
Resolved in Pega Version 8.5.2
After upgrade from v7, the case link was not visible for the cases that were created in the old platform version. In Pega 7.1.7, metadata was stored in .pyPrivacyContextor while the later versions are using .pxContextType for Case type to show the related data. To resolve this, new properties have been implemented to hold the Case ID link
INC-158519 · Issue 625080
Filter considers all instances pages during deployment
Resolved in Pega Version 8.5.3
During package deployment, attempting to use Filter to skip some of the instances only displayed the result of the current active page instead of all pages. This was an unintended consequence of previous work, and has been resolved by adding the logic to strip quotes in the value and adding the "Pagination activity manages filtering" checkbox by default.