SR-B58009 · Issue 312838
Updated removeAssignment call for Assign- class
Resolved in Pega Version 7.3.1
After upgrade, some cases were becoming corrupted with the error "trying to calculate the handle of an instance may not be written to Database". This was traced to an unnecessary removeAssignment call to the ProCom flow library when work objects class is of Assign- ; this is old and has references to named pages like newAssignPage which may be empty. To correct this, the call to pega_procom_flow.RemoveAssignment has been replaced with pega_processengine_flowutilities.RemoveAssignment.
SR-B64353 · Issue 313990
Resolved assignment error when competing with SLA
Resolved in Pega Version 7.3.1
An Assignment error was occurring when the SLA competed with the user for an assignment. This was an error with setting the success indicator in the EstablishContext Activity, and has been fixed.
SR-B53049 · Issue 311589
SLA agent honors custom case type time-out
Resolved in Pega Version 7.3.1
Despite an assignment having a 3-hour lock period, the SLA agent was able to advance the assignment and remove access if the goal/deadline passed in less than that lock period. This was caused by a handling error where the order of steps led to not honoring custom timeout mentioned in the case type. This has been fixed.
SR-B57619 · Issue 316602
Bulk processing actions list corrected
Resolved in Pega Version 7.3.1
Even though the filter condition contained 'Assigned to Workbasket', the action list on selected assignments contained action for work objects. This was caused by a defect in the @baseclass.pyGetRelevantActions activity which would conditionally set local.bAssignmentChosen; this setting is not necessary, and the conditional setting has been modified to be 'true'.
SR-B53374 · Issue 312278
Bulk actions RD templates can be overridden
Resolved in Pega Version 7.3.1
Even though the pyBulkProcessingTemplate RDs in the application class were overridden, the RDs in Work- were being picked at runtime. This was because in pzRunBulkProcessReport, the class of RD is hardcoded to Work- while opening the RD. To resolve this, the hardcoding has been removed and instead the workpool class will be passed as the pyClassName while opening the template RD.
SR-B56510 · Issue 312804
Bulk actions RD templates can be overridden
Resolved in Pega Version 7.3.1
Even though the pyBulkProcessingTemplate RDs in the application class were overridden, the RDs in Work- were being picked at runtime. This was because in pzRunBulkProcessReport, the class of RD is hardcoded to Work- while opening the RD. To resolve this, the hardcoding has been removed and instead the workpool class will be passed as the pyClassName while opening the template RD.
SR-B55647 · Issue 313610
Improved page reference passing for subflow with split shapes
Resolved in Pega Version 7.3.1
For named pages, the page reference was not retrieved from pages and classes while performing validation during a subflow from a split shape. This has been fixed by sending pageandclasses as a parameter to findClassOfPageReference.
SR-B46908 · Issue 306223
Corrected incomplete filter clearing in Bulk Action search
Resolved in Pega Version 7.3.1
In Bulk Actions, searching cases using a filter property assigned to Operator with a particular operator, the results were displaying correctly. However, removing the operator ID and searching with an empty value showed the results for previously searched operator ID instead of showing all results. This was traced to the pyUserIdentifer not being cleared when the value of the Assigned To Operator filter value was removed, and has been fixed.
SR-B57138 · Issue 313180
BulkUpdate search function made available for customization
Resolved in Pega Version 7.3.1
In order to support customization for activities such as the updating of display of filters in bulk update, the use of pzBulkUpdateSearchSection has been withdrawn and replaced with pyBulkUpdateSearchSection.
SR-B53230 · Issue 310973
SendEmail shape validation calls updated
Resolved in Pega Version 7.3.1
Inconsistencies were seen with using the SendEmail smart shape to send email to the configured workparty. This was traced to the way pyWorkPartyUri was populated from the CallWorkPartyRetrieve activity. This activity is referred in pyWorkParty property and called when any property on the work party is changed in the UI. However, when the work party is populated programmatically, this activity was not getting called and mandatory properties were not being set or validated. To ensure consistent behavior, pyWorkPartyUri has been included in Validate.