collective.contentrules.mailfromfield 0.1.0

How it take the email data

First of all you must choose the type of target element.

If you choose to keep default “From trigger object” option, the data is read from the section you have activated the rule on.

Example: if you activated the rule on a folder called section and the rule will raise event when working on a document called foo (like: modifying the document), the e-mail address will be taken from the folder.

Changing to “From event target” will change the behavior, trying to get e-mail data from the same attribute but looking for it on the object that raised the event.

In the example above: we will look for the value from the document.

What it try to read

The rule try to get from the object:

• an attribute of the given name

• a callable method from the given name

• an Archetypes field with given id

• a ZMI property with given id

The rule try to read, one after one, all this data. The first match found will be the one used; if not one give results, no e-mail is sent at all.

Message markers

Marker labels that follow can be used in the message text and subject.

${title}

The title of the content that triggered the event (foo title in our example)

${url}

The URL of the content that triggered the event (foo URL in our example)

${section_name}

The title of the folder where the rule is activated on (section title in our example)

${section_url}

The URL of the folder where the rule is activated on (section URL in our example)

A real Plone use case

A Plone site use Signup Sheet for manage internal training session. The form fieldset is customized as normal, but one of the field is director_email.

The scope there is that this e-mail address is notified when a user subscribe and the user itself put there the e-mail address of the proper director.

To reach this we need to:

• create a new rule triggered on “Object added to this container”

• add a filter condition based on content type Registrant

• add an action using the “Send email to address taken from the content”

• specify in the action the SignupSheet field with the director email

• specify in the action that we want to take the email from the target object (the Registrant itself)