Overview

Release 3.18 brings a powerful new feature to Ascendix Composer: Conditions. This enhancement gives you greater flexibility and control over how content is displayed in your Printable and Microsite templates. With Conditions, you can dynamically show, hide, or replace content blocks based on specific data values - making your templates smarter and more responsive to your data.

What Are Conditions?

Conditions allow you to set rules that determine how certain parts of your template behave, depending on the values of fields in your data. For example, you can:

• Hide a section if a certain field is empty or has a specific value.
• Display or hide static text next to a dynamic variable only if that variable exists.
• Replace the content based on field values.

Key Use Cases

• Conditional Visibility: Hide or show template blocks based on field values (e.g., only display a section if “Status” is “Active”).
• Smart Labels: Hide static labels if the corresponding dynamic variable is missing (e.g., don’t show “Property name:” if there’s no property name value presented).
• Complex Logic: Use multiple IFs and nested IFs for advanced scenarios.

How to Use Conditions in Ascendix Composer

1. Accessing Conditions

• Open your Printable or Microsite template in Ascendix Composer.
• Select the element you want to apply a condition to.

2. Setting Up a Condition

1. Choose a Field:
   Select the field from your data collection that you want to use as the basis for your condition. It can absolutely be any field from the current collection, including text, number, date/datetime, and boolean field types.
2. Define the IF Statement:
   • Compare the selected field with a value.
   • You can only select one field per condition.
3. Configure THEN and ELSE Actions:
   • Assign what should happen if the condition is met (THEN) or not met (ELSE). If you remove THEN or ELSE, it means the element will remain unchanged if the scenario happens.
   • Actions can include total replacement or changing visibility.
4. Avoid Logical Conflicts:
   • Each action (e.g., “Change Visibility”) can only be assigned once per THEN/ELSE to prevent conflicts.
   • The UI will help prevent conflicting assignments.
5. Shared ELSE for Multiple IFs:
   • When you have multiple IFs for one field, they share a single ELSE action to keep the interface clean.
   
   

   

6. Advanced Logic:
• Use multiple IFs and nest them for complex scenarios.

3. Example: Hiding a Label if a Variable is Missing

Suppose you have a label “Property name:” followed by a dynamic variable {{Property name}}.

Set a condition: IF “Property name” is empty, THEN hide both the label and the variable.

4. Example: Styling Based on Status

IF “Status” equals “Active”, THEN replace the element with “Active”.

[deleted ELSE] (means no changes happen in this case).