- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2024 07:53 AM
Hello,
I'm trying to understand how the 'assigned to' field is populated in a Standard Change Request when the form loads and the state is 'New'.
It seems to populate based on the assignment group's manager. Could someone please explain what triggers this behavior?
Ideally, I would prefer the 'assigned to' field to start empty when the form loads. Thank you.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2024 07:46 AM
@Erica2 - I just noticed that you said this is on a STD CHG request...this could also be a part of the template - check the std_change_record_producer table and you may find it as a pre-set field. If it is, to change it, you will want to use the "modify standard change" proposal template, and remove that field from the existing template. Also, it doesn't seem like you are using change models...and this would be bad practice (IMO) and a pretty "significant deviation" from the oob Standard Change model, but it is possible that the STDCHG (preapproved) model has a field preset on it for "assigned_to" also. Go to "Change Models" (search in nav filter) and look for the Standard model (open and examine, you'll see it right there, if it is set by the model).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2024 09:09 AM
@Erica2 - this could also be due to a dictionary override on the base task table for the assigned_to field. We have one on for the change_request table on our instance:
...just right-click on the assigned_to field and then go to "configure dictionary" and then examine the overrides tab at the bottom of the task table form.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2024 10:36 AM
Hi @jMarshal
I checked the configure dictionary for the assigned to field, but not thing was configured. Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2024 02:15 PM
It's possible that the customization is on the base task table, in which case you need a blank override on the change request table to fix this. Check the box that you have highlighted in your screenshot and leave the text field blank, then save the override and see if that works!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2024 03:24 PM
Hi @jMarshal
Currently, there is no dictionary override on the task table. Only on the change table and the text filed is blank.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2024 07:27 AM - edited 06-25-2024 07:27 AM
OK, great. Save that (leave it with the checkmark - as highlighted in your second screenshot) and see if that helps!
If not, then like others have said, its probably a client script...or possibly an 'advanced script' on a UI Policy.
You can try doing a filter on the UI Policy table, like the one that was suggested by @Bert_c1 suggested for the Client Script table.