Dynamic Field Population from CMDB #2260
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Project Description Dynamic Field Population from CMDB is a reusable ServiceNow solution that automatically fills key fields on incidents, tasks, or change requests based on the selected Configuration Item (CI). By fetching data such as Owner, Assignment Group, Location, Department, and Business Service directly from the CMDB, this project reduces manual effort, ensures data consistency, and improves ITSM efficiency. It leverages a Business Rule that triggers on record insert or update, combined with a Script Include that handles dynamic mapping of CI fields to target fields. The solution can be extended for multiple tables, integrated with the Service Portal via GlideAjax, and configured using a JSON or mapping table for maximum flexibility. Key Benefits: Saves time for agents by auto-filling fields. Reduces errors and ensures standardized data. Reusable across multiple tables (Incident, Change, Problem). Easily configurable for different CI-to-field mappings. This project is ideal for ITSM teams, ServiceNow developers, and Hacktoberfest contributors who want a lightweight, practical automation solution.
var DynamicFieldPopulator = Class.create();
DynamicFieldPopulator.prototype = Object.extendsObject(AbstractAjaxProcessor, {
populateFields: function(currentRecord, tableName) {
// Ensure CI is selected
if (!currentRecord.cmdb_ci) return;
// Fetch CI record
var ciGR = new GlideRecord('cmdb_ci');
if (!ciGR.get(currentRecord.cmdb_ci)) return;
// Mapping: CI field -> Target record field
var mapping = {
"owned_by": "assigned_to",
"assignment_group": "assignment_group",
"location": "location",
"department": "u_department", // custom field example
"business_service": "cmdb_ci_service"
};
// Loop through mapping and populate fields if empty
for (var ciField in mapping) {
var targetField = mapping[ciField];
if (!currentRecord[targetField] || currentRecord[targetField] == '') {
currentRecord[targetField] = ciGR.getValue(ciField);
}
}
return currentRecord; // optional, for reusability
}
});
(function executeRule(current, previous /*null when async*/) {
// Call the Script Include
var populator = new DynamicFieldPopulator();
populator.populateFields(current, current.getTableName());
})(current, previous);
|
👋 Unassigning @rohi-v due to inactivity (> 60 min without comments/reviews). This PR remains open for other reviewers. |
earlduque
approved these changes
Oct 18, 2025
Contributor
|
Just FYI, next time we are hoping that you put an X in all of the check boxes, not just the first one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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:
Project Description
Dynamic Field Population from CMDB is a reusable ServiceNow solution that automatically fills key fields on incidents, tasks, or change requests based on the selected Configuration Item (CI). By fetching data such as Owner, Assignment Group, Location, Department, and Business Service directly from the CMDB, this project reduces manual effort, ensures data consistency, and improves ITSM efficiency.
It leverages a Business Rule that triggers on record insert or update, combined with a Script Include that handles dynamic mapping of CI fields to target fields. The solution can be extended for multiple tables, integrated with the Service Portal via GlideAjax, and configured using a JSON or mapping table for maximum flexibility.
Key Benefits:
Saves time for agents by auto-filling fields.
Reduces errors and ensures standardized data.
Reusable across multiple tables (Incident, Change, Problem).
Easily configurable for different CI-to-field mappings.
Pull Request Checklist
Overview
Code Quality
Repository Structure Compliance
Core ServiceNow APIs/Server-Side Components/Client-Side Components/Modern Development/Integration/Specialized Areas/Documentation
Restrictions