Send Email On Form for every Record

[Kart-19]

PR Description:

To Send Email on Form Directly by population some field and then customize the body and trigger it.

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]

Hello @Kart-19

Can you please explain How is this use case different from OOB Email client which allows user to send an email from any record
https://www.servicenow.com/docs/bundle/zurich-platform-administration/page/administer/notification/concept/c_EnableTheEmailClient.html

[Kart-19]

Hi @ravichandra1998g - Yep, you are right, we've the OOB as an email client template. The one difference that I see is the custom fields, which we can add on the UI Page HTML and then populate the value. But in the OOB, the fields are standard and generic. But as you said both will have the same functionality but the user view and the experience are different.

[ravichandra1998g]

Hello @Kart-19

In the current code snippet, all the fields you have included are already available from the OOB email client.

[Kart-19]

Yes, I've made a basic template functionality, to just keep it simple as you know, we can add based on the use case by adding the other field on the UI page. Just want to show there is a way to use this functionality rather than OOB which is customizable.

[ravichandra1998g]

Hello @Kart-19

How the custom fields added here can be sent through Email. As every email would only contain a body?

appreciate your effort in submitting this PR but just trying to understand

[Kart-19]

Sure, the Custom field which will be populated in the UI page for the User view and if they want there is a piece of code which, for example, I've implemented in the UI Page for every email-body, the INC number will be added in front in the same way we can add our custom field.

Piece of code - <textarea id="body" name="body" placeholder="Body to send email" >${jvar_num}</textarea>

Result - INC000001 and the body content.

Appreciate your interest on this.

[ravichandra1998g]

looks good to me.