Workflows: Add Actions for the Trigger Contact Field Updated
B
Bernardo Gonzalez
Add actions "Contact field is added" and "Contact field is removed" to work similar to the Step "Contact Tag Updated"
This way we can create a Workflow that starts with "Contact Field A is Added" and add a Step "Remove Field A Value" without generating a loop.
We should also consider adding a "Source" Trigger Filter, so that we only run the Workflow if the change of custom field came from a specific source. e.g. only Trigger if the field was changed manually by a user.
N
Nabilah Binti Salleh
open
K
Kcfreedomagency Kcfreedomagency
That would be very important
Jerry (CEO)
Merged in a post:
Different triggers for two kinds of ASSIGNEE change
J
John Buckman
Currently, the assignee can change using two ways:
1) USER X uses the drop-down to assign a contact to USER Y
2) or USER Y replies to a contact, in which case the assignee changes automatically
I'd like to be able to use different triggers for each type of assignee change.
Why?
Because in case #1, User Y is not necessarily going to reply right away, and so a system message like "USER X HAS ASSIGNED YOU TO USER Y" is appropriate.
In case #2, the reply goes out first, then trigger fires. In this case, the system message should be "YOU ARE NOW TALKING TO USER Y"