Conditions

    Conditions help to replace the data grabbed to the report with values set on custom.

    Conditions act as intelligent editors, operating on an 

    "if-then-else" principle

    enhancing flexibility in customizing report data presentation. They don't skip records that don't meet the criteria but rather help display their data in a relevant manner.

    Dynamic Text and Date elements can be assigned with conditions, which become available once the field is mapped. Here's how it works:

    1. Clicking the "Add Conditions" button opens the Conditional Values popup, where the selected field is designated as "IF" and cannot be altered.
    2. The next field sets the condition for processing, such as "equals," "is not equal," "contains," and more, depending on the field type.
    3. The subsequent field is for specifying the value used to trigger the condition. This value should be manually added based on the requirement.
    4. The "Then" field can remain empty or be manually assigned a value. This value replaces the database value when the condition is met.
    5. "Else" determines what should be displayed if the condition is not met. By default, it's set to "Database Value," but it can be replaced with a custom value.

    Here's how Text-type fields' conditions function:

    1. The "Equals" condition only processes records that exactly match the entered value in the conditioned field. It's case-sensitive, so the value must match the database case.
    2. The "Is not equal" condition processes records that do not exactly match the entered value in the conditioned field. The match must be exact, and it's also case-sensitive.
    3. The "Contains" condition processes records that contain the value entered in the conditioned field. An exact match isn't necessary, and it's not case-sensitive.
    4. The "Does not contain" condition processes records that do not contain the entered value in the conditioned field. An exact match isn't required, and it's not case-sensitive.
    5. The "Is blank" parameter handles records with an empty conditioned field.
    6. The "Is not blank" parameter handles records with data in the conditioned field.

    Number-type fields have these conditions:

    1. The "Equals" condition only processes records that exactly match the entered value in the conditioned field.
    2. The "Is not equal" condition processes records that do not exactly match the entered value in the conditioned field.
    3. "More" processes values greater than the entered number (without including it).
    4. "Less" processes values less than the entered number (without including it).
    5. "More than or equal to" processes values greater than or equal to the entered number.
    6. "Less than or equal to" processes values less than or equal to the entered number.
    7. "Is blank" and "Is not blank" work as they do for text fields.

    Date-type fields have the following conditions:

    1. "Today" takes the date when the condition is set. :warning:Note! The set date doesn't update dynamically now.
    2. "This week" processes records with dates from the current week when the report is generated.
    3. "This month" processes records with dates from the current month when the report is generated.
    4. "Last week" processes records with dates from the previous week compared to the report generation week (current week not included).
    5. "Last month" processes records with dates from the previous month compared to the report generation month (current month not included).
    6. "Before" processes records with dates before the entered date.
    7. "After" processes records with dates after the entered date.