Most form builders can draw a field. Far fewer can make a field behave — appear only when it’s relevant, suggest a value the moment you start typing, or let a list be filtered the way a person actually thinks (“four stars and up”, “this month”). In PPPHP RAD Studio those behaviours are now configuration, not code: you set them once in the Designer, and they compile into the plain PHP your app runs on.
Key takeaways
- Conditional field visibility — show a field only when another field matches (e.g. Spouse name only when Marital status is Married). Hidden means hidden: not shown, not submitted, and not required.
- Enforced on the server, not just the browser. A hidden-but-required field never blocks a save, because the same condition is re-checked server-side — so the rule can’t be bypassed by editing the page.
- Smarter list filters — a star “& up” rating facet, a compact segmented/pill bar for statuses, and one-click date presets (Today · This week · This month · Last 30 days).
- Type-ahead from your own data — Tags and the choice controls can suggest from the column’s existing values, with no list to maintain.
- Configured once, compiled in. Everything here is baked into the generated app at build time. No runtime add-on, no separate form engine — just PHP you own.
Fields that show up only when they matter
Every real form has fields that only apply sometimes. Ask for a company name only for business customers. Ask why only when someone picks “Other”. Collect a delivery address only when the order isn’t collection. Done badly, these turn into a wall of boxes where most are irrelevant to most people — and a required field the user can’t see becomes a save that mysteriously fails.
In the Designer, open a field’s Field controls and switch to the new Visibility tab. Pick a controlling field, a condition, and a value:
The important part is what happens when a field is hidden: it is not shown, not submitted, and not required. A required “Reason” that only appears for “Other” will never block the save for everyone else — because the visibility rule is also applied to validation, on the client and again on the server. That server check matters: client-side logic alone can be bypassed by anyone who opens developer tools, so a form that enforces its own rules only in the browser isn’t enforcing them at all.
Filters that match how people search
A list is only as useful as its filters. Generic text boxes are fine for names; they’re poor for ratings, statuses and dates. Three new filter controls cover the cases people actually reach for:
They apply the same way every other filter does, and they ride the generated list’s existing query engine — so sorting, pagination, shareable URLs and the REST API all keep working unchanged. And because a saved view in PPPHP simply remembers the current filter state, a view like “My region, four stars and up, this month” is one click to save and one click to return to.
Suggestions from the data you already have
Nothing is more tedious than maintaining a hand-typed list of options that your data already contains. The Tags control and the choice controls — Dropdown, Radio Group, Button Toggle, Checkbox — can now take their options from “this column’s existing values”. The app reads the distinct values already saved in that column and offers them as type-ahead suggestions, updated automatically as your data grows.
For Tags, suggestions show even in free-form mode: you get the convenience of autocomplete and the freedom to add something new — the “suggest, but don’t restrict” pattern good tag inputs are known for. It runs in the generated app the same way the lookup machinery does, so there’s nothing extra to wire and nothing new to host.
Values that read the way you entered them
The display side got the same attention. A duration stored as minutes reads back as 2h 30m, not 150. Big numbers can show in compact form (1.2K, 3.4M) and negatives in accounting parentheses. A long URL can show as just its domain so it fits a column. A progress bar can colour by thresholds you choose, or invert them for metrics where low is good. Small things — but they’re the difference between a screen that looks generated and one that looks considered.
Configured once, and it’s yours
None of this is a runtime plugin or a hosted form service you rent. You configure it in the Designer, and it’s compiled into the generated application: clean, readable PHP, with prepared statements, escaped output, CSRF-protected forms and the same role permissions, row-level security, field encryption and audit trail every PPPHP app carries. If you ever walk away from the tool, the app keeps working — because it’s just code you own.
Build an app that behaves, not just one that stores
PPPHP RAD Studio turns a database into a secure web and mobile application — with forms that react, filters that fit, and plain PHP you keep. PPServer gives you a free, patched local stack to build it on.
Frequently asked questions
Can I show or hide a form field based on another field, without writing code?
Yes. In the Designer, open a field’s Field controls and use the Visibility tab: pick a controlling field, a condition (is, is not, is any of, contains, is filled in, is empty) and a value. The field then appears only when the condition is met, live as the user types — no JavaScript or events to write.
What happens to a required field when it is hidden by a condition?
It is not shown, not submitted, and not required. The visibility condition is applied to the field’s validation too, on the client and again on the server, so a conditionally-hidden required field never blocks the save for people it doesn’t apply to.
Is the conditional logic enforced on the server or only in the browser?
Both. The browser shows and hides the field live for a fast experience, and the same condition is re-checked on the server when the record is saved — so it can’t be bypassed by editing the page or disabling JavaScript.
Can a list be filtered by star rating, status pills, or a date preset?
Yes. There is a star “& up” rating filter, a compact segmented/pill filter for exact values like status, and one-click date presets (Today, This week, This month, This year, Last 7 / 30 days) that compute to real dates and preserve your other active filters.
Can a dropdown or tag field suggest values from existing data?
Yes. Tags and the choice controls (Dropdown, Radio Group, Button Toggle, Checkbox) can take their options from “this column’s existing values” — the app reads the distinct values already saved and offers them as suggestions, with no list to maintain. For Tags, suggestions also appear in free-form mode.
Do these features need a runtime plugin or an external form service?
No. Everything is configured in the Designer and compiled into the generated application at build time. The result is plain PHP you own, with prepared statements, CSRF protection, role permissions, row-level security, field encryption and an audit trail — no form engine to rent or host.
Will the new filters break sorting, pagination or the REST API?
No. They ride the generated list’s existing query engine and submit in shapes it already understands, so sorting, pagination, shareable URL state, saved views and the REST API keep working unchanged.
Build your first app today
Point PPPHP RAD Studio at a database — or start on the built-in one — and have a secure, responsive web app running before lunch.