From a8e0c680a4c9b8376dd233cd7d71015287ec713b Mon Sep 17 00:00:00 2001 From: WebVPF <61043464+WebVPF@users.noreply.github.com> Date: Sun, 23 Jan 2022 01:39:57 +0200 Subject: [PATCH] Update backend-forms.md --- backend-forms.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/backend-forms.md b/backend-forms.md index 483c1742..a9dae07f 100644 --- a/backend-forms.md +++ b/backend-forms.md @@ -1560,9 +1560,9 @@ In the above example the `send_at` form field will only be shown if the `is_dela Option | Description ------------- | ------------- -`action` | defines the action applied to this field when the condition is met. Supported values: show, hide, enable, disable, empty. +`action` | defines the action applied to this field when the condition is met. Supported values: `show`, `hide`, `enable`, `disable`, `empty`. `field` | defines the other field name that will trigger the action. Normally the field name refers to a field in the same level form. For example, if this field is in a [repeater widget](#widget-repeater), only fields in that same [repeater widget](#widget-repeater) will be checked. However, if the field name is preceded by a caret symbol `^` like: `^parent_field`, it will refer to a [repeater widget](#widget-repeater) or form one level higher than the field itself. Additionally, if more than one caret `^` is used, it will refer that many levels higher: `^^grand_parent_field`, `^^^grand_grand_parent_field`, etc. -`condition` | determines the condition the specified field should satisfy for the condition to be considered "true". Supported values: checked, unchecked, value[somevalue]. +`condition` | determines the condition the specified field should satisfy for the condition to be considered "true". Supported values: `checked`, `unchecked`, `value[somevalue]`. ### Field dependencies