TeamDesk Knowledge Base & Support

Philipp Matuschka (MMB) 2/19/2019 3:31:38 AM

Hi Jeff

I had been doing some thinking about this in the background as well and have not come up with an answer yet. However I have not made any real effort to solve it yet. I would be interested to see what solutions are suggested by the TeamDesk guys.

Philipp

Slava Shinderov  Staff  2/19/2019 4:38:16 AM

@Jeff I guess, you've "User Property" table with "Low Priority Notification" checkbox in it.
If so, simple include check for "Low Priority Notification" into your email notification filter condition.
System will check condition for each user under manager role individually.

Jeff Zortman 2/19/2019 8:31:52 AM

@Slava Yes, So if the Email Notification "To" field is set to a role, it iterates one-by-one through each user of that role using the specified custom formula filter. Then I can use "User[Low Priority Notification]" in the filtering. Table record access is applied as defined. All correct?

How does it handle a [User] in the custom formula filtering when the "To:" is a column that contains an email address instead of a user? Null user?

Slava Shinderov  Staff  2/19/2019 8:41:08 AM

> Yes, So if the Email Notification "To" field is set to a role, it iterates one-by-one through each user of that role using the specified custom formula filter. Then I can use "User[Low Priority Notification]" in the filtering. Table record access is applied as defined. All correct?

Yes.

> How does it handle a [User] in the custom formula filtering when the "To:" is a column that contains an email address instead of a user? Null user?

If you're sending to the email address instead of a user then it's executed under database owner user.

Jeff Zortman 2/19/2019 10:51:37 AM

I tested this a few different ways and I really believe that the "User" in the Email Notification custom filter is referring to the User that is creating/modifying/deleting the record, not the User that the email is potentially being sent to. Is there different syntax for the User that is being referred to in the potential email?

Slava Shinderov  Staff  2/20/2019 5:47:16 AM

@Jeff it looks like I've misleaded you.
Trigger filter condition is checked once.
As a workaround, please consider creating many-to-many relation between "Issue" and "User Property" table and crete a summary concatenate column on user email address to create a list of users to notify.
After that, wrap that newly created summary with help of Formula-Email column and use it for your notification.

Jeff Zortman 11/22/2019 7:56:57 AM

@Slava Using the many-to-many relationship introduces a problem for me. It creates a tab at the bottom of each table's view which I don't want to display to users. Any suggestions on hiding the tab?

I propose that the system allow the option of trigger filter conditions evaluating for each iteration of Users. Maybe it would be a check box in the email notification setup to use this method?

Right now I have users that are getting so many email notifications that they ignore them. Allowing them to unsubscribe from certain lower priority ones would be helpful.

Seems like I have run across a similar issue with email reminders and subscriptions that could potentially be solved by checking the User for each trigger filter condition iteration.

Slava Shinderov  Staff  11/22/2019 8:12:43 AM

@Jeff please open support questions and provide an URL to the relation you're talking about.

MYCS Support 12/4/2019 4:08:20 AM

Hi Jeff, not if this has been solved for you but you should be able to remove the default view that is automatically set when the relationship was created under manage relations. Set the details view to none on both sides of the relationship

I assume this may have been advised via support.
Dave