- 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 08:15 AM
Hi Erika2,
That is not OOB behavior, at least that doesn't occur in my instance. It may be a Client script that runs 'onLoad' for the change_request table. Check those in your instance. Especially if the Assigned-to field is empty in a list view of change_request table where State = New.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2024 08:32 AM
Hi @Bert_c1
There are many of Client Script that runs 'onload' for the change_request table. I show match on the 'change_request' table and type is 'onload', but it is still a long list. Is there a easier way to find which client script is triggering this behavior? Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2024 08:37 AM
Yes, Add another condition with 'Script', 'contains', 'assigned_to'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2024 10:47 AM