Missing Field display_on_consent_screen: Inability to Toggle Off Display Content Screen When Consent Text is Void/Null

[victor97gonzalezmartinez]

Problem:
The current implementation lacks a crucial field that allows the deactivation of the display content screen. This absence is critical because there are scenarios where the display toggle is ON or true, yet the consent text is void/null, rendering it impossible to turn off the display.

Example:
Consider the following situation:

In this case, the absence of the necessary field prevents the user from turning off the display even when the consent text is void/null.

Workaround:
Currently, the only workaround is suboptimal. Users must set the consent_screen_text field with a random value, apply the changes, then set the field to void/null and reapply the changes.

Expected Solution:
The addition of a new field is required to allow users to seamlessly toggle off the display content screen even when the consent text is void/null. This enhancement will eliminate the need for the current workaround and provide a more intuitive and user-friendly experience.