Skip to content

Conversation

@bkb68
Copy link
Contributor

@bkb68 bkb68 commented Oct 7, 2025

PR Description:

The use case is a MRVS with a reference variable (to the customer account table in this case). When an (active) account is selected in the first row, subsequent rows should only be able to select active accounts in the same department as the first account.

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

bkb68 added 4 commits October 7, 2025 08:13
Catalog Client Script to run onLoad of the MRVS, not the Catalog Item
Script Include to work with reference qualifier and onLoad Catalog Client Script
explain usage, reason for Catalog Client Script
explain usage and reason for Script Include
@rohi-v rohi-v self-assigned this Oct 7, 2025
@rohi-v
Copy link
Contributor

rohi-v commented Oct 7, 2025

Hi @bkb68

Thank You for your contribution.

The script include file that is required for that client script should be kept under same folder of your client script folder and seperate folder under script includes is not required.

Place all your relevant scripts related to that use case under this folder - Client-Side Components/Catalog Client Script/MRVS dependent ref qual 1st row.

Closing this for now. Once you make the changes, feel free to re-open this Pull Request or create a new one.

@rohi-v rohi-v closed this Oct 7, 2025
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