There is a standard Vault Entry Action CC: Update Change Controlled Documents in the Document Change Control object Lifecycle. Adding this entry action to the Approved state in that lifecycle allows the Document Change Control object record to perform state changes and field updates to the related documents and requests upon approval
A user has this Entry Action configured on the Approved state in the Document Change Control Lifecycle, but the Planned Effective Date, Planned Obsolescence Date, and Obsolescence Approval fields are not getting populated automatically on the associated documents as expected.
These Document Change Control fields are not mapped to their corresponding document fields.
A user must map the Document Change Control fields to the corresponding document fields that are populated by the entry action by going to Admin --> Settings --> Application Settings --> QualityDocs.
Vault Multi-Document Change Control Documentation: Document Change Control Object
Send us your feedback: We are always looking for feedback to help improve our Knowledge Base! Please let us know if this article is helpful or provide feedback on how we can improve your experience by clicking here.