Card #3475 · Autodesk App Store
Issues with Vault revision table automation and management
Merchants are struggling to correctly configure Vault revision tables, specifically with populating comments from lifecycle changes and ensuring new revisions create new rows rather than overwriting existing ones. There is also confusion regarding how to handle 'false start' revisions and a desire for alternative revision management methods.
Pain score
0.70/ 1.00 · weighted product of four components
Reach0.82distinct authors (log-normalized)
Recency1.00freshness decay, half-life months
Engagement0.63upvotes + comments, normalized
Monetization0.50willingness-to-pay cues in evidence
§ Evidence — 3 verified quotes
I can get the revision bump and the new revision table row, but I can’t get the comments from the state change to populate the table reliably.
When the Vault creates a new revision based on state changes, the information is added for that revision. But it gets filled in at the first row of the table instead of adding a new row.
Is there a recommended way in Vault to “cancel” a revision without marking the original released revision as obsolete?
Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.
Upgrade to Pro