Undo & Redo
Applies to: Pro · Enterprise Last updated: 27-Feb-2026
Overview
Every editing action in Kazinex is recorded as a command that can be undone and redone. The system maintains a history stack of up to 200 commands and tracks all changes for a dirty-state indicator. Batch operations (like creating multiple relationships at once) undo as a single action.
Prerequisites
- Active Pro or Enterprise subscription
- Editor Mode enabled
Basic Usage
| Action | Shortcut | Toolbar |
|---|---|---|
| Undo | Ctrl+Z | Undo button (shows description of last action) |
| Redo | Ctrl+Y | Redo button (shows description of next action) |
Performing a new edit after undoing clears the redo stack — you cannot redo previous actions once new edits are made.
Command System
Every edit generates a command object with:
| Property | Description |
|---|---|
| ID | Unique identifier |
| Description | Human-readable action label (shown in undo/redo buttons) |
| Category | field-update, add, delete, move, duplicate, bulk-update, or project-settings |
| Entity Type | What was modified |
| Timestamp | When the command was executed |
Supported Entity Types
| Entity | Example Operations |
|---|---|
| Activity | Update field, add, delete, dissolve, move, duplicate |
| Relationship | Add, delete, update type/lag |
| WBS | Add, rename, delete, move |
| Calendar | Add, update, delete, add/delete exceptions |
| Resource | Add, update, delete |
| Assignment | Add, update, delete |
| Activity Code | Add/delete types, add/delete values, assign/unassign |
| UDF | Add/delete types, update values |
| Project | Update project settings |
Batch Commands
When you perform a bulk action (such as batch-creating relationships or bulk-updating fields), all individual commands are wrapped in a single BatchCommand. Undoing a batch command reverses all contained operations atomically.
Change Tracker
The change tracker monitors all modifications since the last save:
| Indicator | Description |
|---|---|
| Change count badge | Shows the number of changes in the Editor Toolbar |
| Dirty state | Indicates unsaved changes exist |
The change summary breaks down modifications by entity type and lists all affected entity IDs.
Change Types
| Type | Description |
|---|---|
| Add | New entity created |
| Update | Existing entity modified |
| Delete | Entity removed |
| Move | Entity relocated (e.g., WBS reparenting, activity moved to different WBS) |
Checkpoints
Create named checkpoints to mark significant milestones in your editing session. Restore a checkpoint to revert to that exact state, undoing all changes made after the checkpoint.
Middleware Pipeline
Commands pass through a middleware pipeline before execution:
- Before middleware — can transform or cancel a command
- After middleware — reacts to command results (e.g., collaboration sync)
This ensures that actions like real-time collaboration awareness happen automatically when commands execute.
Tips & Best Practices
- The history holds 200 commands — for very long editing sessions, consider saving periodically
- Use Ctrl+Z liberally — every single field change is fully reversible
- Batch operations are your friend — creating 10 relationships at once counts as a single undo
- The change count badge in the toolbar tells you how many edits you have made since the last save
- Click Discard in the Editor Toolbar to reset all changes and return to the last saved state
Related Documentation
- Activities Grid — Inline cell editing
- WBS Editor — WBS operations
- Relationship Editor — Relationship creation
- Calendar Editor — Calendar modifications