JSON Mapping for Incident Creation

[durgeshservicenow-hub]

PR Description:

JSON Mapping for Incident Creation

When we got the JSON payload (Object/Array of Object) for Incident creation with dynamic fields. You need a reusable script to create an Incident without hardcoding fields.

##Example

`// Usage with a single object
var singlePayload = '{"short_description":"System Down","caller_id":"durgesh1@example.com","priority":1,"assignment_group":"IT Support"}';
createIncidentsFromJSON(singlePayload);

// Usage with an array of objects
var arrayPayload = '[{"short_description":"System Down","caller_id":"durgesh2@example.com","priority":1,"assignment_group":"IT Support"}, {"short_description":"Email Issue","caller_id":"durgesh3@example.com","priority":2,"assignment_group":"IT Support"}]';
createIncidentsFromJSON(arrayPayload);'

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

[ravichandra1998g]

looks good!