SR-129876 · Issue 198152
Modified filename verification for Pulse
Resolved in Pega Version 7.1.8
A problem was encountered when uploading files from Pulse if the filename contained special characters. A legacy verification method existed that tested the validity of the filename by creating and then deleting a test file, but that encountered errors when the file system was not writable. To avoid this issue, the validation method has been updated to check for special characters in the file and then decide the file name validation.
SR-129891 · Issue 198738
Reworked decision table cnflict check logic
Resolved in Pega Version 7.1.8
In a decision table, using expressions like property-property caused the decision table to report a non-existent logic conflict because there was another column with different data present. To void this, the system will skip the conflict check for Columns if the property type cannot be determined, eg: column type contains expressions.
SR-127452 · Issue 192406
Case match duplicate check resolved
Resolved in Pega Version 7.1.8
A case match rule to check for duplicates with adding an expression in weighted condition was giving a runtime error due to incorrect page referencing in java step of activity 'RunDuplicateCasesReport' that was attempting to obtain the property from the RD page (which was using a different structure). The page reference has been updated to correct this issue.
SR-130208 · Issue 198155
Handling added for step page call to DeleteAssignment
Resolved in Pega Version 7.1.8
After upgrade, the pxDeleteAssignment with step page Assign-Workbasket was not working as expected. The error was traced to the 'DETERMINELOCKSTRING' activity being available in Work- class while the local customization was passing the Assign- page as the steps page. Handling has been added for cases when the activity gets called on a page other than primary work page.
SR-130526 · Issue 200786
Modified 'save as' to update workgroups across nodes
Resolved in Pega Version 7.1.8
On a multi-node environment, 'Bulk Actions' was not showing all of the workbaskets after a product rule with a workbasket data instance was imported to one node and not others. This was a lookuplist cache issue caused by 'save as' not updating the workgroups, and has been resolved.
SR-130751 · Issue 198798
Clarified handling of unlocked work objects in multinode environments
Resolved in Pega Version 7.1.8
Release lock was not working correctly on a multinode environment. When trying to release the lock from same operator different requestor from different nodes, the error "Unable to unlock this work object" was generated. In a multinode environment, system pulse takes time to update the cache across the nodes, hence the option is not effective immediately. Messaging has been updated to reflect this delay. Once System pulse executes then other requestor will be able to work on this item.
SR-132538 · Issue 201237
Updated RD handling for WorkBasketAssignments
Resolved in Pega Version 7.1.8
After upgrade, if the Assign-WorkBasket pyWorkBasketAssignmentsDefinition report definition included the WHERE criteria .pxSystemFlow== 'FALSE', workbasket assignments for existing cases were not displayed in the harness. This was due to the new PXSYSTEMFLOW column in the pc_assign_workbasket DB table not properly handling this criteria, and a check has been added to resolve this.
SR-129239 · Issue 200337
Added handling for Flow not at Task error
Resolved in Pega Version 7.1.8
Flow not at task and flow removed errors were appearing sporadically. This happened when the trigger fired off the commit inside the post-processing called CorrUpdateNoWO and returned a stale copy of the Workobject, and was complicated by an assumption that was trying to iterate over "pzInternalCaseFlow". This has been addressed in the CORRUPDATENOWO activity.
SR-131217 · Issue 199744
Stopped unexpected trigger caused by attaching note with gadget
Resolved in Pega Version 7.1.8
Declarative rules were being fired every time a note was attached to a work object using the "Notes" gadget (not advanced notes link). To fix this, the pxAttachNote activity has been updated to not trigger the declarative chaining in this scenario.
SR-A100558 · Issue 271513
Oversized file null-pointer exception resolved
Resolved in Pega Version 7.3
A 413 exception was being generated by uploading files with a size greater than the Initialization/MaxFileUploadSize DSS value. The controls have been modified with a check to restrict properly restrict file size during this process.