Smart Assign task to available member

[Soumyadeep10]

PR Description:

Use-case:
The primary goal of this UI Action is load-balancing.
It assigns tasks based on the fewest currently Active tasks assigned to a member in a group.

Example Scenario:
An assignment group has 10 members. Instead of assigning a new task to the whole group or any random member, the user/agent clicks on
"Smart Assign" to find the member with the fewest currently Active tasks in the same group and assign the task to them.

UI Action Name:
Smart Assign

Condition: !current.assignment_group.nil() && current.assigned_to.nil()

How it works:

1. The code queries the Group members table to find every single user associated with the currently selected assignment group.
   If someone removes a previous assignment group and then clicks on Smart Assign button, they are shown an error message to choose an Assignment group.
2. There is a loop on the task table. This loop uses GlideAggregate to count how many active records are assigned to a specific user.
3. It tracks the user that has the lowest count of tasks assigned to them and assigns the current task to them.

Pull Request Checklist

Overview

• Put an x inside of the square brackets to check each item.
• I have read and understood the CONTRIBUTING.md guidelines
• My pull request has a descriptive title that accurately reflects the changes and the description has been filled in above.
• I've included only files relevant to the changes described in the PR title and description
• I've created a new branch in my forked repository for this contribution

Code Quality

• My code is relevant to ServiceNow developers
• My code snippets expand meaningfully on official ServiceNow documentation (if applicable)
• I've disclosed use of ES2021 features (if applicable)
• I've tested my code snippets in a ServiceNow environment (where possible)

Repository Structure Compliance

• I've placed my code snippet(s) in one of the required top-level categories:
  • Core ServiceNow APIs/
  • Server-Side Components/
  • Client-Side Components/
  • Modern Development/
  • Integration/
  • Specialized Areas/
• I've used appropriate sub-categories within the top-level categories
• Each code snippet has its own folder with a descriptive name

Documentation

• I've included a README.md file for each code snippet
• The README.md includes:
  • Description of the code snippet functionality
  • Usage instructions or examples
  • Any prerequisites or dependencies
  • (Optional) Screenshots or diagrams if helpful

Restrictions

• My PR does not include XML exports of ServiceNow records
• My PR does not contain sensitive information (passwords, API keys, tokens)
• My PR does not include changes that fall outside the described scope

[ravichandra1998g]

Looks good, Thank you!

[Soumyadeep10]

Thanks a lot @ravichandra1998g !