Conditional display properties

conditional display (visibility rules) lets an administrator define when specific parts of a record should be hidden, based on the record's own data by default, a record always shows all of its fields, sections and tabs — regardless of the record's type or stage on large, shared data models this clutters the screen and increases the risk of entering data in the wrong place when a rule's conditions are met, its selected fields, sections, tabs, relation sections or charts are hidden on the record's detail page examples when you have a vehicle object, different fields can be relevant for different vehicle types for example if you sell trucks and cars, you want to hide certain fields for vehicle type truck, and other ones for vehicle type car hide a section until the record reaches the relevant stage show one set of fields for one contract type and another set for another type key principle visibility, not security visibility rules control only what is shown on screen they are not a permissions or security mechanism no data is removed or deleted any user can temporarily reveal hidden elements (see show hidden conditional fields) access rights are a separate mechanism and are not affected where it applies works on the record detail page cms record detail page process detail page why while a record is being created or filled in, fields appearing and disappearing would be confusing, and "hiding" something before the record exists makes little sense rules therefore apply only when viewing the full card of an already existing record how an administrator configures rules a new "visibility rules" tab appears in entity settings the tab is available for both cms entity and process settings for each entity you can create one or more rules rules can be reordered via drag and drop rule structure each rule has rule title — the rule's name, multilingual enabled toggle — a rule can be turned off without deleting it a disabled rule is ignored entirely elements affected — what exactly this rule hides when to hide (conditions) — for which record data to hide elements affected elements are picked from the entity's tree of tabs → sections → fields (relations and charts are shown as sections) you can select an entire tab (everything inside is hidden), or an entire section , or individual fields , or a relation or dashboard — as a whole section only to manage the list there is search , expand all / collapse all , and an "elements affected (n)" counter checkbox states state meaning ☐ (empty) not selected, the element is visible ✓ (blue) explicitly selected at this level − (minus, blue) not selected itself, but has selected descendants (partial selection) conditions (when to hide) the same condition builder as elsewhere in the product is used meet all / any of the conditions; each condition is field — operator — value ; there can be several conditions, and they can be grouped (nested groups) conditions are evaluated against the record's own field values what the end user sees on the record detail page the system checks every enabled rule against the record's current values for each rule whose conditions are met, its elements are hidden if several rules apply, an element is hidden when at least one matching rule hides it (or logic between rules) everything else is shown as usual example the rule "hide extended info for premium vehicles" hides the extended info tab when price (eur) ≥ 50000 on a vehicle priced at 31,200 eur the extended info tab is shown; on a vehicle priced at 60,000 eur the same tab is hidden show hidden conditional fields on the record detail page, the record's menu contains a "show hidden conditional fields" action — temporarily reveal everything hidden by rules available to all users , but only if the entity actually has visibility rules if there are no rules, the menu item is not shown either temporarily reveals all elements hidden by rules, so everything can be seen and verified it is a personal display toggle (remembered per user and per entity) — it does not change the rules themselves and does not affect other users rule indicator in properties settings in settings → properties editor , any field, section or tab affected by a visibility rule shows a small indicator icon the indicator appears at all three levels the field row, the section header, and the tab header the icon is visible only if the element is affected by at least one rule clicking it opens a short menu listing the rules that affect this element (there can be several) selecting a rule navigates to the "visibility rules" tab for review/editing this makes it immediately clear, while editing the data model, which elements are governed by rules and why selection behaviour and edge cases whole tab/section selected everything inside is hidden if you later add a new field inside that tab/section, it is hidden automatically too (the rule "owns" the container) unchecking one descendant if you uncheck a single field inside an otherwise fully selected section/tab, the rule switches to "specific elements" mode only the ones you explicitly left are hidden, the parent shows a partial selection mark (−), and newly added fields are no longer hidden automatically moving a field or section if an element is hidden because its parent tab/section is selected , and you later move it out — it becomes visible again automatically (and moving it into a hidden container hides it) the behaviour follows the container if an element was selected individually , it stays hidden regardless of where it is moved required fields cannot be hidden a required field cannot be hidden — that would block saving the record in the selection tree, required fields are shown but disabled for individual selection and marked with an "always visible" badge (lock icon) with an explanatory tooltip even if the whole parent tab/section is selected, its required fields are not hidden the section hides everything it can, while required fields remain visible if a field was added to a rule and later made required (or deleted/hidden in properties), the reference to it is removed automatically from the rule, and the "elements affected" counter is recalculated a field used both as a condition and as a hidden element if a field is used in a rule's conditions and you try to hide the same field, the system shows a small warning ("this property is used in this rule's conditions hiding it can cause conflicting behaviour ") it does not block the selection — it is just a hint that hiding a field you are also testing a condition on may give unexpected results multiple rules on one element each rule is independent an element is hidden if any enabled, matching rule hides it each rule needs at least one condition and one element a rule must have at least one condition and at least one affected element — both are required a rule with no conditions is not allowed this rules out accidental "always hide" rules — hiding is always contextual, based on record data