Skip to main content
hamburger menu Created with Sketch.
Veeva Support APAC Holiday May 1st - May 5th - Limited staff, please plan accordingly

Search the Knowledge Base

Unable to Complete Milestone via Automated Milestone State Changes After Populate the Actual Finish Date of Milestones in Clinical Vault

  • Updated

Overview:

Vault can attempt to automatically move a Milestone to a new state after certain fields are updated, without the user having to perform additional lifecycle actions. The following automation are available:

  • Move the Milestone to the Complete state when the Actual Finish Date is populated
  • Move the Milestone to the Planned state when the Planned Finish Date is populated
  • Move the Milestone to the Planned state when the Planned Start Date is populated and a value exists on the Expected Duration (Days) field
  • Move the Milestone to the Started state when the Actual Start Date is populated

In this case, the milestone is not changed to the Complete state even after the Actual Finish Date is populated

Root Cause:

If a state (State A) is set to the complete state type, then Vault tries to move the milestone to State A when entering an actual finish date, and if it fails entry criteria, Vault alerts the user at that time and prevents saving the date. In this case, the state for the complete state type is empty. 

image_-_2022-08-09T134433.572.png

Solution:

Admin can follow the steps below to resolve this issue:

  1. Go to Admin --> Configuration --> Object Lifecycles --> Milestone Lifecycle 
  2. Click Complete State
  3. Provide a desired state for the Complete State

Related Documentation:

N/A  

Powered by Zendesk