Once a work order or direct action is submitted/recorded, it cannot be deleted unless it is the most recent recorded action. In some cases, the best way to change the details of a submitted work order or recorded action may be to delete the action, and re-enter the information.
Deleting a recorded action on a lot can be done if:
- the action is the most recent action on the involved lots and vessels
- the action does not have any dependent actions recorded after it
This article covers:
To delete an action:
- Navigate to the Action Details page. (hint: Click on at the far right of the action summary in the History tab of the Lot Details page, or in the Winery Activity Feed. Also, from the Work Order details page, click on View action at the top of each task.)
- Click "Delete Action" in the upper right corner.
- A pop-up window will appear to verify the deletion.
If there are any dependent actions, you might get an error message like this one:
You will continue to get this error message until all dependent actions have been removed.
To view dependent actions:
Go to the Action Details page and click on "View dependent actions list".
That will open this page in InnoVint 👇
The list of dependent actions displays all actions that will prevent you from deleting the action that needs editing. In the example above, the Barrel Down and Blend actions in the dependent actions list will prevent the Top Off action from being deleted. The Barrel Down and Blend actions will need to be deleted before the Top Off action can be edited or deleted. Then the Barrel Down and Blend actions will need to be re-recorded as well.
Q. What is a dependent action?
A. Dependent actions refer to all movement actions recorded on the lot and/or any involved vessels. Movement actions are any action in InnoVint that have the potential to change volume or vessels. Non-movement actions include Additions, Analysis, and Custom Actions.
Q. What does the dependent actions list show actions for unrelated lots?
A. Dependent actions include any movement actions recorded on involved vessels. For example, imagine this sequence of events:
- Lot A was transferred from Tank 1 to Tank 22
- Lot X was racked into Tank 1
- Lot X was barreled down
In this scenario, the Rack action and the Barrel Down action would be dependent actions if you tried to delete or edit the Transfer action on Lot A, because Tank 1 has since been involved in other movement actions.