I was working on a new workflow rule and when I came to the 'Update Field' action, I noticed that one of the linked field sets was 'Email Fields'. This piqued my interest because I am trying to figure a way to send an email notification to the PM if an email reply comes in from a (non-license) customer.
However, if I try to use a 'Conditional Action' or an IF function in a 'send email' action (on, for example, AttachedEmails.Subject)...
- In the case of the Conditional Action, the Email Fields link is not available
- In the case of an IF function, Check Syntax tells you that the $AttachedEmails.Subject field is not a valid field.
So this got me wondering:
a. What is the 'Clarizen Official Use Case' for updating fields on an email attached to the project?
b. Wouldn't there be more use for access to those fields for filtering workflow rules? For example"
- If(IsChanged($EmailsCount)) on the WFR trigger filter
- (contains('RE:',AttachedEmails.Subject)) on a Conditional Action OR
- not(contains($ProjectManager,$AttachedEmails.From))
Seems like access to these fields for filtering purposes would help solve the issue of Clarizen not notifying PMs when rule-triggered emails receive replies.
Please sign in to leave a comment.
a.) I'm not sure if there is a standard use case for editing fields on emails that have already been attached to a project (or any other object for that matter)
b.) Interesting use case, this would be where the feature request comes in.
Thanks Josh. Any chance we can get that feature request (ability to query Email Fields field set in workflow rules) logged... if you didn't already?