SR-D84754 · Issue 548165
Resolved erroneous problem assignment error
Resolved in Pega Version 8.4.1
If a user processed a work item while the SLA agent was also attempting to process it, it sometimes resulted in an assignment with the error: "Error: Flow Not At Task." In this scenario, an error message was displayed stating that "Assignment already completed" even though the assignment was not yet finished, causing confusion. Investigation showed that in cases where the success indicator was -28, the assignment was marked as problem assignment even though it was processed. To resolve this, the system has been updated to skip marking the assignment as a problem when the success indicator is -28.
SR-D88141 · Issue 550010
TemplateButton field correctly set read-only
Resolved in Pega Version 8.4.1
When a control was added to a section using the DX API, a pyTemplateButton field was added to the XML definition of the section with read-only set to 'false'. This has been corrected so the pyTemplate Button field does not allow input.
SR-A5412 · Issue 219159
Error marking fixed for TreeNavigation7 screen flow
Resolved in Pega Version 7.3.1
When using the TreeNavigation7 harness in the screen flow to call the validation from the post action, any property error in any of the flow-actions caused only the first flowaction to be marked as having an error while the rest were marked as successful. This has been fixed.
SR-B64971 · Issue 315219
Added alt text attribute to paperclip icon for accessibility
Resolved in Pega Version 7.3.1
A paperclip icon in the pzMultiDragDropControlStandard rule did not have alternative text, impacting its accessibility. An alt="" attribute has been added to the image tag to correct this.
SR-B51367 · Issue 311023
Resolved stack overflow for three level nested WO
Resolved in Pega Version 7.3.1
A StackOverflow exception was generated when using three levels of nested work objects due to a recursive looping of the parent pzInskey looking for its children. To fix this, the pyLoadMyCasesNested activity has been updated to set the RD based on whether a parameter sent to it is blank.
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.