- 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 12:55 PM
Hi Erica,
Open a change request record, point to the 'Assigned to' label and right-click. See:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2024 01:54 PM
Hi @Bert_c1
That was the exactly the steps I did, but the "watch" did not display. There must be a way of enable the debug.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2024 07:03 PM
Hi @Erica2 ,
There are few things you need to check which is also mentioned in the doc which I provided earlier.
- The field watcher works only on form fields. It cannot be used on list fields. Also, field watcher is not available on password-protected fields or encrypted fields.
- Field watcher is only available within the UI frame. The option to watch a field does not appear in the context menu if you open a record outside of the UI frame, for example, in a new tab.
- Field watcher is not supported with Next Experience in Utah. You need to navigate back to UI 16.
Hopefully, these will help.
Mark this as Helpful / Accept the Solution if this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2024 09:09 PM
Thank you for continuing to help @SN_Learn
I successfully activated the watcher by accessing the system property glide.ui.polaris.experience and setting its value to false.
After making these adjustments to the form and reloading it, however, I couldn't observe any triggers. Except ACL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2024 10:19 PM - edited 06-24-2024 10:21 PM
Hi @Erica2 ,
Could you please open the record again and check that only those ACLs are showing?
Also, In the history of that change ticket, could you please check who updated it last time? Is it by 'system' or any user?
You can also check Assignment Rules[sysrule_assignment] if any rule is defined for change_request table.
Mark this as Helpful / Accept the Solution if this helps.