Rules Integration for Registration Type and Tokens

Hi,

Since tokens are not available, does that mean using a hook_form_alter() would be the best way to pre-fill the forms with default values?

Thanks.

Would love to see a full support of tokens by this module. Unfortunately I am missing the entity title tremendously.

Even a workaround with a Computed Field and the page title does not work for me, because the registration should be safed on an extern page (node/*/register) which always has the same title ("Registration"). :(

This helped me a bit... http://drupal.stackexchange.com/questions/69050/registration-module-rule...

thanks for the link maerys ..trying to figure out how to send a meaningful email on submission of a registration.. following..

Having a hard time using the node title , body of the content type (event) that has the registration field..
I've been trying to drill down and pull out the content w rules using the stackexchange recomendations above..but no luck.. its real opaque..
even view.. hard to connect the content / event to the registration to show a list of events they are registered for.. not their particular registration details..
still working at this.
thx

I'm with you @jackhutton - By fetching a linked entity (ie, the Event node), I can only access the values of the following fields:

• Node Title
• Node URL
• Fixed Length Text fields
• Taxonomy References

Where Rules is struggling is getting values of long text fields (ie, ones that can have a text filter applied to it, and are rendered in forms as TEXTAREAs)

Bit more testing finds that I can't handle text fields that have a filter format (eg 'Filtered HTML') applied to them. Also fields like Dates, Addressfield etc can't be used successfully as tokens in Rules actions (for building messages, emails etc).

(The pedant in me couldn't hold back from deleting the random apostrophe in the issue title)

I followed the settings proposed on #6 and managed to create a rule to send an html e-mail with the event title as subject without problems.

Events: after saving a new registration

Conditions: Text comparison - Text [registration:state:label], Matching text: Active (also used for Wait list to send an e-mail for people that are placed on the waiting list; you can also use variables other than label, for example machine name or id)

Action 1: Fetch entity by id - Parameter: Entity type: Node, Identifier: [registration:entity-id]

Action 2: Parameter: Key: registration_notification_mail, To: [registration:mail], Subject: You are registered to [registration:entity:title]

I think comment #10 goes out of the scope of this issue, so marking as closed.

Phew... you guys saved my day, thank you so much:-)

Thank you guys for this module, it really helps my job!. and this thread was helpful:)