Explaining the "Activation" Section Within Triggers

Chris Quiroz -

The "Activation" section allows you to select the action that will activate the trigger and set it in motion. There are many options to select from:

 

General Workflow Related Activations

Submissions: An application has been promoted to a new stage: When an application moves to another round, the trigger will activate. This activation is typically used with a condition stating which stage the submission is in. This is if you would like to specify which stage the task is promoted to in order to activate the trigger.

Submissions: An application has been submitted: When an applicant completes the “Submit” task, the trigger will activate.

Submissions: An application has been withdrawn: When a user withdraws an application, the trigger will activate.

Submissions: A submission has been created: When a new submission is created, the trigger will activate. This trigger can be useful if you have other triggers setup to automatically create submissions.

Submissions: On a specific date: This trigger will activate on the date specified at 7:30AM EST.

Note: If you are planning for the trigger to fire on the same day you are creating it then you will need to ensure that you are creating the trigger prior to this time otherwise the trigger will not fire.

Submissions: A submission has been created from archived data: When Data Re-Use is enabled on the site and a submission has been created from archived data (a submission from a previous application), the trigger will activate. For more information on Data Re-Use please see, Submissions Tab (link)

 

User Related Activations

User: A user has registered: When a user registers a new account within your site, the trigger will activate.

Users: A user has created a submission: When a user creates a new submission, the trigger will activate. This trigger activation is often used alongside a condition for which group the user is in. 

Submissions: A submission has been created: the submission will need to be created manually in order for the trigger to activate.

Users: An admin has added a user: When an admin adds a new user to the site, the trigger will activate.

Users: A member has been added to a submission: When a member has been added to a submission, the trigger will activate.

User: A user has been added to a group: When a user has been added to a group, the trigger will fire. This activation is usually used in conjunction with the condition, User is in group as a way of specifying which group the user is added to in order to fire the trigger.

 

User Task Completion Activations

User: A task has been completed: This trigger will fire when a User Task is first completed. If you are using this activation once the task has been completed once it will not fire again when the task is edited.

User: A task has been edited: When a previously completed User Task has been edited and saved, the trigger will activate.

User: A task has been edited OR completed: This trigger will first fire when the User Task is initially completed as well as any time it is edited and saved after initial completion. This is useful if you require the trigger to activate whenever the User Task form is saved.

 

Task Completion Activations

Submissions: A task has been completed: This trigger will fire when a task is first completed. If you are using this activation once the task has been completed once it will not fire again when the task is edited.

Submissions: A task has been edited: When a previously completed task has been edited and saved, the trigger will activate.

Submissions: A task has been edited OR completed: This trigger will first fire when the task is initially completed as well as any time it is edited and saved after initial completion. This is useful if you require the trigger to activate whenever the form is saved.

Submissions: A task has been started: When a user clicks to Start a task, the trigger will activate.

Submissions: A task has been started or edited: This trigger will fire when the task is initially started as well as when the task is edited and saved after completion.

Submissions: An attachment has been uploaded: When an attachment has been uploaded to a user's profile, the trigger will activate.

Submissions: An attachment has been edited: When an attachment is edited, the trigger will activate.

 

Reviewer Related Activations

Submissions: A submission has been ranked: When a reviewer has completed a ranking task for a submission, the trigger will activate.

Submissions: A reviewer has completed their rankings: When a reviewer has completed all of the ranking tasks for all submissions assigned to them, the trigger will activate.

Submissions: A reviewer has been assigned to a submission: This trigger will activate whenever a submission is assigned to a reviewer through Manual Assignments or assignments through triggers. For more information on assigning submissions to reviewers you can go to Assigning Applications to Reviewers (link)

Submissions: A reviewer has submitted their rankings: This trigger is used when “Enable ‘Submit’ Button” is enabled under the Behaviour tab of a reviewer task, this is typically used in conjunction with “Render Inline”. Therefore when the review task is submitted, this trigger will fire.

 

Award Related Activations

Submissions: An award has been applied to: When a user has finished the application process for an award, the trigger will activate.

Submissions: Has begun an application process to an award: When a user has begun the application process to an award, the trigger will activate.

Submissions: Award transaction has been created: Within an awards site, this trigger is fired when a transaction has been created and saved in the Manage Awards > Distribute > Submissions section of the site.

Submissions: Award transaction status has been changed: Within an awards site, this trigger is fired when the status of the award transaction has been changed in the Manage Awards> Distribute > Transactions section of the site.

Submissions: Award transaction has been approved: Within an awards site, this trigger is fired when an award transaction has been approved in the Manage Awards> Distribute > Transactions section of the site.

Submissions: Award transaction has been cancelled:  Within an awards site, this trigger is fired when an award transaction has been cancelled in the Manage Awards> Distribute > Transactions section of the site.

Submissions: Award submission has been rejected: Within an awards site, this trigger is fired when the award submission has been rejected in the Manage Awards > Distribute > Submissions section of the site.

Submissions: Award transaction payment was completed: Within an awards site, this trigger is fired when an award transaction has been completed in the Manage Awards> Distribute > Transactions section of the site.

Submissions: Award transaction has been rejected: Within an awards site, this trigger is fired when an award transaction has been rejected in the Manage Awards> Distribute > Transactions section of the site.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.