Every save in the Application Designer creates a save point — a recoverable prior state of the application. v2.0.0 makes saving cheaper to do and easier to read back.
Press Ctrl+S (Cmd+S on macOS) anywhere in the editor to save immediately. No dialog opens. A Saved confirmation appears when it succeeds; if it fails, the error appears in its place.
CYPEX may store data that requires a durable change trail. History
tracking (table auditing) records every INSERT, UPDATE, DELETE, and
TRUNCATE on a selected entity in cypex.t_history. Each entry holds before
and after JSON images, a timestamp, the PostgreSQL role that made the
change, and — when the change came through CYPEX — the CYPEX user id.
Changes made directly against the table are captured too, so no separate
application-level logging layer is required for those row events.
CYPEX allows users to audit tables and to keep track of login activity. Both live under Monitor & Audit in the admin panel, as two separate entries: Table Audit History and User Audit Trail.
For the enablement path and how row images land in cypex.t_history, start at History Tracking. Permission and organization decisions are a separate stream — see Governance evidence.
When a table is audited (see Database — Auditing), its change history shows up here. Filter by schema and table using the dropdowns at the top right:
