Overview:
Required field not appearing as required in a placeholder.
Root Cause:
Create new documents as Planned option is enabled in Vault.
Solution:
The Create new documents as Planned option is enabled for a Vault. If the following criteria are met, the fields are not required.
- The Lifecycle associated to the selected Document Type, Subtype, and Classification has the Planned state enabled.
- All documents that are created are associated to that Lifecycle.
Vault automatically configures planned documents so that if the field is required because of the document type, it is able to be skipped. But, if the requirement for the planned document is required because of a field dependency, it is required to fill-in that field.
Related Documentation:
Vault Help Documentation: Working with Content Placeholders
Send us your feedback: We're always looking for advice to help improve our Knowledge Base! Please let us know if this article was helpful or provide feedback on how we can improve your experience here.
Thank you