Feature proposal #6514
closed
Implement optionally firing of profile update triggers in a field action
Added by krileon over 7 years ago.
Updated about 7 years ago.
Start date:
20 February 2017
Description
Currently a field action directly queries then updates the user object. It ideally should have a parameter to specify if triggers should also fire, but due to existing usages should be disabled by default.
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Parameter implemented to toggle Save Directly Enabled/Disabled. Default Enabled, which matches current behavior. If disabled it'll use APIs to save and result in triggers firing.
- Status changed from Resolved to Closed
Also available in: Atom
PDF