Logic: Conditions

Conditions are the triggers that cause a rule to be fired which in turn will execute one or more steps.

In Sintel Forms, there are several conditions available that can be used to cause a rule to fire such as a field containing a specific value or a form being in a particular status. In addition, you can use the "Custom js function result check" step to create more complex conditions. Let's take a look at some of the available conditions:

  1. Form: field value check.

    To set this condition you need to define:

    Field - The field which value you want to check. The list contains all the fields defined for the form (not only added into the form)

    Operator - describe how you want to compare the value on the field. Different types of fields can have different operators.

    Value - describe the value you want to check.

      Note

    Condition values are case-sensitive!

    Example

    Form_field_value_check.gif

     

    Form_field_value_check_example.gif

     

  2. Form: related list items count check.

    To set this condition you need to define:

    Field - The field which you want to count. The list contains all the fields defined for the form (not only added into the form)

    Operator - describe on which terms you want to count field.

    Value - describe the natural number of the list items to which you want to compare.

    Example

    Form_related_list_items_conut_check.gif

     

    Form_related_list_items_conut_check_example.gif

     

  3. Form: mode check.

    To set this condition you need to define:

    Form mode - describe the desire form mode in which the steps will take actions.

     

      Note

    Form mode is not the same as workflow status! There are three form modes: create, view and edit.

    Example

    Formmode_check.gif

     

    Formmode_check_example.gif

     

  4. Form: author check

    This condition is by default set to check if the current user is an author of the item. You can negate this (the current user is NOT an author).

    Example

    Form_author_check.gif

     

    Form_author_check_example.gif

     

  5. Form: attachments check

    This condition gives you a possibility to check if the form has the attachment (default) or has not.

    Example

    Form_attachments_check.gif

     

    Form_attachments_check_example.gif

     

  6. User: anonymous access

    This condition gives you a possibility to check if the user is anonymous (default) or not.

    Example

    User_anonymous_access.gif

     

    User_anonymous_access_example.gif

     

  7. User: group membership (by name) check

    This condition gives you a possibility to check by the group name if the user is a member of the group (default) or not.

    Example

    User_group_membership__by_name__check_.gif

     

    User_group_membership__by_name__check_example.gif

     

  8. User: group membership (by id) check

    This condition gives you a possibility to check by the group id if the user is a member of the group (default) or not.

    Example

    User_group_membership__by_id__check.gif

     

    User_group_membership__by_id__check_example.gif

     

  9. Workflow: status check

    To set this condition you need to define:

    Operator - describe how you want to compare status value: should it be equal or not?

    Status - describe which status indicate steps. This is a list of every defined status (used or not)

    Example

    Workflow_status_check.gif

     

    Workflow_status_check_example.gif

     

 

Conditions can be either disabled or deleted if they are no longer needed and you can change their order using drag and drop.

 

Conditions_possibility.gif

 

For more advanced JavaScript conditions visit this article.

Was this article helpful?
0 out of 0 found this helpful