Anonymous
My feedback
6 results found
-
14 votes
Hi, this is an interesting idea, however, we would be worried about the configuration complexity of adding differing version limits below the enterprise level.
An error occurred while saving the comment Anonymous
supported this idea
·
An error occurred while saving the comment Anonymous
commented
Example Workflow:
v1: Initial file upload to Box
v1.1, v1.2, etc.: Auto-saved redlines (grouped as subversions)
v2 "Box RL": Legal marks editing complete with a label
v2.1, v2.2, etc.: Next round of auto-savesThis would eliminate file renaming workarounds and provide cleaner version history for contract management.
-
65 votesAnonymous
supported this idea
·
-
11 votesAnonymous
supported this idea
·
-
15 votes
Thanks for your feedback. We’re exploring introducing new cascading triggers or system-wide workflows which would address this issue.
Anonymous
supported this idea
·
-
17 votesAnonymous
supported this idea
·
-
1 voteAnonymous
shared this idea
·
Current State: Box auto-saves frequently (every few minutes) or upon hard saves in Word. This creates numerous versions (potentially v1-v50) during a single editing session.
Pain Point: Legal teams need to distinguish between meaningful document milestones and routine auto-saves. Currently, they resort to renaming files to track major versions (e.g., "Contract_BoxRL.docx").
Proposed Solution: Enable "milestone versioning" with custom labels, while grouping auto-saves as subversions.
Example Workflow:
v1: Initial file upload to Box
v1.1, v1.2, etc.: Auto-saved redlines (grouped as subversions)
v2 "Box RL": Legal marks editing complete with a label
v2.1, v2.2, etc.: Next round of auto-saves
This would eliminate file renaming workarounds and provide cleaner version history for contract management.