To manage mandatory and read-only states of fields for records not changed on a form, what should you use?

The correct choice for managing mandatory and read-only states of fields on a form based on the condition of whether records have been changed is to use Data Policies. Data Policies are specifically designed to enforce data consistency by defining rules that control the mandatory and read-only states of fields regardless of the form's state. This means that you can establish whether a field must be filled in or if it should be read-only based on the data's context, ensuring that the integrity of the records is maintained across the system.

With Data Policies, you can ensure that certain fields are enforced under specific conditions, while also considering the impact on both the client-side (user interface) and the server side (when data is submitted). This functionality is critical for maintaining compliance with business rules and data governance strategies.

On the other hand, while UI Policies also manipulate field visibility and states, they are mainly focused on the client-side and are not designed to enforce rules when records remain unchanged. Client Scripts, similarly, are used for real-time interface behavior and might not effectively manage mandatory or read-only conditions over the long term. Business Rules operate server-side and are primarily used to automate processes and enforce data governance but do not directly manage field states on forms. Hence, Data Policies stand out as