[SOLVED] Auto Actions - after field value change - what's the trigger?

Hi Kyle - I want to generate auto action (send email) after user saves value in checkbox:
[cb_bonus_prog_01] Equal to 1 / YES

What trigger should I select?
BTW, is there list of all triggers with some basic explanation of what they do?
Thanks!

OK - I dig that out: onAfterUserUpdate and onAfterUpdateUser - if I'm understanding it correctly those two triggers work when field is updated by user, the other when admin updates the user field. - tested and it worked.

Allright - this was fairly easy. How about this one:
user checks the box (value =1) => AFTER UPDATE (=> after saving the changes) the field EITHER is hidden from view, replaced by another (information - such as, 'step 1 completed'), or becomes read-only - whichever is easier/faster/safer to setup.

I'm not thinking here of a conditional visibility on the field - this would instantly hide the field after user checks the box, which might be confusing and cause that user do not click the update.
Thanks!

BTW, is there list of all triggers with some basic explanation of what they do?

No, not at this time. Each trigger trys to be self explanatory, but some of the legacy core triggers maybe a little vague. In your case you need the after user update and after update user triggers. We do have the below, but it's a little out of date.

www.joomlapolis.com/support/tutorials/120-api-usage/18358-using-cb-triggers

OK - I dig that out: onAfterUserUpdate and onAfterUpdateUser - if I'm understanding it correctly those two triggers work when field is updated by user, the other when admin updates the user field. - tested and it worked.

Yup, those are correct. On fires for backend and the other fires for frontend. Specifically as follows.

Backend: onAfterUpdateUser
Frontend: onAfterUserUpdate

user checks the box (value =1) => AFTER UPDATE (=> after saving the changes) the field EITHER is hidden from view, replaced by another (information - such as, 'step 1 completed'), or becomes read-only - whichever is easier/faster/safer to setup.

CB Conditional can do this.

I'm not thinking here of a conditional visibility on the field - this would instantly hide the field after user checks the box, which might be confusing and cause that user do not click the update.

You don't have to condition on profile edit. You can configure the condition to only apply to profile display.

CB Conditional can do this.

Yes, I played with that - as I have said - all looks good, however, from the UX perspective, if I hide the field before client has a chance to click the "update" it might be confusing and thus client might not click the "Update" - this is a speculation, but thought to address it and find a solution...

You don't have to condition on profile edit. You can configure the condition to only apply to profile display.

OK - perhaps you are answering it right here what I'm after above, but I'm not sure I quite understand...
Ideally I would like to see the field hidden when user RETURNS to the edit tab (after initially saving /updating the account) -and will notice a note instead of checkbox (or just no checkbox to simplify) - if I would to use CB Conditional I think you're talking about the "For... and then use Profile View" ... ?
From what you see in my explanation - is this more clear from initial description?

Ok, that's doable too. You're wanting a hard condition and not an ajax one. This is done as follows.

Condition
Display: Field conditional self
Field: Custom > Value
Value: [FIELD_NAME]
Translate Value: No
Operator: Equal To
Value: VALUE
Translate Value: No
Mode: Hide