Issue
When UI policies are not working as expected, there can be a number of causes for this behavior. This article covers the most common factors that contribute to this issue. It is important to remember that UI policies are client-side rather than server-side. For this reason, other client side components can affect UI policies.
Cause
Symptoms may include the following:
- Field removed from form
- Cannot change field
- Form is broken
- UI policy not working
- UI action not working
- Client scripts not working
- Form sections not loading
- Fields not visible
- Mandatory field not working
Resolution
Determine whether any of the troubleshooting steps below are true for your environment.
Each step provides a link to an article that can help you eliminate possible common causes and take corrective action as necessary:
- Determine if your UI policy is disabled or another UI policy is taking precedence. For more information, see KB0547064: Determining if your UI policy is disabled.
- Determine if your client script is disabled or interfering. For more information, see KB0547067: Determining if your client script is disabled.
- Determine if you have any script errors, including client-side Java script errors. For more information, see KB0547069: Determine if there are client-side script errors.
- Determine if there is an issue with your browser version. For more information, see KB0547068: Determine if there is a browser version issue.
- Determine if there is a bad or missing element on the form. For more information, see KB0547070: Determine if there is a bad or missing element on a form.
Related Links
Another configuration that would be useful to check, if your instance is Domain Separated, check the domain of the record and of the UI Policy. "By default, process administration always uses the record's domain to determine what policies to apply." - Domain Separation > Process administration
