Click on a field in the form. The selected field is designated by the chasing blue dotted lines. Once a field has been selected, the field properties for that field type appear in the Properties section on the left hand side of the Form Builder. The Conditional Actions Builder link is contained in the Validations section of the form properties as shown in the figure below.
Currently, the field reads 2 – View/Edit. This indicates there are two Conditional Actions for the Date of CRO/Sponsor Notification field as shown above. As conditional actions are added to the field, the number will increase to represent the number of Conditional Actions that are on the field. Likewise, if a Conditional Action is removed or deleted, the number will decrease.
Conditional Action Types
The Conditional Actions Builder contains 6 types of actions as shown in the following figure:
To insert conditions/criteria in the Expression Area shown in yellow above, click on the arrow at the bottom. Once at least one condition exists, the other arrows can be used to insert additional expressions where they are needed. To create blocked expressions, select the "Block" button prior to inserting a new condition. Expressions can also be deleted using the red "X" icon.
When done, click the "Okay" button prior to saving the form.
Conditional Action Limitations and Considerations
Validations are the only three type of conditional action that will function inside a normalized table (sub-form):
If a field contains both Hide and Validation type CAs, its possible in instances where the field becomes hidden, the validation will fire an edit check error in the background. To prevent this, an additional CA would be needed on the field to prevent the validation from firing when the field is hidden.
Upload field types cannot be used with conditional actions. For example, the following CA would not work: "Send an email notification if 'Upload field A' is not blank." From a conditional action and data validation perspective, the system does not recognize changes to upload fields. Additionally, characterizing an upload field as 'required' in the field properties does not have an effect.