- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2016 08:22 AM
We currently have a Business Rule that will pull the user from the requested_for or who_requested variables on the catalog item and updated the Requested For field of the Request with that user. Of course, this poses issues if you open multiple catalog items for various people within one request.
We're adding a custom u_requested_for field to the sc_req_item table and would like a Business Rule that sets the u_requested_for based on who was entered in the requested_for or who_requested variables on the catalog item.
I tried altering the existing BR but had no luck. Here is the existing BR for the Request table. I just need it updated so that it works on the Requested Item (sc_req_item) table.
var grRITM = new GlideRecord('sc_req_item');
grRITM.addQuery('request', current.sys_id);
grRITM.query();
while (grRITM.next()) {
if (!JSUtil.nil(grRITM.variables.requested_for)) {
current.requested_for = grRITM.variables.requested_for;
}
if (!JSUtil.nil(grRITM.variables.who_requested)) {
current.requested_for = grRITM.variables.who_requested;
}
}
I tried changing the table to the sc_req_item table and updated the script but it didn't work. I tried a couple other versions but no luck.
var grRITM = new GlideRecord('sc_req_item');
grRITM.query();
while (grRITM.next()) {
if (!JSUtil.nil(grRITM.variables.requested_for)) {
current.u_requested_for = grRITM.variables.requested_for;
}
if (!JSUtil.nil(grRITM.variables.who_requested)) {
current.u_requested_for = grRITM.variables.who_requested;
}
}
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2016 09:04 AM
Hi Alexander,
Make the business rule you have written active false.
Write an async type business rule in the sc_req_item table.Script should be like:
updateRequestedFor();
function updateRequestedFor(){
if(current.variables.requested_for !=''){
current.u_requested_for = current.variables.requested_for ;
}
else{
current.u_requested_for = current.variables.who_requested ;
}
current.update();
}
Mark it as Helpful/Correct if it helps
Thanks,
Mihir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2016 09:53 AM
Hi Deepak,
We do not use Requests and there is no Requested For field on the Requested Item table, so we had to add that field. We only care about RITMs, not REQs.
Thanks for this info though, it may be helpful in the future.
- Alex
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2016 10:47 PM
Tell me if you get that error again...becoz i did it and it worked