Nested logic allows you to set a parent condition that must be met before additional (child) logic is evaluated. This lets you build more sophisticated rules that handle complex combinations of answers and dependencies.
Instructions
1. Understand when to use nested conditions
- Use nested conditions when there’s a primary requirement that must be met before other rules apply.
- Example:
- “Show GST details only if the contact is a company and either:
- the company is Australian, or
- the company is overseas but registered for AU GST.”
- In this case, the logic is dependent on the contact being a company before checking other criteria.
2. Open the Logic tab
- Select the field, section, or template you want to control.
- Click the Logic tab.
3. Create the parent rule
- Click + Rule and create the top-level condition (e.g. Contact type = company).
- Set the connector for this level (usually AND) if you’re combining multiple parent-level rules.
4. Add a nested rule set
- Click + Rule Set to create a nested group of conditions.
- In the new rule set, add rules that define the secondary logic (e.g. Country = Australia OR Registered for GST = Yes).
- Choose the connector (AND/OR) for rules inside the nested set.
- You can continue nesting to as many levels as needed to match your requirements.
5. Review the nested structure
- Nested rules are visually indented beneath their parent condition.
- Make sure the structure follows your intended logic flow.
6. Save and test
- A logic pill will appear after saving.
- Click the pill to view the full nested condition summary.
- Use Preview mode to test that the logic evaluates correctly across all paths.
Common Issues & Solutions
- Issue: The logic never reaches the nested conditions
- Solution: Check if the parent condition is too restrictive or returning FALSE — child rules are only checked if the parent condition is TRUE.
- Issue: Unexpected results due to connectors
- Solution: Confirm whether you’ve used AND or OR correctly within each rule set and between levels.