How to Develop Custom Rules For the Conditional Display Option
Thrive Architect gives you the possibility to register your own custom conditional display rules. This article will show you how you can create them.
Please note that creating custom rules is an action that should be performed by developers or more tech-savvy persons, as it does require technical knowledge.
Example 1: You can add a new field, called "Page - Demo" with a subfield called "Title - Demo". It will also add a field called "Number of comments - Demo" to the already existing "User" entity.
After activating the plugin, the new fields will be visible in the conditional display pop-up of Thrive Architect:

Note: You can find this demo example on GitHub, here.
Example 2: we'll show how to create a new rule that is conditioned by whether the user has WP Fusion tags assigned to them or not.
Here are the steps to be taken in order to create a new rule:
→ Define the entity class
Firstly, an entity class will have to be defined. This should describe the subject/entity, as well as its properties.
→ Extend the entity class and define specific properties to describe your subject
The get_key function defines a unique identification key for the entity:
The get_label function defines the name of the entity that will be visible to the users.
This will appear inside the visual editor.
The create_object property, upon running the condition logic, will create the entity object containing all the data representing individual fields.
→ Register entity class using the tve_register_condition_entity function
As a result, once you put everything together, the code snippet will look like this:
→ Create an entity field that will be used to fetch the specific entity data which the condition will be tested on
Example (in the visual editor):
→ Extend the field class and define specific properties to describe your field

The get_key function defines a unique identification key for the field.
The get_label function defines the name of the field that will be visible to the users.
This will appear inside the visual editor.
The get_conditions property describes the type of condition that the field data represents.
The get_conditions type can be one of the registered types of conditions that extend the condition class, or you can create your own and register it, using the tve_register_condition function:
Use the condition class as a parameter.
The get_value property has to be defined. This will fetch the value from the entity upon running the condition logic.
The $user_data parameter will contain the entity data object.
→ For multiple-choice fields:
The property get_options has to be defined and the values/label pairs of options have to be provided.
- $selected_values will contain the values already chosen;
- $searched_keyword will be used to filter dropdown results;
As a result, once you put everything together, the code snippet looks like this:
→ Register the field class using the tve_register_condition_field function