Skip to main content
hamburger menu Created with Sketch.
Updates were made to the Support and Services ticketing processes. Click the link below the search bar for more information.

Search the Knowledge Base

Field Dependencies Based on the Document Lifecycle Override Other Related Dependencies in Vault

  • Updated

Question:

When a field dependency is configured and based on the document lifecycle, all other related dependencies based on document type or document field are overridden. Is this working as designed?

Answer:

This is working as designed. Lifecycle field dependencies override regular field dependencies.

Example:

  • When a document field is made hidden to a user in a specific role for a document version in a specific state, no regular field dependency can make that field visible again to the user.
  • When a document field is made read-only to a user in a specific role for a document version in a specific state, no regular field dependency can make that field editable again to the user.
  • When a document field is made visible to a user in a specific role for a document version in a specific state, no regular field dependency makes that field read-only to (or hidden from) the user.

This includes fields covered by the behavior of other fields' configurations.

Related Documentation:

Vault Help Documentation: Managing Dependent Fields   

 

Powered by Zendesk