Managing Triggers for Forms, Autobill, and Emails

triggers are a powerful tool in your project that allow you to automate actions based on user behavior and system data creating, editing, and reviewing triggers is the same process across all modules forms (including fields) https //help regpack com/product triggers autobill emails you'll only need to learn how to work with triggers in one module, and once you've learned, you'll know how to work with triggers everywhere this guide will walk you through the process of setting up, reviewing, and managing triggers effectively what can triggers do? triggers can be set to take actions based on the following elements in regpack system registration if any account is created in your system as well as the creation of a sub unit account if you're using a group or family system you can also trigger on sub unit login if that function is enabled payments if the user has indicated they'll send a manual payment, the user's balanced has closed and no longer has a balance due, as well as the different payment statuses approved, refunded, pending, chargeback, and under review statuses assigned all of the custom statuses that are created and managed in user management assigning a status will cause a triggered event products all of the products that are created and managed in product management and will trigger an event if the product is added to cart, deleted from cart, waitlisted, and paid for forms all of the forms that are created in your system will be listed and can trigger an event if the form is added, deleted, set to incomplete, submitted, completed, locked fields all of the responses to multiple choice fields, and designated short answer fields, that you’ve added in your system if a user, or an admin in the back end, selects the response it will cause a triggered event how to set up a trigger locate the trigger option for forms, fields, products, emails, or autobill plans, look for the white lightning icon or the trigger button when hovered over an element define trigger action define what should happen when the criteria are met for example if it's a product or autobill plan should it add or show to your audience if it's an email who are the recipients, adding cc'd or bcc'd recipients, selecting which admin the email is sending from, and if it should send only once if it's a field or form it can only add to their registration and it's visibility is controlled by designating if a field or form is admin only set the criteria once the action is defined, a menu will open where you can specify the conditions for the trigger for example trigger an action when a user selects a specific product send an email once a payment is made display a new form after a specific status is assigned define if it's "and" or "or" by choosing all conditions are required every condition must be achieved for the triggered element to react choosing any conditions are required any of the selected conditions will cause the triggered element to react save the trigger once the criteria and actions are defined, click save the white lightning icon will turn purple , indicating that a trigger is now active for that item how to review triggers to review an existing trigger click the purple lightning icon locate the module (form, field, product, etc ) with the trigger you want to review click the purple lightning icon to open the trigger details view trigger settings the settings box will show the criteria and actions defined for the trigger this helps ensure everything is functioning as intended how to edit or delete a trigger open the trigger settings click the purple lightning icon associated with the trigger you want to modify edit the trigger adjust the criteria or actions as needed if you'd are adjusting any email related trigger elements, such as recipients of an email or a cc'd/bbc'd email, they will not send retroactively and will only affect future attempts if you are adjusting criteria on products, autobill, forms, or fields when saving the system will confirm if you'd like to update the action for existing users the system will find and force an update for any users that this new criteria applies to, including removing or hiding any products, autobill, forms, or fields from their application do not update existing users this can effect users retroactively if they manually go through the registration again and re submit the forms, but the system won't find and force an update on their application delete the trigger if the trigger is no longer needed, click the delete option the icon will revert to white, indicating no active trigger best practices for triggers start simple begin with basic triggers and test their functionality before creating complex workflows test thoroughly use a test user account to ensure triggers fire as expected and the correct actions occur review regularly periodically check triggers to ensure they align with current project needs and adjust as necessary by leveraging triggers, you can automate workflows, improve efficiency, and create a seamless user experience with a consistent ui and straightforward setup process, managing triggers for forms, fields, products, autobill plans, and emails is easier than ever