Which cannot be debugged using the field watcher?

Which cannot be debugged using the field watcher?

• A. Script includes
• B. Client scripts
• C. UI policies
• D. Form scripts

Answer: (A)

Field watcher focuses on client-side behavior by tracking field values and changes in the form as you interact with it. It’s most useful for diagnosing issues with components that run in the browser—like client scripts that respond to field changes, UI policies that alter field states, and form scripts that execute on the form. Script Includes are server-side libraries that run on the server and don’t operate within the browser context, so field watcher can’t debug them. To inspect Script Includes, use server-side debugging tools or add logging and use the Script Debugger on the server.

Field watcher focuses on client-side behavior by tracking field values and changes in the form as you interact with it. It’s most useful for diagnosing issues with components that run in the browser—like client scripts that respond to field changes, UI policies that alter field states, and form scripts that execute on the form. Script Includes are server-side libraries that run on the server and don’t operate within the browser context, so field watcher can’t debug them. To inspect Script Includes, use server-side debugging tools or add logging and use the Script Debugger on the server.