See recent changes across your solution.
Reference → Solution → DevOps → Track Changes → Recent | Version Control | Cross-Reference | Unused | Use Count
Recent Changes (Reference):
Automatically logs changes within solutions, covering configuration adjustments and object creation/deletion.
Access: Track Changes → Recent Changes
Data Persistence Settings
Note: Modification of Auto-Delete requires Administrator privileges. Login at Designer Home with Administrator credentials to change settings.
Auto-Delete Options
| Setting | Behavior | Use Case |
|---|---|---|
| Previous Sessions | Delete records from prior Designer sessions | Development cleanup |
| After Build Command | Delete records from previous builds | Build-based tracking |
| After Publish Command | Delete records from previous publishes | Production releases |
| Keep All Changes | Disable auto-delete (manual only) | Full audit trail |
| Tracking Changes Disabled | Stop adding new records | Performance/privacy |
Manual Deletion
With Administrator privileges:
- Select rows (Shift-Click or Ctrl-Click for multiple)
- Right-click selected rows
- Choose "Delete Selected Rows"
Table Columns
Default Visible Columns
| Column | Description |
|---|---|
| Build* | Build number reference |
| TableType* | Database table type (UnsTags, AlarmItems, etc.) |
| RowState* | Current database row state |
| ChangedObject* | Part of object changed |
| UserName* | User who made change |
| Notes* | Additional change information |
Additional Columns
| Column | Description |
|---|---|
| ID | Unique change identifier |
| VersionID | Object version |
| ObjectName | Changed object name |
| ObjID | Object instance reference |
| UserID | User identifier |
| UserComputer | Computer used |
| DateCreated | Object creation date |
| DateModified | Last modification date |
*Columns marked with * are displayed by default
Navigation
Double-click any row to navigate directly to that configuration in Designer.
Best Practices Checklist
Retention Policy
- Development: Use "Previous Sessions" for cleanup
- Testing: Use "After Build Command"
- Production: Use "Keep All Changes" for compliance
- Performance: Review and clean periodically
Audit Requirements
- Enable "Keep All Changes" for regulated industries
- Export regularly for long-term storage
- Document deletion reasons when manual cleanup
Use Cases
| Scenario | Setting | Benefit |
|---|---|---|
| Active Development | Previous Sessions | Clean workspace |
| Test Environment | After Build | Build-based history |
| Production | Keep All | Complete audit |
| Large Solutions | Manual cleanup | Performance control |
In this section...
Overview
Content Tools
Tasks