User manual/Project

Saving and versioning

Single project save, external edits and automatic Git versions.

1 min read

Single save

Save project (Ctrl+S) saves everything: variables, types, connections, screens, faceplates, alarms, loggers, trends, scripts and tasks. The ● Unsaved changes badge and an asterisk in the title mark pending changes; switching sections does not lose them.

All documents are validated before writing. Files are prepared in a temporary folder and only the changed ones are replaced. If a replacement fails, the previous files are restored where possible.

External editing

You can edit the JSON and .py files with any editor. Studio detects when another program changed them and refuses to overwrite. Review your pending changes and use Reload files. There is no automatic merge between Studio and an external editor.

Versions with Git

  1. Open Versions… → Enable Git (Git must be on the PATH).
  2. From then on, every save with changes creates an automatic commit.
  3. The dialog shows the last 30 versions and the diff of the latest one.

Configuration, screens, faceplates, scripts and assets are versioned. runtime/, temporary files and caches are excluded. The repository is standard Git: add a remote and work with branches from your usual tools.

Recovery folders

If you see .abscada-recovery-* folders after an error, review them before deleting: they hold copies to recover the project.

Saving and versioning · abSCADA