Skip to Content Skip to Menu

🎃 Happy Halloween! Treat yourself with an awesome discount on memberships! Get 20% off now with code SPOOKY-2024!

CB Auto Actions Trigger Explanation

8 years 2 months ago #284813 by Intellitech
Replied by Intellitech on topic CB Auto Actions Trigger Explanation

krileon wrote:

Does this mean that, even if I do not use the "onAfterUserApproval" from in Auto Actions, the Welcome email set in the Configuration will default be the one that will be sent. I'd just want the email to be sent after user has been set to Approved to send the Welcome email to let them know they can access the site.

The Welcome email already does this. I see no reason to try replacing it with CB Auto Actions usage.

Trigger when an update is done to their profile.

You'd just act on onAfterUserUpdate with an Email action then.

Ok, scenario is this - if users are in membership category "X", they are eligible to complete other fields [configured using tab conditionals] in the profile to be on a panel. Their "application" to this panel is subject to approval. Only when the admin indicates their appointment (using a selection field criteria) to the panel, then this email informing them of their appointment will be sent. Reason that we are using the tab conditions to add the extra fields to capture this "second" application in the Profile Update, is because we require the existing information to access if the user is eligible to be appointed. in this case, should the Trigger be onAfterUpdateUser?

Ok, so you've a field you set as an administrator to approve the application. In that case you'd act on onAfterUserUpdate and condition against that field in an Email action. If you're doing this from backend you need to use onAfterUpdateUser (or both if you want to support both locations).

Basically I'm looking from the perspective of the Admin user end - which triggers to set when from the user details are being Saved from the Backend.
And also from the Front user end - which triggers to set when the user updates from the front.

Frontend = onAfterUserUpdate
Backend = onAfterUpdateUser

Their location somewhat noticeable due to their wording "After User Update" and "After Update User". They key change being User and Update swap changing their meaning significantly.

I believe in the previous version, the Triggers were broken into Frontend and Admin Backend for selection. The newer version does not quite identify which trigger is executed if from the Frontend or Backend.

Correct, that's now gone and no plans to return. I encourage everyone to simply learn the triggers if you intend to use CB Auto Actions extensively. Most are obvious, but some of the older triggers maybe a little confusing about their usage or location. Newer triggers will always be clear as to what they're doing and where.


Thanks krileon. So far so good. Triggers set have been working.

Please Log in or Create an account to join the conversation.

8 years 2 months ago #284824 by Intellitech
Replied by Intellitech on topic CB Auto Actions Trigger Explanation
I got to ask this -

Ok, so you've a field you set as an administrator to approve the application. In that case you'd act on onAfterUserUpdate and condition against that field in an Email action. If you're doing this from backend you need to use onAfterUpdateUser (or both if you want to support both locations).

Is there a way to have the notifications triggered only one time, based on that field administrator approves? This particular email CANNOT CONSTANTLY fire whenever there is an update to the profile. We just require it to fire ONCE time. how do we limit to that first time after approving the field? Is there a solution to this?

Intellitech wrote:

krileon wrote:

Does this mean that, even if I do not use the "onAfterUserApproval" from in Auto Actions, the Welcome email set in the Configuration will default be the one that will be sent. I'd just want the email to be sent after user has been set to Approved to send the Welcome email to let them know they can access the site.

The Welcome email already does this. I see no reason to try replacing it with CB Auto Actions usage.

Trigger when an update is done to their profile.

You'd just act on onAfterUserUpdate with an Email action then.

Ok, scenario is this - if users are in membership category "X", they are eligible to complete other fields [configured using tab conditionals] in the profile to be on a panel. Their "application" to this panel is subject to approval. Only when the admin indicates their appointment (using a selection field criteria) to the panel, then this email informing them of their appointment will be sent. Reason that we are using the tab conditions to add the extra fields to capture this "second" application in the Profile Update, is because we require the existing information to access if the user is eligible to be appointed. in this case, should the Trigger be onAfterUpdateUser?

Ok, so you've a field you set as an administrator to approve the application. In that case you'd act on onAfterUserUpdate and condition against that field in an Email action. If you're doing this from backend you need to use onAfterUpdateUser (or both if you want to support both locations).

Basically I'm looking from the perspective of the Admin user end - which triggers to set when from the user details are being Saved from the Backend.
And also from the Front user end - which triggers to set when the user updates from the front.

Frontend = onAfterUserUpdate
Backend = onAfterUpdateUser

Their location somewhat noticeable due to their wording "After User Update" and "After Update User". They key change being User and Update swap changing their meaning significantly.

I believe in the previous version, the Triggers were broken into Frontend and Admin Backend for selection. The newer version does not quite identify which trigger is executed if from the Frontend or Backend.

Correct, that's now gone and no plans to return. I encourage everyone to simply learn the triggers if you intend to use CB Auto Actions extensively. Most are obvious, but some of the older triggers maybe a little confusing about their usage or location. Newer triggers will always be clear as to what they're doing and where.


Thanks krileon. So far so good. Triggers set have been working.

Please Log in or Create an account to join the conversation.

  • krileon
  • krileon
  • ONLINE
  • Posts: 48457
  • Thanks: 8280
  • Karma: 1443
8 years 2 months ago #284844 by krileon
Replied by krileon on topic CB Auto Actions Trigger Explanation

Is there a way to have the notifications triggered only one time, based on that field administrator approves? This particular email CANNOT CONSTANTLY fire whenever there is an update to the profile. We just require it to fire ONCE time. how do we limit to that first time after approving the field? Is there a solution to this?

How are you keeping track of approved profiles? If you've another field to check against then you'd just condition against it. Aside from that I've no idea as you'll need something to condition against to state that it's already approved.


Kyle (Krileon)
Community Builder Team Member
Before posting on forums: Read FAQ thoroughly + Read our Documentation + Search the forums
CB links: Documentation - Localization - CB Quickstart - CB Paid Subscriptions - Add-Ons - Forge
--
If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
--
If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please send me a private message with your thread and will reply when possible!
--
Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
--
My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.

Please Log in or Create an account to join the conversation.

Moderators: beatnantkrileon
Powered by Kunena Forum