Dynamic table record selector widget #2015
Merged
+198
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Description:
Added a Dynamic Table and Record Selector ServiceNow Service Portal widget.
This widget allows users to dynamically select any table and its records. It automatically determines the correct display field, supports parent table lookups, and uses sn-record-picker for flexible and accurate record selection. The widget is fully client-side and uses AngularJS along with HTTP requests to ServiceNow REST APIs.
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 (not applicable)
I've tested my code snippets in a ServiceNow environment
Repository Structure Compliance
I've placed my code snippet(s) in one of the required top-level categories:
Client-Side Components/
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
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