**Problem:**

l10n_co_dian_certification_process (Activate the certification process) can still be checked if l10n_co_dian_test_environment (Test environment) is left unchecked. There are two ways to cause this:

1.

|  | l10n_co_dian_test_environment | l10n_co_dian_certification_process |
|--------|--------|--------|
| Start | False | False |
| End | False | True |

Here, the write call will trigger l10n_co_dian_certification_process is set from False to True without triggering the “if” condition since l10n_co_dian_test_environment is not set.

2.

|  | l10n_co_dian_test_environment | l10n_co_dian_certification_process |
|--------|--------|--------|
| Start | True | False |
| End | False | True |

Here, l10n_co_dian_test_environment is set from True to False from the first write call, which will trigger the “if” condition, causing it to also set l10n_co_dian_certification_process to False. However, then the l10n_co_dian_certification_process is set from False to True by the second original write call.

**Purpose:**

Make the l10n_co_dian_certification_process field a computed field such that l10n_co_dian_certification_process cannot be set to True if l10n_co_dian_test_environment is False.

**Steps to Reproduce on Runbot:**

1. Install l10n_co_dian

Case 1:

2. Start at the state, where both l10n_co_dian_test_environment and l10n_co_dian_certification_process are False
3. Check the box for l10n_co_dian_test_environment so that the box for l10n_co_dian_certification_process will also show up. Then check the box for l10n_co_dian_certification_process and uncheck the box for l10n_co_dian_test_environment. Finally save the new configuration.

Case 2:

2. Start at the state, where l10n_co_dian_test_environment is True and l10n_co_dian_certification_process is False
3. Check the box for l10n_co_dian_certification_process then uncheck the box for l10n_co_dian_test_environment. Finally save the new configuration.

opw-4225471

Forward-Port-Of: odoo/enterprise#76098
Forward-Port-Of: odoo/enterprise#73532

Since [1], a fix was introduced to display the actual value of a relational field instead of its ID. However, another issue occurs when a form is inside a tab (Tabs snippet) and a new tab is added. During this process, the currently active tab is cloned, including its field IDs. Although a method exists to update the IDs after cloning, the form rendering is triggered beforehand.

This causes the labels property of input elements—which is expected to return a NodeList of associated <label> elements—to fail because the cloned input IDs are not unique.

This commit resolves the issue by using querySelector to target the associated label elements directly.

Steps to reproduce:

- Open the Website editor.
- Drag & Drop a Tabs snippet.
- In the first tab, drag & Drop a Form snippet.
- Set the first field as a radio buttons.
- Make the second field's visibility depend on the first field.
- Add a new tab by clicking the "+" icon in the right panel.
- Observe that a traceback occurs.

A second issue related to [1] has been resolved for cases where there is
only a single checkbox. In this scenario, the value displayed in the
visibility condition dropdown menu should be "Yes".

opw-4345340

[1]: https://github.com/odoo/odoo/commit/4b37f22cece5424d6992c6bafe619c9a457d184b

Forward-Port-Of: odoo/odoo#191709
Forward-Port-Of: odoo/odoo#190460