ENGAGE HELP CENTER
Advanced conditions
This guide will help you with setting up more advanced logic relationships between all of the activities of your project.
What are the benefits of this feature?
  • Increased control over the participant experience
    The Manage conditions builder equips the project administrators with valuable controls over the way the participants of the initiative will experience the whole project flow. This is a useful toolbox for designing a straightforward and uncomplicated project flow.
  • Intuitive project design
    Similarly, the Manage conditions builder is a great instrument of building an intuitive and logical project design. From simple controls over the number of times a specific project activity is available to a participant to intricate Conditional expressions, make sure that the project flow is detailed and polished to ensure its success, as well as excellent participant experience.
The selection Manage conditions also provides an option to set up in-depth advanced conditions. This function can not only regulate the logic relationships between the elements of the project, but also determine how the components of a specific survey can work into the general design of the project flow. With an advanced conditions setup your project can be tailored to recognize and incorporate different groups of your audience. The Conditions builder can also be accessed when selecting the Conditions button located in the top-right corner of the Activities view of a project.
Once a set of rules has been created, a robot icon will appear in the top-right corner of each activity card that has some conditional expressions built.
Advanced conditions
When selecting the tab Advanced of the Conditions builder, you will be presented with the basic building blocks to start constructing logic conditions for the project. The comparatively complicated expression building process is now available in a much easier form with only a small number of elements that will enable you to build the most intricate project flows.
Condition - the situation or state that must exist for the selected project activity within the expression.
Select activity - select one of the Consent or Survey activities of the project from the dropdown menu. This field determines the activity for which the conditional expression will be built, or rather what conditions have to be met for the selected activity to be seen by the project participants.
Add condition - allows to add a new single conditional expression.
Add group - allows to add a new set of expressions that can be grouped below the conditional criteria And, Or.
And - conditional criterion that requires all of the conditions it combines to be true.
Or - conditional criterion that requires only one of the conditions it combines to be true.
Logic behind Add condition and Add group
It is possible to add however many conditions and groups as necessary both at the top level and inside the already created groups. It is important to follow the level from which these buttons are selected.

Add condition
When selected from the a certain level of expression, this button will add a new condition on the chosen level. Add however many conditions to each level as needed.
Add group
When selected from the first level of expression, this option will add a new group of the same level.
However, when selected from the second level of expression, this button will add a new sub-level group.
Conditions
A set of operators of the conditional expression is available for your disposal to build the system of rules for your project activities.
is signed - an operator specific to the Consent activity. It is used to make the activity for which the rules are being built available only after the Consent activity has been signed.
is revoked - an operator specific to the Consent activity. It is used to make the activity for which the rules are being built available only after consent has been revoked.
completed (days) ago - an operator used to make the activity for which the rules are being built available a specific number of days after the activity named in the conditional expression has been completed.
is taken - an operator with similar functionality as the one above, except without a set time frame since the completion of the activity named in the conditional expression.
is not taken - an operator used to make the activity for which the rules are being built available only when the activity named in the conditional expression has not been completed.
is taken N times - an operator used to make the activity for which the rules are being built available only when the activity named in the conditional expression has been taken a certain number of times.
is taken less than N times - an operator used to make the activity for which the rules are being built available only when the activity named in the conditional expression has been taken less times than indicated.
is taken more than N times - an operator used to make the activity for which the rules are being built available only when the activity named in the conditional expression has been taken more times than indicated.
answer equals - an operator used to make the activity for which the rules are being built available only when a specific question of the activity included in the conditional expression equals a specific answer.
order starting from most recent - an operator used to include in conditions a specific submission in case an activity can be completed multiple times.
Condition operator answer equals
The condition operator answer equals allows the administrator to make a subsequent activity available if specific answers are given in a different activity that has been included in the conditional expression modified by this operator.
Dropdown and Radiogroup question types
Dropdown and Radiogroup question types are supported to be used with the operator answer equals to build conditions between activities.
Title values of the Dropdown, Radiogroup and Checkbox question types will be displayed in the fields "Question (Name)" and "Answer (Value)" of the Condition builder when selecting the operator "answer equals".
Checkbox question type
Checkbox question type is supported to be used with the operator answer equals to build conditions between activities. The following sub-group operators can be applied to build Checkbox question-based conditions:

is within group - use to make an activity available only if the participant's selection of answers fall within the answer group defined in the condition.
is not within group - use to make an activity available only if the participant's selection of answers does not fall within the answer group defined in the condition.
contains any of - use to make an activity available only if the participant's selection of answers contains any of the answers defined in the condition.
contains none of - use to make an activity available only if the participant's selection of answers contains none of the answers defined in the condition.
contains all of - use to make an activity available only if the participant's selection of answers contains all of the answers defined in the condition.
Our team is ready to provide you assistance in any of the steps and would gladly guide you through the process.

Do not hesitate to contact us via support@longenesis.com if you have any questions or any help is required.