Skip to content

Conversation

@TejasSNOW
Copy link

PR Description:

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

Feature Description: Enhanced Approval Widget
This update introduces an enhanced user interface and functionality to the standard Service Portal approval widget, addressing a common gap in the Out-of-the-Box (OOTB) experience.

Key Features and Improvements:
Mandatory Rejection Reason:

Added a mechanism to prompt the approver to enter a reason when rejecting an approval record directly from the portal.

Ensures better auditing and accountability for rejection decisions.

"Request More Information" Functionality:

Introduced a dedicated "More Info" button on each approval line and a corresponding modal.

Allows approvers to easily rollback the approval record, add comments detailing the required information, and send it back to the requester/fulfiller.

Modernized Interface:

Implemented custom CSS styling for a cleaner and more consistent visual presentation.
Enhanced UI Page Description
I've developed a UI page (or custom form) designed to streamline the process of granting user access.

When a user clicks a button, a form appears that collects the necessary information for the access request.

Form Elements:
Multiline Text Area: For the user to enter a detailed justification or description of the access needed.

User Picker (or Select User field): To specify the individual who requires the access.

Category Selector: A dropdown or selection field to define the type or level of access being requested.

Submission Action:
When the user submits the form, a new record is automatically created to process and track the access grant.
@TejasSNOW TejasSNOW closed this Oct 5, 2025
@ravichandra1998g ravichandra1998g self-assigned this Oct 5, 2025
@TejasSNOW
Copy link
Author

two page desing added

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.

2 participants