now have this working from an asynch, insert business rule
UPDATE 2: this doesn't really seem to work. Instead, see my post "Write to script processing table (extended from DL) to execute stored gliderecord scripts"
ideally, this would be done within workflow. But if for some reason you didn't want to modify the wf...
UPDATE 1: I since managed to figure out that the issue was being caused by using .get within the business rule instead of .query and .next. Reverting to the latter appears to have resolved the issue
hence, a business rule before insert on the sc_request table with the following code seems to do the trick:
below is a workaround solution I came up with, but would recommend against using. Illustrates principle of firing off an on-demand scheduled job which can be of interest, script actions seem to have certain limitations within the scope of an insert/update operation in that these seem to run asynch and I experienced some problems with them targetting the same record
the problem of doing this in business rules, avoiding circular updates of course, is that at the point the REQ record is being created, the RITM record appears to be held in memory and hence ritm.short_description will show as undefined
I got around it using a scheduled script execution from the business rule (after insert on REQ) with a 2 second delay:
(probably other/better ways to do this!)
Business rule - note, must be 'after insert' rule on sc_req_item not request:
Scheduled job (on demand): (avoid gs.sleep)