Assignment Group is not getting changed as per Record Producer

Chaisai
Kilo Expert

For a Scoped Application and Table in it i have created a Record producer and once the task gets created from the Record Producer it will be assigned to some group for this i have used in the script section of record producer

current.assignment_group = gs.getProperty('assignmentGroup.Example');

while this worked perfectly and as required in the DEV instance , when i moved entire record producer and export and imported Group to the UAT , for some reason it is not getting assigned as per the property and getting assigned to different group. I have checked the sys id s of groups in both instance and what not but could not figure out what is happening. Any help in this is much appreciated! Thanks.

1 ACCEPTED SOLUTION

Chaisai
Kilo Expert

Hi Everyone,

 

Thanks for your precious time and replies.

 

In my case there was both a business rule and workflow running on the Custome Table and changing the assignment group. Obviously i could not put set workflow to false to use. So i have tried with a before business rule and after tweaking a little bit with the order of the business rule i have achieved the functionality and this whole issue was because of the configuration differences between UAT and development instances.

 

View solution in original post

5 REPLIES 5

Pradeep Sharma
ServiceNow Employee
ServiceNow Employee

Hi Chaisai,

 

Could you check if there are any Assignment Rules or a Business rule on the Target table that is overriding the assignment group value?. If the Table is audited, you can also view the record history to check if the value is getting overridden or not.

https://docs.servicenow.com/bundle/london-platform-administration/page/administer/security/reference/r_HistoryList.html

 

Thanks,

Pradeep Sharma

 

ccajohnson
Kilo Sage

Was the system property moved to UAT? You may want to validate that it is there and has the correct information in it. Not sure what is in your property (sys_id value, or Name), but this may not be matching due to similar named groups if it is not a sys_id value.

ChanakyaMekala
Kilo Guru

I had same issue with Change Record producer, after some R&D I found that a business rule is setting it so based on some set of conditions. 

 

Assignment will work in this order(While inserting a record):

After Business Rule assignment (overrides) --->Before Business rule assignment (overrides)---> Record Producer assignment (overrides)---->Providing Assignment Group while creation (overrides)----> Default value (overrides)--->Assignment Rule

 

So superior is the Business Rule in assignment, so please check in this order you may get something, else please reply here so that we can check other possibilities.

 

 

Please mark Correct or helpful if it is so

Hello Chani,

 

i so wanted to use the after business rule but it comes with a current.update i believe for it to work. Please let me know if you may have used it differently with current.update.

 

Thank you!