Updating Request [REQ] record inside an after insert business rule defined on 'sc_req_item' table [RITM] is not working as expected - Support and Troubleshooting

Updating Request [REQ] record inside an after insert business rule defined on 'sc_req_item' table [RITM] is not working as expected Issue When updating a field on 'sc_request' record inside an after insert business rule defined on 'sc_req_item' table, it is not working as expected.

Sample code:

//Query REQ record of the current RITM var grReq = new GlideRecord('sc_request'); grReq.addQuery('sys_id', current.request); grReq.query();

while(grReq.next()){ //Set the Assignment Group of REQ record to some value grReq.assignment_group = "sys_id_of_some_group"; grReq.update(); } Expected behavior is 'Assignment Group' of REQ record should be updated, but it remains empty.

Cause When a catalog item is requested, in the backend first RITM record gets committed into the database before REQ record. So, when you try to fetch REQ record using "GlideRecord" inside an after insert business rules defined on 'sc_req_item' table, it will not work as the REQ record is NOT YET COMMITTED to the database. GlideRecord tries to fetch it from the database.

Resolution There is an alternative way you can access the request record inside the sc_req_item business rule, by using "current.request.getRefRecord()" which is pointing to the request object that is available in the memory unlike "GlideRecord" which fetches from the database.

Sample Code:

var REQ = current.request.getRefRecord(); REQ.setValue('assignment_group', 'sys_id_of_some_group');

Related Links To learn more about Request Management Architecture, refer this documentation