Problem/Motivation

To be able to do much of anything useful with the tokens provided by tasks, we need entity tokens. We need them to create meaningful email messages like the following:

[gdpr_task:owner:field_first_name] [gdpr_task:owner:field_last_name]

A data request has been submitted to provide an export of your data. It is currently in [gdpr_task:status] status.

Visit <a href="[site:url]user/[gdpr_task:owner:uid]/gdpr/requests">My data requests</a> to see your exported data once it has been reviewed and processed.

Proposed resolution

Review it.

Remaining tasks

User interface changes

API changes

If someone is using the current tokens, this could cause issues as the previously named tokens now provide chained entities for the user relationships.

Data model changes

Release notes snippet

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

heddn created an issue. See original summary.

heddn’s picture

Status: Active » Needs review
FileSize
3.76 KB

Status: Needs review » Needs work

The last submitted patch, 2: 3026973.patch, failed testing. View results

lbesenyei’s picture

Thanks for the patch.

There is one part that needed to be changed.
Since we're using strings as status values the "entity_metadata_status_options_list" had to be replaced with a custom callback.

  • lbesenyei committed d62b653 on 7.x-1.x authored by heddn
    Issue #3026973 by heddn, lbesenyei: Full entity token support
    
lbesenyei’s picture

Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.