SR-C42849 · Issue 395987
Validation corrected to honor Read-Only designations
Resolved in Pega Version 8.2
Validation was happening on Read-Only fields due to pyReadonlyValidation not being honored in all editable cases. This has been corrected.
SR-C54754 · Issue 395508
Work by Work Queue modified to use RD in place of deprecated list view
Resolved in Pega Version 8.2
When the "Find" button was selected in Designer Studio >> Case Management >> Tools >> MyWork >> Work by Work Queue, a series of dotted lines that exceeded the section limitation appeared. This was traced to the use of the deprecated function List-view in workbasketlistPopup. In order to support the needed display, the Pega-Landing.pzProcessAndCaseRulesMainMenu Navigation rule has been modified to call a report definition Assign-WorkBasket.pyASSIGNMENTSFORWORKBASKET instead of the deprecated list view. While there is a small difference in user experience and behavior, all the columns being fetched and filters being added will be similar to that of the ones previously seen in the list view.
SR-C55269 · Issue 395845
Custom filter values correctly pass to custom drilldown filters
Resolved in Pega Version 8.2
Reports with summarize column, drilldown, and custom inline sections were not forwarding values from the custom filter to the drilldowns custom filter. This was a missed use case in earlier work done to ensure custom filter values are populated during runtime, and has been added.
SR-C59762 · Issue 402287
Custom filter values correctly pass to custom drilldown filters
Resolved in Pega Version 8.2
Reports with summarize column, drilldown, and custom inline sections were not forwarding values from the custom filter to the drilldowns custom filter. This was a missed use case in earlier work done to ensure custom filter values are populated during runtime, and has been added.
SR-C57259 · Issue 396052
Reference Rules gadget shows results for GET >> Service Activity
Resolved in Pega Version 8.2
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-C55675 · Issue 396851
Handling added for work cases being synchronized after missing flow rule changes while offline
Resolved in Pega Version 8.2
Mobile application work items submitted offline did not always appear when online again.After coming back online, new work items that were created online were synchronized, but the work items that were created offline were not synchronized. This occurred when changes were made to the flow rule after cases had already been created offline. To resolve this, any failure in finishAssignment/ previousAssignment/ doSave actions which does PRocessAssignment will persist the incoming data from device in following way: 1. Create a Pega-Work-OfflineSync case. 2. Merge all the actions related to the failure work object and copy the merged page in pySyncErrorCase page. 3. If a work basket is configured, the newly created case is moved to the work basket else it is moved to the default work basket. To check the data please check the work basket or instances of Pega-Work-OfflineSync.
SR-C55017 · Issue 397186
Mapping corrected for Constraints rule properties
Resolved in Pega Version 8.2
The Constraints rule was not working for page list due to Page context and Page Context class both referring to the same property of pyPageContextClass. This was an error introduced during a UI Ruleform upgrade, and has been resolved by correcting the mapping of the "Page Context" field to pyPageContext.
SR-C57881 · Issue 398819
Localization support added for page level properties
Resolved in Pega Version 8.2
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 399199
Hazelcast thread locking improved
Resolved in Pega Version 8.2
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-C55724 · Issue 399508
SetTracerOptions modified to correctly pass needed parameter for displaying changes on the UI
Resolved in Pega Version 8.2
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.