SR-C55724 · Issue 402954
SetTracerOptions modified to correctly pass needed parameter for displaying changes on the UI
Resolved in Pega Version 8.1.1
When opening trace from any rule form's Action > Trace option and modifying the settings, the changed settings were not reflected on the UI until the tracer window was closed and opened again. This was caused by the data page used to store Tracer Settings not getting its parameters properly and hence was getting duplicated. This has been fixed by modifying the activity SetTracerOptions to pass the missing parameter.
SR-C57025 · Issue 402913
Filter value Autocomplete uses localized text for the 'Case Type' string
Resolved in Pega Version 8.1.1
The Filter value autocomplete field of the Case Manager portal bulk action landing page was not working as expected while using the Japanese locale setting. If the locale setting was English or empty, the filter value was displayed correctly in the autocomplete. This was an issue with comparisons being hard-coded to use the literal text string 'Case Type', which was failing in localization. To fix this, a 'when' rule has been added to compare localized text against pyFilterName and use it in the appropriate rules.
SR-C57259 · Issue 402875
Reference Rules gadget shows results for GET >> Service Activity
Resolved in Pega Version 8.1.1
Even if a Rule had activities in the GET >> Service Activity portion of the rule, the References panel did not show them. This was a missed use case and has been addressed by using Start-Validate and End-Validate in Rule-Service-REST.Validate activity.
SR-C57445 · Issue 404782
Test Cases tab visible to delegated rules
Resolved in Pega Version 8.1.1
When the Revision Manager assigned rules in the CR, the TestCase tab was not available to the rules. This has been fixed by adding the test cases tab to "RevisionRuleFormLayout" and "pyRMRuleFormLayoutDE".
SR-C57545 · Issue 402942
Corrected retrieval of externally-stored PDF attachment
Resolved in Pega Version 8.1.1
After generating a PDF using the out of the box activities GenerateEForm and AttachEForm, the message "Failed to load PDF document" was displayed with a Reload button when trying to open the attachment. This was traced to an implementation error when CMIS/WebStorage/Repositories was updated that neglected to modify AttachEForm to match extra properties that were added to AttachFile. This caused issues when storing an attachment in an external storage system that was skipped in AttachEForm. To correct this, the Link-Attach file has been modified to properly to indicate where the attachment is being stored when it is stored externally.
SR-C57557 · Issue 402906
Work Object lock released correctly when modal dialogue is canceled
Resolved in Pega Version 8.1.1
The Work Object lock was not being released when the modal dialogue cancel button was clicked. This was due to the primary page not being switched to the pyWorkPage during the cancel, and has been fixed.
SR-C57881 · Issue 402879
Localization support added for page level properties
Resolved in Pega Version 8.1.1
When trying to change the out-of-the-box pyMessageLabel "This field may not be blank.", the changes were applied at the property level but were not applied at the page level. This was due to Localizations not being handled properly at page level, and the HarnessErrorList rule has been updated to correct this.
SR-C58201 · Issue 402953
Hazelcast thread locking improved
Resolved in Pega Version 8.1.1
The system was hanging after attempting Hazelcast locking. Tracing showed threads that seemed to be waiting for the system lock to become available so that they could acquire a database lock. This was caused by an implementation issue in LockUtils that did not wait to ensure that the distributed map's lock was released if it wasn't yet available. To correct this, debug logging has been added to the "LockUtils" class which will print when the lock is acquired or released along with the associated stacktrace. In addition, a wait function has been added to the Distributed Map lock to improve the timing between release and grab.
SR-C58241 · Issue 402872
Agent Access Group corruption resolved
Resolved in Pega Version 8.1.1
The Access Group used by agents was intermittently becoming corrupted. This was caused by a timing issue where sometimes the conclusion was built before the rulesets to the requestor were set up, resulting in the role being added to the RoleNotFound cache. To resolve this, the RoleNotFound cache has been removed so that every time a role lookup happens the system will check the database.
SR-C58279 · Issue 402899
Fixed retrieval of attached emails on cases with Japanese characters
Resolved in Pega Version 8.1.1
When using the "Send Email" shape on a case life cycle where the case type had Japanese characters, the mail was created and attached into the work object as expected, but an error was generated while trying to open the attached mail from the work object indicating "not found in database or insufficient privilege". This was due to the InsHandle being double-encoded, and has been resolved by avoiding encoding during assembly.