Skip to content

Conversation

@Rampriya-S
Copy link
Contributor

PR Description:

Pull Request Checklist

Overview

  • [ x] I have read and understood the CONTRIBUTING.md guidelines
  • [ x] My pull request has a descriptive title that accurately reflects the changes
  • [x ] I've included only files relevant to the changes described in the PR title and description
  • [x ] I've created a new branch in my forked repository for this contribution

Code Quality

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

Repository Structure Compliance

  • [x ] 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/
  • [x ] I've used appropriate sub-categories within the top-level categories
  • [x ] Each code snippet has its own folder with a descriptive name

Documentation

  • [x ] I've included a README.md file for each code snippet
  • [x ] 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

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

This Business Rule automatically prepares an email reminder for Change Requests that are about to close.
When triggered, it dynamically builds a clear and actionable subject and body message to alert users that the Change Request is nearing closure.
This Business Rule automatically prepares an email reminder for Change Requests that are about to close.
When triggered, it dynamically builds a clear and actionable subject and body message to alert users that the Change Request is nearing closure.
@snamjosh snamjosh self-assigned this Oct 7, 2025
Copy link
Contributor

@snamjosh snamjosh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @Rampriya-S for your contribution. Can you provide screenshots of business rule trigger condition ? I see that notifications are sent to user for reminder records when reminder.notify event is triggered.

This Business Rule automatically generate a reminder message for Tasks that are approaching their closure time.
@Rampriya-S
Copy link
Contributor Author

@snamjosh snamjosh merged commit 695d030 into ServiceNowDevProgram:main Oct 8, 2025
ravichandra1998g added a commit that referenced this pull request Oct 22, 2025
ravichandra1998g added a commit that referenced this pull request Oct 22, 2025
@ravichandra1998g
Copy link
Contributor

Hello @Rampriya-S
I have reverted this PR as this attached the Readme file (and the script file) under the Business Rule folder.

Please place the script in a sub folder and resubmit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants