The overall goal is to track the creation of scripts. I would like to allow people to request functionality and if we need to build scripts to achieve the functionality I want to tie that script to the request.
If I cannot do this, I guess I will add a journal and make it mandatory and by process require a RITM # be added to the journal for each update.
I was working too long apparently because when I looked at the script this morning, I was like "why did you do that?" It all works now.
My thought is that the developer would always be adding the RITM to the BR and never the other way around. I can't think of a use case where someone would have to link the BR to the RITM at the RITM. I guess if the developer is putting it in because they know they need to do the work, but I wouldn't want them to link them until they actually do the work to ensure they didn't decide to create a new BR rather than use an existing one.
I guess if it's needed, we'll cross that bridge when we come to it.
(function executeRule(current, previous /*null when async*/) {
var gr = new GlideRecord('x_245394_scripts_0_scripts_requests');
gr.initialize();
gr.business_rule = current.sys_id;
gr.requested_item = current.u_requested_item;
gr.insert();
})(current, previous);
