Explaining the "Conditions" Section Within Triggers

Chris Quiroz -

The "Conditions" section allows you to add prerequisites that must be met before the trigger will fire. Examples include having the application be in a certain round, having been ranked a certain score, or being part of a specific group.

 

Basic Conditions

Submission is in Stage: Selecting this condition will allow you to choose which stage the application should be in for the trigger to activate.

Is in Group: Selecting this condition will allow you to select the group the application or user should be a part of for the trigger to activate.

Submission has been Submitted: Selecting this condition allows you to determine if a submission should be submitted or not

Submission has completed task: Selecting this condition will specify which task should be completed before the trigger can be fired.

Date at time of trigger is: This condition will allow you to set a time this trigger should be fired. You can select After a certain date, Before a certain date, or On a certain date.

NOTE: This refers to 12AM UTC on the date set. Therefore After a Certain date, will start at 12AM on that day, and this would fire for any submissions on the date set as well. Before a certain date would fire up until 12AM on the date selected. On a certain date would be fire before 12AM to 11:59 PM on the date selected. 

Submission has completed stage: This condition allows you to select the round the submission should have completed previously in order for the trigger to take effect.

Task is pending: This condition allows you to select a task that has yet to be completed by the user in order for the trigger to activate. Typically used in conjunction with Recommender tasks or Payment Tasks.

Submission is in category: This condition allows you to select the category a submission should be in before the trigger activates.

Submission has been ranked: This condition allows you to indicate whether or not the submission should be ranked in order for the trigger to fire.

Provided rank is: This condition allows you to indicate the ranking that a submission should have in order for the trigger to fire. You can select whether you would like the ranking to be Less than, Equal to, or Greater than a certain number.

Has been ranked by X reviewers: This condition allows you to dictate the number of reviewers who need to rank a submission in order for this trigger to fire. You can select whether you would like the number of reviewers that need to rank the submission to be Less than, Equal to, or Greater than a certain number.

Has applied to award: This condition allows you to indicate that a submission must have applied to a certain award in order for the trigger to fire.

Remote URL call is equal to: This condition allows you to select what the remote URL call in a question or metatada field should equal in order for the trigger to activate.

Current user has completed ranking task for submission: This condition allows you to indicate that a specific ranking task has been completed before any action can be taken. The user in question depends on who the trigger is activated by. This is often useful if you have multiple reviewer tasks and would like a trigger to fire only when one of the tasks has been previously completed.

Submission is currently assigned to team: This condition allows you to indicate whether the submission has been assigned to a reviewer team within your site.

User has role: This condition is only useful if you have Manage Admins enable on your site and can assign roles to your administrators. It is useful for applying conditions based on what role the admin has on your site.

Number of Installments in transaction is: This condition is used within an awards site, so the trigger will only fire when the number of installments is Less than, Equal to, or Greater than a certain number.

Submission is for award in category: This condition will allow you to select an Award Category that the submission is in, in order for the trigger to fire.

Note: Award Categories are different than Submission Categories

Submission was created via auto-apply: This condition allows you to select whether or not the submission needs to have been created via auto-apply in order for the trigger to fire.

 

Form Responses

These conditions will be specific to your site and the forms and questions that you have built. These conditions allows you to select a question from a form, and indicate what the response should be in order for the condition to fire, or not fire. For example, if the response to a certain questions is “YES”, then the trigger would fire.

 

Metadata

Under this head are sub-headings for Award Fields, Submission Fields and User FIelds. Conditions under these sub-headings will only be available if metadata has been added to your site. You can view more information about Metadata here: Understanding Metadata. These conditions will be specific to the metadata within your site.

 

Ranking Information

Under this heading are three sub-heading allowing you to create a condition based on the Average Rank, Cumulative Rank. or Standard Deviation. By clicking on each subheading you are then given the option to narrow it down based on the ranking of (All Tasks) or specific review tasks within your site.

Average rank: These conditions allows you to indicate the average ranking that a submission should have in order for the trigger to fire. This can be based on a single review task or can take the average based on all review tasks in your workflow. You can select whether you would like the ranking to be Less than, Equal to, or Greater than a certain number.

Cumulative rank: This condition allows you to dictate what the cumulative ranking for the submission should be in order for the trigger to activate. This can be based on a single review task or can take the average based on all review tasks in your workflow. You can select whether you would like the ranking to be Less than, Equal to, or Greater than a certain number.  

Standard deviation: This condition allows you to indicate the standard deviation that a submission should have in order for the trigger to fire. This can be based on a single review task or can take the average based on all review tasks in your workflow. You can select whether you would like the ranking to be Less than, Equal to, or Greater than a certain number.

 

Recommender Responses

Similar to the Form Responses, these are specific to your site and allow you to apply conditions based on responses that Recommenders have given to the Recommendation forms. These conditions allows you to select a question from a form, and indicate what the response should be in order for the condition to fire, or not fire. For example, if the response to a certain questions is “YES”, then the trigger would fire.

 

Reviewer Responses

Similar to the Form Responses, these are specific to your site and allow you to apply conditions based on responses what Reviewers have given to the Reviewer forms. These conditions allows you to select a question from a form, and indicate what the response should be in order for the condition to fire, or not fire. For example, if the response to a certain questions is “YES”, then the trigger would fire.



Have more questions? Submit a request

0 Comments

Article is closed for comments.