Actions
Feature proposal #4261
closed
Implement better user object searching
Description
It checks each variable to see if it's a CB user object, if it's a user id, etc.. it should first check if any of the variables are a user object. If none are it should then try to parse IDs. Current implementation causes issues trying to find the user object for multiple GJ triggers.
Updated by krileon about 11 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
It will now do 2 passes. First pass specifically tries to find a CB user object. If it fails to find one it'll parse each variable for one.
Actions