• Workflows Enhancements: Implemented Swagger (SWG) and LaTeX endpoints for improved API documentation and reporting capabilities.

• Application Configuration:

  • Added functionality for changing the application logo, enhancing brand customization.

  • Introduced the ability to set the uploaded file name within the Admin panel, streamlining file management.

  • Enabled support for SSL connections, ensuring secure data transmission.

• User Interface Improvements:

• Backend Refactor.

• Added translation to the Query group.

• Enhanced Workflow UI.

• Button to create a new record moved to a default table config.

• Resolved bugs impacting Workflow transitions.

• Copy table element bug.

• Admin Panel - broken Query filter.

• Ability to remove the existing workflow
• Default table simple filter, able to filter on a numeric column
• Notifications can be created and sent by the admin to the end-user
• Ability to see the difference between the query statement and the view statement
• Added info on the queries that this app already includes
• Ability to see tables and views list during query creation
• Simple UI to build a fixed filter with expressions for the table by using autocomplete input elements
• Ability to use the page load timestamp in custom expression
• Use lodash in custom expressions
• Ability to perform any actions via a button
• Reset an autocomplete input on call button success
• Show more values in the autocomplete input than visible if values are available

• Custom query update does not refresh definition.

Info

This screen is Builder → Database in the sidebar. The in-product Setup Guide refers to the same screen as Data Model, and older documentation calls it the model builder or ER editor. All four name the ER canvas documented here.

The next important feature of the admin panel is the ER editor. It allows you to check your ER model, define queries, handle workflows, and a lot more. It is the backbone to handle the data side of your database infrastructure:

A workflow in CYPEX is a state machine stored with your data model: named states, allowed transitions, and which roles may fire each transition. Once you enable enforcement, it is applied in the database — a CHECK constraint on the state column plus a trigger that rejects any transition you did not model, and checks the caller’s role against the transition’s permissions. The UI only offers what the database would accept anyway.