Dependencies define all possible new values which can be set respecting the settings under dependent values. Its activation is defined with option activation.
...
The following table describes how setting type influences the activation. For the example only two fields are used, in reality the number of fields and hereinafter the sets in the activation are unlimited.
Type | Field 1: Test value / | Field 2: Test value / | Result |
|---|---|---|---|
All filter values must be changed and match (1). | Y / X → Y | Y / Y → Y | 🔲 |
All filter values must be changed and match (2). | Y / X → Y | Y / X → Y | ✅ |
All filter values must be changed and match (3). | Y / X → Y | Y / X -→ Z | 🔲 |
One filter value must be changed, all must match (4). | Y / X → Y | Y / Z → Z |
|
One filter value must be changed, all must match (5). | Y / X → Y | Y / Y → Y |
|
One filter value must be changed and match (6). | Y / X → Y | Y / Z → Z | ✅ |
Explanations:
(1) | Both field values match the test value, but only one has been changed. Dependency will be ignored. |
(2) | Both field values match the test value, and both values have been changed. Dependency will be used. |
(3) | Both values have been changed, but only one matches the test value. The dependency will be ignored. |
(4) | One value was changed; the second doesn't match the test value. The dependency will be ignored. |
(5) | One value was changed and both values match the test values. Dependency will be used. |
(6) | One value was changed and matches the test value. The second value can be false. Dependency will be used. |
...