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.

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.

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.