How the assigned to field is populated?

Erica2 · ‎06-24-2024

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.

jMarshal · ‎06-25-2024

@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).

View solution in original post

Erica2 · ‎06-24-2024

Hi @SN_Learn

I have tried many times reloading the record, but it is still showing those ACLs. The history log is showing my co-worker name, because we have been working together on this issue.

I will contact SN support for help, because they have access to our instances. Hopefully, they will able to trace the root cause.

Many thank to you and the community for the effort.

Bert_c1 · ‎06-24-2024

There can also be an 'Assignment Rule' defined. There is one OOB with name 'Assign unauth change to chg management' however that one does not set the 'assignedt_to' field, just the 'assignment_group' field.

Try using the Field watcher as mentioned above.