Hi @ManasiC ,
As per my understanding , you’re basically doing a JDBC ETL → Robust Transformer → ETL After Script that needs to
1. Take your source u_endpoint field (comma-separated IDs/partial names of Class B CIs).
2. Resolve them to actual Class B CIs using a NameLIKE match.
3. Check if a relationship between Class A (current CI) and each Class B CI exists in cmdb_rel_ci.
4. Create it if it doesn’t.
Below is a pattern you can use in your ETL After Script for this.
I’ll also explain where to plug it in so you can handle variable-length comma-separated values without hard-coding.
Example ETL After Script - I am not much good in Scripting side but this might provide you an insight -
(function transformEntry(source, target, map, log, isUpdate) {
try {
var classA_sys_id = target.sys_id; // CI just created/updated by ETL
var endpointString = source.u_endpoint || '';
if (!endpointString) return;
// Split and trim comma-separated list
var endpoints = endpointString.split(',').map(function(ep) {
return ep.trim();
}).filter(Boolean); // remove blanks
endpoints.forEach(function(endpoint) {
// Find matching Class B CI (NameLIKE match)
var classB = new GlideRecord('cmdb_ci_class_b'); // replace with actual table name
classB.addQuery('name', 'LIKE', endpoint);
classB.query();
while (classB.next()) {
// Check if relationship already exists
var rel = new GlideRecord('cmdb_rel_ci');
rel.addQuery('parent', classA_sys_id); // Class A
rel.addQuery('child', classB.sys_id); // Class B
rel.query();
if (!rel.hasNext()) {
// Create new relationship
var newRel = new GlideRecord('cmdb_rel_ci');
newRel.initialize();
newRel.parent = classA_sys_id;
newRel.child = classB.sys_id;
newRel.type = 'Depends on::Used by'; // replace with your relationship type sys_id
newRel.insert();
log.info('Relationship created between Class A: ' + classA_sys_id +
' and Class B: ' + classB.sys_id);
} else {
log.info('Relationship already exists for: ' + endpoint);
}
}
});
} catch (ex) {
log.error('Error in After Script: ' + ex.message);
}
})(source, target, map, log, isUpdate);
Key Points for Your Case
* source → Holds the data coming from your JDBC source record.
* target → Holds the CI just created/updated in ServiceNow by ETL mapping.
* u_endpoint → Must be referenced from source because it’s not mapped to a target field.
* Dynamic handling → Uses .split(',') so you can handle 2, 3, or 50 endpoints without changes.
* LIKE Search → Replace 'cmdb_ci_class_b' with the real table for Class B CIs.
* Relationship Type → Replace 'Depends on::Used by' with the actual relationship type sys_id you want.
* Performance Note → If your endpoints list or CMDB is large, you may want to cache results in a JS object to avoid duplicate queries in one run.
Where to Put This
* In your ETL Definition → Transform Map → After Script.
* Ensure your robust transformer mapping does not map u_endpoint to any field, so you can fully control it in the script.
* Test in sub-prod with a few rows first — relationship creation is immediate and irreversible without cleanup.
Why This Works Better Than Table Lookup or Multi-IO Scripts
* No fixed array length → Works with unlimited comma-separated values.
* Direct CMDB Relationship creation → Avoids intermediate fields.
* Single pass → Reads u_endpoint once, processes all values.
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025
