Iamshankha/Adaptive Scheduler – Automated Report Scheduling with Business Day Awareness

[iamshankha]

PR Description:

🗓️ Adaptive Scheduler – Automated Report Scheduling with Business Day Awareness

📘 Overview

The Smart Quarterly Scheduler automates report execution for quarterly business reviews. It ensures that scheduled reports never fall on weekends or Fridays, maintaining consistent and reliable delivery.

🧩 Problem Statement

The business requires a quarterly report to run on the 2nd day of specific months (February, May, August, and November). However, when the 2nd day falls on a Friday or weekend, the client team will be typically on leave and may miss reviewing urgent reports.
This results in communication delays and missed insights during critical business periods.

💡 Solution

This script dynamically checks whether the 2nd day of the quarterly month is a Friday or weekend:

If yes → the report automatically runs on the 5th day.

If no → the report runs as usual on the 2nd day through another Scheduled Report.

It uses GlideDateTime logic to determine execution dynamically within the Scheduled Report Condition.

🚀 Benefits

⏰ Minimizes manual scheduling effort

✅ Ensures reports always run on valid business days

📊 Maintains consistent quarterly performance insights

🔁 Completely automated logic without admin dependency

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]

Please add a descriptive Title and PR Description for the Pull Request

[iamshankha]

Please add a descriptive Title and PR Description for the Pull Request

Thank you for your inputs. I have made the required changes. Requesting you to review the same.

[ravichandra1998g]

Hello @iamshankha

Thank you for submitting!

I will mark this PR as a Hactoberfest accepted and approve it so that it counts towards your Hactoberfest contribution.

But we cannot merge this aa we have a similar code snippets under GlideDateTime folder under Core ServiceNow APIs and we also have similar code existing under Schedule Job Folder already.

• For Hactoberfest, we are aiming for high quality contributions which will be beneficial for the open source community. Please make unique contributions for your upcoming PRs.