INC-152442 · Issue 616668
Check added for Create Access to attachment
Resolved in Pega Version 8.4.4
After restricting access for the attachments category in a CS application, the attachment was added without category and could not be opened. This was due to the Create Attachment access not being automatically created for all categories when privileges were added, and has been resolved by adding a step to check Create Access for attachments of the respective category.
INC-153688 · Issue 616919
Class name length limitation raised to 64 characters
Resolved in Pega Version 8.4.4
In order to support field audits on very long class names, FLAudit Class has been modified to allow a class Name length of 64 characters instead of the previous limit of 56.
INC-154189 · Issue 617247
Harness used to determine read-only for button/text input
Resolved in Pega Version 8.4.4
If a button/text input was configured to always be editable in a section by using the /v1/cases/{ID}/pages/{pageID} API (say i.e PageID as Review), the button/text input was always returned as readonly. This was due to the API being hardcoded to return readonly info, and has been resolved by updating pzGetPageDetails to not force read-only and let the harness configuration decide the behavior.
INC-154826 · Issue 614818
Enhanced handling for screen/non-screen/screen flow movement
Resolved in Pega Version 8.4.4
When using a screen flow where the last screen had a link to launch a section, a cancel button in the section that was configured with a data transform and a 'Finish Assignment' intended to move back to the screen flow did not work as expected. If a browser refresh was performed and then the cancel button was clicked, the Finish Assignment / return was triggered as expected. Because this configuration navigated to a non-screen flow, the attachOnLoad function did not load the parameter needed for maintaining error messages. This has been resolved by updating the navigation to handle this use.
INC-155469 · Issue 616912
Attach Documents Control updated for busy indicator timing
Resolved in Pega Version 8.4.4
When using the standard control - Attach content - to attach documents for processing in the application, selecting multiple files for upload and then clicking on the attach button before the busy indicator started resulted in not all files being uploaded. Investigation showed that the busy indicator was not set to display as soon as the attachments were added, giving an opportunity to click "Attach" before all the documents could be successfully added to the process. As part of the resolution for this issue, the busy indicator will be displayed immediately upon file selection.
SR-A23106 · Issue 251959
Wait enhanced to maintain case status for multiple children
Resolved in Pega Version 7.2.2
A Parent case that was configured to resume when the sub-case reached a particular status using "Pending-ParentCaseResume" was not working as expected if there were multiple child cases for a single parent. This was due to the Wait shape taking the current status of the activator (first child case resolved) instead of the dependency status for which the wait shape should be looking for (subsequent child case), and has been fixed by establishing a new property on the Activator page to hold the dependency status and rely on this while checking if the activator has crossed the desired status.
SR-A43745 · Issue 249270
Copied ticket shapes properly visible on Work Management
Resolved in Pega Version 7.2.2
After correcting a problem with the XML generated by ticket shapes related to work states, attempting to use a copied shape with Tickets resulted in a problem locating new entries in the Work Management Tickets landing page. This was an issue with the ticket details being embedded in the shape pages while the rule references that were created for the tickets in pyModifiers were not updated to match, and has been resolved by adding rule references for the tickets embedded inside the shapes.
SR-A77119 · Issue 255564
Fixed attaching files to pre-existing inflight cases after upgrade
Resolved in Pega Version 7.2.2
After upgrade, loading pre-existing inflight cases and attaching a file generated the error "Trying to save an invalid page: Trying to save an invalid page: page is not valid". This was caused by a missing check for LinkPage.pyMemo in cases where LinkPage.pyCategory is not set, and has been fixed by setting pyMemo from LinkPage.pyMemo.
SR-A23504 · Issue 251757
Value corrections made to "Timeliness by resolving unit" SLA functions
Resolved in Pega Version 7.2.2
After upgrade, reports which relied on the out-of-the-box "Timeliness by resolving unit" function were failing. This was an issue with the Work-Resolve application, which was not correctly carrying values for the three SLA columns "Within Goal", "Past Goal", and "Past Deadline", which has now been fixed.
SR-A86465 · Issue 257770
Updated partial search from the Case Manager portal to return consistent results
Resolved in Pega Version 7.2.2
After upgrade, the search functionality was not working as expected. Launching the Case manager portal to search and then open a case worked, but then searching for another case and opening it resulted in the contents of the first search being displayed again. This was traced to inconsistent results when partial search was used from case manager portal,, and has been resolved by showing all the results (top 20) every time partial search is used from case manager portal, irrespective of the ranking ES provides to the search results (i.e., even if the work id is present in the top 20 or not).