User interface for sending messages to lists of users in a View requires steps that can confuse users.

Given a View with many fields that are irrelevant to sending an email, configuring the email takes too many steps, and can be confusing to users.

EX: I have a View of OG members that a group manager uses as a dashboard. Things like profile2 fields, user points, group membership status are fields in the View. When the manager selects a row to send an email, the form displays two select boxes, one for selecting a field for selecting the Recipient's name, one for selecting the email. In my example, there are approximately twenty fields the manager must scroll through to find the appropriate fields. Additionally, the field names are visible along with the labels, and any fields without labels only show the field name. Setting an Administrative Title on the field does not change this.

Assume a case where a View contains profile2 field, field_preferred_contact_email, and mail. The user may not know which field to select.

Finally, fields configured to not be displayed are visible in the Recipient select boxes.

Feature Request:

Allow for the View to be configured to set the appropriate fields on the View itself, rather than expect the end-user to select the correct fields. Potentially in the Global:E-mail field configuration form, add the ability to set tokens for the Recipient name and email in the View. This should include setting tokens for fields in the view but are not displayed.

Thoughts?

Comments

scottsawyer’s picture

NOTE: Includes potentially duplicate requests from

hansfn’s picture

Many good points here.

As you have seen in your list of potentially duplicate requests, I have recommended using custom modules to alter the Views Send form many times. However, you mention two things that definitely could be improved:

1) Fields that don't display in the view, shouldn't be listed (in the dropdown or as tokens).
2) Fields that doesn't contain email addresses shouldn't be available in the Recipient dropdown.

Patches are welcome. If I have time, I'll do 1) in the near future ;-)

zulfierken’s picture

I am also waiting for that near future :)

Why do not you add these fields into the global e-mail field.

I will simply choose:

Sender's name; use a field from row
sender's email use from row field
receipent e-mail data from row etc,.

Replacement patterns can be used when e-mail field is added.

Views Php can be used to create sender name and email dynamically for the rows.

I simply do not want people to send e-mails with using different e-mail adresses.

hansfn’s picture

Status: Active » Closed (won't fix)

Sorry, but I don't see that I will have time to fix any D7 issues.