You're still using a field called change_request on the change_request table. Did you not just say that field does not exist?
OK, let me know if I misunderstand something...
- At some point, you want to create a change request by triggering a business rule. What that trigger is yet, I don't know.
- When the change request is built, you want to related it to the problem request that generated it so it shows up on a related list of changes at the bottom of the form.
- Do you also want to save the newly created change request's sys_id in the problem's RFC field?
Such a business would look something like this. Keep in mind this is untested code.
Name: Create Change
When: Before
Advanced: true
Update: true
Insert: true
Condition: (you specify this)
Script:
(function executeRule(current, previous /*null when async*/) {
var chg = new GlideRecord('change_request');
chg.newRecord();
chg.u_problem = current.sys_id; // change u_problem to your field on the change request that points to the problem or task table
chg.short_description = 'Generated from problem ' + current.number;
current.rfc = chg.insert();
})(current, previous);
Depending on what field you use for u_problem, you'll need to add the proper related list to the problem form. For example, if you use a field that references problem, use Problem -> Change. If you use Task, you'll need Problem -> Task. The key here is that the field and what it references needs to coordinate with the related list you choose. It's as big of a difference as having a related list of incidents or users or CIs.
