Why CFC Charts Have No Undo or Save Button in SIMATIC PCS 7

Continuous Function Chart (CFC) in SIMATIC PCS 7 lacks an 'Undo' button and an explicit 'Save / Don't Save' prompt upon exit because it is an auto-saving, transaction-based database editor. Unlike document-based programming editors (such as LAD/FBD/STL in classic STEP 7), every graphical action in CFC—placing a block, drawing an interconnection, or editing a parameter—executes atomic database commits directly into the underlying Step 7 project database. To safeguard work against accidental deletions, engineers must utilize chart readback archives, project versioning, and Control Module Types (CMT).

Database Architecture of CFC vs. Document-Based Editors

Engineers transitioning from discrete PLC programming environments (such as STEP 7 classic LAD/FBD or TIA Portal) to SIMATIC PCS 7 frequently observe that the CFC editor provides neither an Undo menu item nor a prompt asking to Save changes when closing a chart window.

This fundamental design difference arises from the underlying architecture of PCS 7:
1. Document-Based Editors (LAD / FBD / STL):
* When opening a block (e.g., FC 1 or FB 10), the editor loads the block bytecode into a temporary volatile RAM buffer.
* Edits remain local to the buffer until the user clicks Save (Ctrl+S). If the user makes an error, the in-memory undo stack can reverse changes, or closing without saving discards edits.
2. Transaction-Based Database Engine (CFC):
* CFC charts do not exist as independent standalone file documents. They are graphical front-ends querying the relational STEP 7 project database (*.s7p).
* When you drag a block onto a sheet, delete an interconnection, or modify a parameter, CFC immediately executes an atomic database transaction. The database allocates instance DB numbers, updates cross-reference pointers, recalculates run sequence positions in cyclic OBs, and updates technological hierarchies.
* Because every action commits to the database instantly, there is no uncommitted memory buffer. Consequently, closing the window commits nothing new—everything is already saved in the database repository. Implementing a simple "Undo" button would require full relational database transaction rollbacks across multi-instance data structures.

Engineering Strategies to Protect Against Accidental Modifications

Because deletions and parameter alterations in CFC are immediately permanent in the offline database, engineers must deploy disciplined development workflows:

Perform Multiproject Archiving Prior to Major Changes:
* Before modifying complex interlocks or refactoring plant logic, always select File -> Archive in SIMATIC Manager.
* Store timestamped archives (e.g., Project_20261014_PreRefactor.zip) locally. If an accidental deletion occurs, the chart or project can be recovered cleanly.
Utilize CFC Chart Readback:
* Prior to modifying running charts, execute Chart -> Read Back....
* This captures current live tuning parameters (PID gains, alarm limits, timer presets) from the online CPU into the offline database, preventing parameter loss during subsequent compiles.
Copy Charts Before Editing:
* If testing experimental logic, duplicate the chart within the Plant View (e.g., Reactor1_Temp_Test).
* Perform modifications on the duplicate chart. Once verified, delete the obsolete chart.
Deploy Control Module Types (CMT) in Modern PCS 7:
* In modern PCS 7 architectures, manage logic within Control Module Types (CMT) in the Master Data Library.
* Modify the master type and test it in isolation before using Synchronize with CMT to propagate validated changes to active plant instances.
Next-Generation DCS Evolution (SIMATIC PCS neo):
* Engineers seeking modern session-based undo, multi-user version branches, and change rollback will find native undo/redo capabilities fully implemented in Siemens' web-based DCS platform, SIMATIC PCS neo.

Verification

In SIMATIC CFC, place a test block (e.g., Pcs7DiIn) and connect an input.
Close the CFC window without pressing any save command.
Reopen the CFC chart. Confirm that the block and interconnection are present exactly as placed, verifying instant transactional persistence.
In SIMATIC Manager, verify that instance DB numbers and symbol table assignments were updated simultaneously.

Limitations and Operational Precautions

Accidental deletion of a block in CFC immediately removes its instance DB and symbol bindings from the offline program. If changes are compiled and downloaded, CPU variables are re-initialized.
Never use Windows Task Manager to abruptly kill s7jcfcap.exe (CFC editor) in an attempt to discard unwanted changes; killing the process mid-transaction can corrupt the Step 7 database, requiring a slow database reorganization.
In multi-user engineering mode, changes committed by one engineer in a CFC chart become instantly visible to other engineering clients upon chart refresh.

Engineer FAQ

Can I restore an accidentally deleted CFC chart?
If a chart is deleted, it is removed from the project database. You can restore it by retrieving a previous project archive (*.zip) or copying the chart from an uncorrupted backup project.
Why does CFC allow deleting blocks that are online?
CFC modifies the offline project database. The online CPU continues executing the previously downloaded program uninterrupted until the engineer compiles and downloads changes.
Does CFC have any auto-backup feature?
No automatic file version history is maintained inside classic Step 7. Versioning must be managed externally via SIMATIC Version Trail / Version Cross Manager or manual archiving.

Technical References

SIMATIC PCS 7 CFC for S7 / M7 Manual (A5E41356247-AA).
SIMATIC PCS 7 Engineering System - Engineering Workflow and Data Management.
Siemens Industry Online Support Entry ID 109801081: Working Efficiently with CFC in SIMATIC PCS 7.