Skip to main content
CYPEX Documentation
Support
v2.0.0 Latest stable release View changelog ->

Release Notes v1.4.1

Features

  • Migrate an app definition Now, it’s possible to migrate apps that have versions different from the latest ones.

  • Ability to get information about the available DATA API endpoints

  • Usability improvements:

    • Add an ability to inject custom CSS styles into an app
    • Add an ability to toggle a modal dialog via an action
    • Fetching query data now available without a visible element
    • Preview all columns of a table
    • Generate pages for specific queries in the app
    • Query information contains which pages were generated
    • Preview the data of an existing query and of a database table
    • Ability to display a custom error message in a form
    • Table reload on form success
    • Data preview for a query in edit mode
    • Ability to delete a role
    • Permissions editing of a custom query
    • Ability to render different elements if the advanced conditional element is not visible
    • Add row actions to an existing table
    • Page title moved to the appbar

Resolved Bugs

  • Controlled date input/ date-time input cannot be cleared once a value is set

Read full post

Release Notes v1.3.0

Features

  • Install CYPEX on an existing database

    It is now possible to run CYPEX with an existing PostgreSQL database rather than using the one shipped with CYPEX by default

  • Usability improvements:

    • Display the table count within a schema
    • Display the table disk size in the entity tree
    • Add the ability to edit the title of a query
    • Display runtime errors in the query preview when creating or editing a query
    • Display the query statement while in edit mode
    • Add the ability to upload an image in the image element configuration

Resolved Bugs

  • Nested form cannot be set as data source in input elements

Read full post

Governance evidence

A change that affects a tenant boundary should be reconstructable afterwards. CYPEX records part of that automatically and leaves the rest to you. This page documents the three layers where evidence lives, in order of increasing persistence:

  1. The permission audit log — queryable in PostgreSQL.
  2. The write path — what CYPEX captures automatically, and what it does not.
  3. Documentation approvals — recorded in product docs and release notes.

If you make a non-trivial decision about an Organization (split, merge, role remap, schema revoke), keep the audit query and its output with the change record, and add an ADR-style note under CYPEX internals.

Read full post