Why does an auto-populated lifecycle state date field display an incorrect value in Vault?
Check if the lifecycle state has an entry action condition that sets the date when it is blank.
- Documents that go through the lifecycle once or are migrated may already have a date value populated. This prevents the current value from being added if there are Entry Criteria requiring it to be blank.
- The Approved State and Approved Date is an example where this can be used.
Vault Lifecycle State Help Documentation: Document State Entry Actions