Webform > E-mails: Add "Content values" (ie: node field) support

Or simply to update the documentation:

To supply a content value, create a new hidden value component that uses the token value [xxx] as the components default value, and then assign this new component as an email source under the emails tab.

Zero new code, and it appears to work in theory. I run some live tests to see if it works.

I''ll confirm tonight, and if issues report back, otherwise I'll write up some notes and run them past you before posting on to the documentation pages. Maybe it would be worth a section on contrib modules that assist automatic creation of webforms, there were so many issues in the queue about that :)

I'll see how my time goes....

OK, mixed results. Testing on a production site with the following relevant modules:
Entity API
Entity tokens (Entity API)
Token

When using a Text field, both available tokens worked without issue.
[node:field-staff-contact] - from Entity Token module (I think. It had a str_replace('_', '-', $name) while Token didn't)
[node:field_staff_contact] - from Token module

Using an Email field from the Email module, the underscore version of the field token did not work. The hyphened version did work.

[node:field-staff-contact] - worked
[node:field_staff_contact] - failed

With that in mind, maybe doco would be:

Using node and field data in 4.x with tokens

With the introduction of token support in Webform 4.x, it is now possible to integrate content from the node with the webform without any programming.

The first thing to note is that not all tokens are the same and they may return different values. There are three main providers of tokens in most installations:

• Drupal - provides a finite set of tokens
• Token - extends the core set of tokens, including some field tokens, and provides the UI for adding tokens.
• Entity Tokens (included with Entity API). Provides additional field tokens.

Adding a new e-mail recipient to webform submissions from a field

When you have webforms being automatically generated via code, or the contrib modules; Node Clone, Webform Share or Webform Default Fields, it is possible to set an email recipient from a node field. This means that the website administrator or content author does not need to edit the webform section.

These are the steps required to achieve this:

1. Create the field
   Edit the content type that the node is attached to and add a new Text or Email field. Note: If you are using the Email module, you will require the Entity Tokens module.
2. Hide the node from display
   Since most users will not want to display the field, update the content types display settings to set this field as hidden.
3. Add a new Hidden component
   
   

   Label, Field Key

   These are for admins, enter short descriptive values.

   Default value

   This is the field where you add the token to pull information from the container node. These follow the pattern:
   
   [node:field_YOUR_FIELD_NAME] (Token module) and / or [node:field-YOUR-FIELD-NAME] (Entity Tokens).
   
   If you are using a Text field, use either tokens provided by either Token or Entity Tokens module.
   
   Initial tests using the Email module showed that the Token modules field token failed. So you would need to install the Entity Tokens module and use it's tokens (the hyphened token).

   Display > Hidden Type

   To keep the email secure from web scrappers, you should select the Secure value option. These are never sent to the client.

   Token values

   If you have the Token module enabled, this fieldset contains a handy reference of the available tokens. Clicking any of the tokens will automatically populate the Default value field.

4. Add an Email recipient
   After saving the new component, visit the emails tab. Select the newly created component from the "Component value" select list and select add.

From memory reading the relevant threads from 6 months back, Token uses the default formatter so that would be a "Won't fix" in relation to the Token display.

But I shall play with this and update according, or maybe not mention Email module integration.

The token tree that is generated on this site was over 5MB last time I checked, but sadly we needed the chained entity tokens. :(

We have actually written a custom page callback that displays the token tree and have themed the token tree display to show a link to this page instead.

Excludes Entity Tokens (well just a brief mention). As before, you mentioned a common use case is to use a global webform and the current node. AKAIK, this is not available yet, e.g. #919760: Add a [current-page:object:?] dynamic token

Revised doco with images :)

Using node and field data in 4.x with tokens

With the introduction of token support in Webform 4.x, it is now possible to integrate content from the node with the webform without any programming.

Drupal provides many basic tokens, but you will need the Token module to provide an UI and basic field tokens.

The field tokens provided by the Token module are rendered by a special view mode called "Token". By default this new view mode this is not enabled and the rendered token is generated using the settings from the main default full view mode. To change this behavior, edit the content type that the webform is attached to and edit the default view mode. Under Additional view modes, ensure that Tokens is checked and save. After saving this page, a new tab will appear and this will define how the tokens are rendered. The image below shows what the page will look like after enabling the Token view mode.

Examples

• Sending emails to an email address set on the webform

Sending emails to an email address set on the webform

It is possible to set an email recipient from a node field. This means that the website administrator or content author does not need to edit the webform section to set the email recipient after the form is set up.

These are the steps required to achieve this:

1. Create the field
   Edit the content type that the node is attached to and add a new Text or Email field.
2. Hide the field
   Edit the content type settings to ensure that the field is hidden when viewing the node.
3. Set the display mode to plain text
   The email field is normally rendered as a link. This needs to be rendered using the display formatter "Email plain text". So enable the Tokens view mode and edit this to set the formatter to "Email plain text".
4. Add a new Hidden component
   
   

   Label, Field Key

   These are for admins, enter short descriptive values.

   Default value

   This is the field where you add the token to pull information from the container node. These follow the pattern:
   
   [node:field_YOUR_FIELD_NAME] (Token module)

   Display > Hidden Type

   To keep the email secure from web scrappers, you should select the Secure value option. These are never sent to the client.

   Token values

   If you have the Token module enabled, this fieldset contains a handy reference of the available tokens. Clicking any of the tokens will automatically populate the Default value field.

   Your webform component list will look something like this once you have added the component.
   

5. Add an Email recipient
   After saving the new component, visit the emails tab. Select the newly created component from the "Component value" select list and select add. The final results will look similar to this.
   

The Entity Tokens module (included with Entity API) provides 100's of additional field tokens, but it can have a significant impact on performance and can potentially break your site as it consumes available resources. Entity Tokens differ from the Token modules tokens in that they use a hyphen rather than an underscore in the token name. i.e. [node:field-YOUR-FIELD-NAME].

Added - http://drupal.org/node/1760332

@sircosta I would post a critical issue report with complete error details (steps to replicate and error message in full / backtrace if available) in that modules queue if there is not one already