A fixed filter narrows what a Table or List element shows, permanently and
invisibly to the end user — unlike search or allowed filters, which the user
drives. Use it for “this table only ever shows open tickets” or “only rows
belonging to the signed-in user”.
Before v2.0.0 a fixed filter had to be written as a custom expression. v2.0.0
adds a visual rule editor alongside it.
Where it lives
On a Table or List element, in the Filter by section of the element
editor. Click Open Filter Builder to open the Filter Builder dialog.
The dialog is draggable, so you can move it aside and keep looking at the
canvas underneath.
v2.0.0 lets three elements draw on a governed external API connector
instead of a database query:
Element
What the connector supplies
Table
The rows the table renders
Form
The record the form reads, and the payload it writes on submit
Autocomplete
The dropdown’s options
Same canvas, same elements — a different source of data.
Before you start
A connector must exist and be published before it appears in the designer.
Connectors are built and governed on the admin side — allowlist, credentials,
definition, then execution enablement. If the picker says
“No published connectors are available for this app”, the work is in the
admin panel, not the designer. See
Connectors and the
Connectors setup guide.
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.
Quick save — Ctrl+S
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.
This page is for people who build and ship CYPEX applications. It covers what
changes about that job once a deployment has more than one Organization.
Organization scope on this page is enforced by CYPEX itself, not by the browser.
Hiding a row in the admin panel would be cosmetic; what is described below holds
even for a caller who manipulates the request directly.
Application visibility per organization
The Applications page does
not show every application in the deployment to every admin. A system admin can
pick any organization in the organization filter, or clear it to see everything.
An organization admin is always restricted to their own organization — changing
the filter in the browser does not widen what comes back.
