There are a few ways you can do this.
First, if you are going to a single altitude constraint, say an along track waypoint, destination/-30 at 10,000, then you can use the DIRECT TO button on the CDU, line select the altitude into the scratch pad, and then re-enter it for the along track waypoint. That will re-sync the VNAV and execute a vertical “direct to”. If you’re in VNAV mode, e.g., VALT or VVS, the aircraft should recapture the VNAV path and change to VPATH mode. You can do this with any altitude constraint and create a vertical “direct to”.
The second method is used of you’re descending on a STAR with multiple constraints. You can use the same method above to execute a vertical direct to the next altitude constraint. However, of that constraint is an “at or above”, then you have just changed that constraint into an “at” constraint. That will affect the downstream VNAV path angle after that constraint. You will comply with the altitude constraints on the STAR, but you may fly them at a much shallower VNAV path angle.
Basically, the Collins VNAV uses the default VNAV path angle (3.0 but can be changed) and the lowest “AT” constraint, or the lowest “AT or BELOW” constraint, and then checks that 3.0 degree path back up through the remaining higher altitude constraints. If that path meets all coded/pilot entered altitude constraints, then the 3.0 path is used. If not, then the VNAV path is “smooth” between the constraints where is doesn’t work until it can again project a 3.0 degree path back to the cruise altitude for TOD.
On a STAR with many altitude constraints, the best way to recapture the VNAV path from above when ATC interrupts the descent is to use either VVS or VFLC and descend at a rate equal to or faster than the target vertical speed shown on the vertical speed indicator (pink target bug) or as shown on the MFD Vertical Path information display. The only catch is that if the target constraint is a window altitude constraint, one that is both “at or above” and “at or below” altitudes, you need to make sure you capture VPATH before you reach that waypoint. Otherwise, you risk not meeting the “at or below” constraint. This is my preferred real world method.
Rich