How do you enforce required fields during contract creation?

• A. By disabling the save button via UI flags only after testing.
• B. By using validation rules or field properties to mark fields as required before saving or submitting.
• C. By setting all fields to optional.
• D. By relying on external checks after submission.

Answer: (B)

Enforcing required fields during contract creation comes from making those fields mandatory in the data model and validating them before the contract is saved or submitted. Validation rules or field properties that mark fields as required ensure the system blocks saving or submitting when any of those fields are empty, giving immediate feedback to the user and keeping data complete and consistent. Relying on UI flags alone can be bypassed or overridden, and checking after submission means incomplete contracts could slip through and cause issues later. Making all fields optional defeats the requirement, and external checks after submission don’t prevent incomplete data from entering the system in the first place. In DocuSign CLM, configuring required fields via field properties and validation rules achieves robust, creation-time enforcement.