Certain assignment groups next up is not reflecting correctly.  Modify the Past Recovery/Reg Deadlines reporting to pull based on task date oldest first.

1. Below assignment groups next up reflects in the assignment group dashboard display.
   1. Daily Critical Assignments
   2. Daily Maintenance Assignments
   3. Final Reg Deadline Assignments
   4. High Dollar Assignments
   5. Manager Assignments
   6. Next Recovery Deadline Assignments
   7. Non-Regulatory Assignments
   8. Past Recovery/Reg Deadline Assignments
   9. Provisional Credit Review Assignments
   10. Unworkable Assignments
2. Past Recovery/Reg Deadlines Assignments should pull and be displayed based on Task Date pulling oldest first.

Resolves a issue where the Next Up assignment tab was not displaying what was going to be pulled next.

Assignment groups when enabled is causing latency for non-related functions, opening a case, etc.

1. When opening a case with our without assignment groups the same amount of time is used to complete the action.

Resolves performance issues associated with assignment groups.  It is taking longer than expected to take actions.  (Open claim, etc.)

All of the reports for the Late Lifecycle Recovery Assignments Group is not sorted first by Next Recovery Date Time.

1. When viewing the late life cycle recovery assignments reports in the dashboard it is sorted first by next recovery date time, then by claim amount for the below tabs.
   1. All Tasks
   2. Next Up
2. When reviewing the assignment groups dashboards you can filter and sort them.

Resolves a issue with how later life cycle reporting is displayed on assignment group reporting.

From ticket: GFTQS-496
This is a product bug as the functionality has not been built yet Per Billy.

Technical Notes:

The fix to this is as follows (also see screenshot):

• When @QVODoesCSVContainEntry(D_AssignmentGroupHelper.TaskLabelCSVGroup(ManagerAssignments), .pxTaskLabel) 
  • When @IsInPageList("ManagerAssignments", ".Key", OperatorID.WorkAllowedAssignmentGroups)
    • Do nothing.  They have the access.
  • Otherwise
    • Set Param.HasAccess to false

1. If a user is configured to use assignment group work routing, if they do not have the Manager Assignments assignment group, then they should not be able to work manager assignments.
2. If a user is configured to use assignment group work routing, if they have the Manager Assignments assignment group, and meet other criteria, then they should be able to work the manager assignment.
3. If a user is configured to use assignment group work routing, if they do not have the Unworkable Assignments assignment group, then they should not be able to work unworkable assignments.
4. If a user is configured to use assignment group work routing, if they have the Unworkable Assignments assignment group, and meet other criteria, then they should be able to work the unworkable assignment.

Resolves a issue where security was not preventing users from working assignment groups which they did not have access too.  

Add indexes outlined in story.

1. Add below Indexes to pc_assign_completed
   1. pc_assign_wb_completed_clientidcsv_pxcreatesystemid
2.  Add below Indexes to pc_assign_created
   1. pc_assign_created_clientidcsv_pxcreatesystemid
3. Add below Indexes to pc_assign_workbasket
   1. pc_assign_workbasket_clientidcsv_pxcreatesystemid
4. Add below Indexes to pr_index_qvo_fb_claims_claim
   1. pr_index_qvo_fb_claims_claim_pxcreatedatetime

Added some indexes to improve performance on assignment groups.