Difference between revisions of "Dynamic Field Visibility Control"
Line 16: | Line 16: | ||
*Define the Primary field | *Define the Primary field | ||
*Define the branching | *Define the branching | ||
− | *Define the branch dependent custom | + | *Define the branch dependent custom field |
===Create new Dynamic Field Visibility Control=== | ===Create new Dynamic Field Visibility Control=== | ||
Line 22: | Line 22: | ||
The Dynamic Field Visibility Control feature can be created against [[Level 1 Entity| level 1s]], [[Level 2 Entity|level 2s]], [[Level 3 Entity|level 3s]], [[User|users]] and [[Organization|Organizations]]. | The Dynamic Field Visibility Control feature can be created against [[Level 1 Entity| level 1s]], [[Level 2 Entity|level 2s]], [[Level 3 Entity|level 3s]], [[User|users]] and [[Organization|Organizations]]. | ||
− | * Click on the Dynamic Field Visibility Control link for the entity that you wish to create the feature | + | * Click on the Dynamic Field Visibility Control link for the entity that you wish to create the feature against. |
[[Image:Dynamic Field Visibility 1.png]] | [[Image:Dynamic Field Visibility 1.png]] | ||
+ | |||
+ | * A list view of previously configured logic is displayed. Click on the '''New Dynamic Field Visibility Control''' button. | ||
+ | [[Image:Dynamic Field Visibility 2.png]] | ||
+ | |||
+ | * The New Dynamic Field Visibility Control is displayed. Populate the Name and, if necessary, the description field and click Save. | ||
+ | [[Image:Dynamic Field Visibility 3.png]] | ||
+ | |||
+ | * When the page refreshes the user will be able to define the Primary field. | ||
+ | [[Image:Dynamic Field Visibility 4.png]] | ||
+ | |||
+ | ===Define the Primary field=== | ||
+ | |||
+ | The Primary field, and indeed all controlling custom fields, must be either a [[Custom Field Type: Select Many – Check Boxes|Select Many – Check Box]] or a [[Custom Field Type: Select One – Combo Box|Select One – Combo Box]]. | ||
+ | |||
+ | * Click on the Primary field icon. This exposed the Edit Field option, which includes a drop-down showing all Check Box and Combo Box custom fields available for the current entity. | ||
+ | [[Image:Dynamic Field Visibility 5.png]] | ||
+ | |||
+ | * Select the relevant custom field and click on the Apply button. The field name will now appear instead of the Primary Field text. | ||
+ | [[Image:Dynamic Field Visibility 5.png]] | ||
+ | |||
+ | |||
+ | ===Define the branching=== | ||
+ | |||
+ | Once the Primary field is selected then the next step is to define |
Revision as of 08:28, 28 September 2016
The Dynamic Field Visibility Control feature is used to create sets of fields that are displayed or hidden dependent on the value selected from another custom field.
The feature is similar to the functionality currently offered by the Display Only – Web Page View, but is designed for scenarios where the required logic is more complex than the dynamic control field allows. This includes . . .
- Multiple levels of field branching logic
- Dependent fields that are not displayed directly under the controlling field
The controlling custom fields must be either a Select Many – Check Box or a Select One – Combo Box.
Contents
Configuration
The feature uses tree settings to add fields and branches. The actual steps for configuring the Dynamic Field Visibility Control feature are summarised below:
- Create new Dynamic Field Visibility Control
- Define the Primary field
- Define the branching
- Define the branch dependent custom field
Create new Dynamic Field Visibility Control
The Dynamic Field Visibility Control feature can be created against level 1s, level 2s, level 3s, users and Organizations.
- Click on the Dynamic Field Visibility Control link for the entity that you wish to create the feature against.
- A list view of previously configured logic is displayed. Click on the New Dynamic Field Visibility Control button.
- The New Dynamic Field Visibility Control is displayed. Populate the Name and, if necessary, the description field and click Save.
- When the page refreshes the user will be able to define the Primary field.
Define the Primary field
The Primary field, and indeed all controlling custom fields, must be either a Select Many – Check Box or a Select One – Combo Box.
- Click on the Primary field icon. This exposed the Edit Field option, which includes a drop-down showing all Check Box and Combo Box custom fields available for the current entity.
- Select the relevant custom field and click on the Apply button. The field name will now appear instead of the Primary Field text.
Define the branching
Once the Primary field is selected then the next step is to define