Feature proposal #3158
closed
Implement parsing of other trigger variables into substitutions
Description
Currently only the user object is found and processed allowing substitutions just from that user object. Ideally all variables sent back from the trigger should be parsed into substitutions so can be used in the actions as well as conditions. For example [var1] or if is array/object {var1[variable]}.
Updated by krileon about 12 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Implemented as [var1], [var2], etc.. for non-array and non-object variables. Arrays and Objects are parsed into an array and stored as [var1_VARIBLE] (e.g. [var1_name], [var1_username]). This gives full access to all the variables a trigger provides. They're cleaned for vulnerabilities and passed as extra substitutions. They straight variable, array, object substitutions however and do not allow for the extra features the primary user object provides ([username], etc.. will always be of the "User").
Updated by krileon about 12 years ago
- Status changed from Resolved to Closed
Added usage info to User parameter description.