Share reports with users and groups

[sivamuruganandam-coder]

PR Description:

Use case:
Currently there's no OOB feature to share all the reports (legacy) from the particular dashboard (legacy) with the user or group at a time. Also, sharing the dashboard with the user/group does not share the corresponding reports with them automatically. In order to do that, admin or report owner should open each report and share them individually. If the dashboard has more reports i.e 20+, then it'll take a considerable amount of time to complete this task. To reduce the manual effort, we can use this custom logic/feature to share all the reports from the particular dashboard at a time.

Pre-requisite:
A database view which shows the reports shared with atleast one dashboard need to be created. ServiceNow community article link which explains how to build one..(Thanks to Adam Stout for this) https://www.servicenow.com/community/performance-analytics-blog/view-reports-on-a-dashboard-and-dashboards-using-a-report/ba-p/2271548

Components:
UI Page: It contains Jelly script (HTML), Client script and Processing script. Used to capture the user/group info and share the reports with them.
UI Action(Client): Created on the Dashboards (pa_dashboards) table. Used to open the UI page as a popup/modal window

This UI action is visible on the dashboard properties page (image attached)

Pull Request Checklist

Overview

• I have read and understood the CONTRIBUTING.md guidelines
• My pull request has a descriptive title that accurately reflects the changes
• 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

[rohi-v]

I have requested few changes for siva, meanwhile

@wiz0floyd Can you help me with checking the conflicts, I don't see the conflicts here but it's showing that this branch cannot be rebased.

[rohi-v]

Thank you for making the changes @sivamuruganandam-coder , Will review.

[rohi-v]

Looks Good and Amazing use case.

This will be very helpful

[sivamuruganandam-coder]

Looks Good and Amazing use case.

This will be very helpful

Thanks for reviewing..