See recent changes across your solution.

Reference  Solution  DevOpsTrack Changes | Git 


Track Changes Designer UI (Reference): Features for logging and tracking engineering solution changes, including Recent Changes, Version Control, Cross-Reference, Use Count, and Unused Objects for audit trails and impact analysis.

Access: Track Changes (in Solution Explorer)


Navigation Pages

PagePurposePrimary Use
Recent ChangesChange log with configurable persistenceAudit trail and navigation
Version ControlTable version trackingOnline configuration sync
Cross-ReferenceObject usage locationsImpact analysis
Use CountUsage frequencyResource optimization
Unused ObjectsUnreferenced objectsCleanup candidates

Core Functions

Change Tracking

Version Control tables maintain summaries by Module and Configuration Table, tracking current versions and last modifications of all solution elements. This ensures consistency when connecting to Runtime for online changes.

Cross-Reference Engine

Powers multiple analysis features:

  • Find Results Panel in Designer
  • Use Count calculations
  • Unused Objects detection
  • Impact analysis for changes

Limitations

Important: Cross-Reference only detects direct object usage. Indirect references are not tracked:

Indirect Usage TypeExampleImpact
String referencesAsset("/folder1/tag1")Not detected
.Link propertyTagReference via stringNot tracked
API accessExternal applicationsNot visible
Dynamic referencesScript-generated namesNot found
OPC UA/MQTTExternal consumersNot tracked

Integration Points

With Designer

FeatureIntegrationPurpose
Find Results PanelUses Cross-Reference dataObject search
Home PageShows Recent ChangesQuick access
Runtime DiagnosticsCompares versionsOnline config
Double-click navigationFrom any table rowDirect access

With Runtime

Version Control data enables:

  • Online configuration verification
  • Hot reload compatibility checks
  • Change synchronization
  • Version mismatch detection

Best Practices Checklist

Regular Maintenance

  • Review Recent Changes daily
  • Check Unused Objects weekly
  • Monitor Use Count for optimization
  • Verify Cross-References before deletion

Before Removing Objects

  • Check Unused Objects table
  • Verify no indirect references
  • Confirm no external usage
  • Use Find Results for verification
  • Document removal reason

Change Management

  • Configure appropriate auto-delete settings
  • Keep audit trail for compliance
  • Export changes for version control
  • Review Version Control before deployment

Performance Considerations

AspectRecommendationImpact
Recent ChangesSet auto-delete policyDatabase size
Cross-ReferenceRefresh periodicallyQuery speed
Use CountReview weeklyPerformance insight
Unused ObjectsClean quarterlySolution size

Troubleshooting

IssueCauseSolution
Missing referencesIndirect usageManual verification
Version mismatchUnsaved changesSave and build
Large change logNo auto-deleteConfigure cleanup
Slow navigationLarge databaseOptimize settings



In this section...