Hide element

See also: Show element, Form elements

Actions – Abstract

The Hide element action deletes the 'Visible' option for the linked Target element at runtime. This option must be set for an element to be effectively visible (see note below). An element for which the 'Visible' option is not set is always effectively invisible.

The Hide element action deletes the 'Visible' option for the linked Target element at runtime. This option must be set for an element to be effectively visible (see note below). An element for which the 'Visible' option is not set is always effectively invisible.

►IMPORTANT◄ An element that is defined as 'Required' must also be filled if it is effectively invisible. In contrast, any Validators configured for an element are only effective if it is effectively visible. The action Hide element may therefore influence not only the validation result of the element, but also the validation of parent elements up to the form.

images/download/attachments/189433140/image-2024-10-8_12-14-7-version-1-modificationdate-1728382447164-api-v2.png

  • The action can only be selected under Action type if a Target element is linked.

  • The 'Visible' property is available for all Form elements, so that any target element except the form element itself can be linked.

►NOTE◄

  • The Hide element action always turns a Target element effectively invisible at runtime.

  • If a Target element of an Element containers type is hidden, all direct and indirect child elements turn effectively invisible. If these are individually 'set to visible', they are considered as latently visible.

Example

In an input form for Shipments, a group of entries for 'Specifics' can be deleted globally by checking the Check box No specifics. In response, the relevant Row layout container should also be hidden unless this Check box is cleared again, if necessary.

Runtime example:

images/download/attachments/189433140/image2020-6-19_16-58-0-version-1-modificationdate-1728378511170-api-v2.png

  • For a new shipment, the Specifics are displayed initially. For specific options (in the screenshot: Signature release) further input fields (in the screenshot: Delivery location) may appear when checked.

images/download/attachments/189433140/image2020-6-19_16-58-34-version-1-modificationdate-1728378511173-api-v2.png

  • When the option No specifics is set, the Row layout container with the specifics disappears.

images/download/attachments/189433140/image2020-6-19_16-59-0-version-1-modificationdate-1728378511175-api-v2.png

  • If the option is activated again afterwards, previous entries are deleted.
    ►IMPORTANT◄ The action Hide element does not delete the entries. This must be arranged separately, as well as the show/hide for the Text field Delivery location depending on the Check box Signature release.

Configuration:

images/download/attachments/189433140/image-2024-10-8_12-16-36-version-1-modificationdate-1728382596267-api-v2.png

For the Check box element No specifics the behaviour displayed on the left is configured:

  • Here, Changed (with the Change type 'Exclusively by user') and Form data loaded are set as Triggering events. Since the Check box does not specify a data field, it appears deleted (empty) when the form data is loaded.

  • The Behaviour type Filled executes the Actions on 'true', if the Check box is set.

  • Under the Actions on 'true', the action Hide element is executed with the Row layout container 'Specifics' as the Target element.

  • Finally, the Execute behaviour action calls the behaviour 'reset' for the same Target element. This behaviour (not shown in screenshot) executes a series of Set value actions that reset all elements defining 'Specifics'. Otherwise, any settings taken previously would reappear when the Check box is cleared. Upon saving the shipment, these values would otherwise be stored despite being hidden in the form.