Version History: Difference between revisions

From ACT3ai MediaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
= Version History =
== Overview ==
== Overview ==
The '''[[Version_History|Version History]]''' feature in [[ACT3AI|ACT 3 AI]] provides a detailed record of all changes made to [[Projects|projects]], [[Scripts|scripts]], [[Scenes|scenes]], and [[Build_Video|video assemblies]].   
The '''[[Version_History|Version History]]''' feature in [[ACT3AI|ACT 3 AI]] provides a detailed record of all changes made to [[Projects|projects]], [[Scripts|scripts]], [[Scenes|scenes]], and [[Build_Video|video assemblies]].   

Revision as of 11:40, 27 August 2025

Overview

The Version History feature in ACT 3 AI provides a detailed record of all changes made to projects, scripts, scenes, and video assemblies. It tracks edits, saves, and renders over time, allowing creators and teams to review, compare, and restore earlier iterations.

Key Features

  • **Change Log:** Full timeline of edits with timestamps and contributor names.
  • **Snapshots:** Auto-saved points created during script editing, timeline adjustments, and video editing.
  • **Manual Checkpoints:** Users can mark important milestones (e.g., “Draft v1,” “Final Cut”).
  • **Comparison Tools:** Highlight differences between two versions of a script, timeline, or storyboard.
  • **Rollback & Restore:** Recover older versions without losing new ones.

Where Version History Applies

How to Access

  1. Open your Editor Workspace or Project Dashboard.
  2. Click **File → Version History**.
  3. Browse the chronological list of changes.
  4. Select one or more versions to preview.
  5. Choose to duplicate, rollback, or lock.

Collaboration Integration

  • Works with Organization Management to track changes by user.
  • Shows edits made by editors, reviewers, and admins.
  • Approved versions can be locked to prevent further changes.
  • Reviewers can comment on specific versions without altering them.

Best Practices

  • Use manual checkpoints for critical milestones.
  • Name versions clearly (e.g., “Client Feedback v2”).
  • Regularly review history to avoid unnecessary credit consumption.
  • Lock final versions for compliance and delivery.

Troubleshooting

  • **History not updating** → Ensure auto-save is enabled.
  • **Too many versions** → Archive older versions or branch projects.
  • **Rollback failed** → Re-open the Editor Workspace and reapply.
  • **Missing contributor data** → Check team roles and permissions.

Example Workflow

1. Script created via AI Wizard. 2. Revised in Script Editor. 3. Saved as **v1.0 – First Draft**. 4. Storyboards added in Storyboard Panels. 5. Final locked as **v2.0 – Approved** before sending to Render Queue.

See Also

Contact Us if you have questions about version history or restoring earlier drafts.