Use of {} not best practice when using Send email in work flow
We have created a form that captures a persons details for attending an event (name, email, telephone, etc).
If a different person is paying for the attending spot then we capture the billing details also (name, email, telephone, etc).
For the person attending the input field (short text) is called Email, with the alias of this field being email.
For the billing information the input field (short text) is called Email, with the alias of this field being billingemail- note: the billing information is inside a seperate group called Billing information, hence why the field is just called Email.
In our workflow we have chosen the send email option and set the Email (Enter the receiver email) field to be {email}
As the alias is unique for each field name, I would have thought Umbraco > Workflow > Send email would have been coded so that if a setting included {xxx} the xxx would refer to the alias of the input field but it appears to refer to the field name.
Has anybody else experienced this and have thoughts on the matter?
As the process still works, I do not believe this is an issue, hence raising the topic on the forum instead.
Use of {} not best practice when using Send email in work flow
We have created a form that captures a persons details for attending an event (name, email, telephone, etc).
If a different person is paying for the attending spot then we capture the billing details also (name, email, telephone, etc).
For the person attending the input field (short text) is called Email, with the alias of this field being email.
For the billing information the input field (short text) is called Email, with the alias of this field being billingemail - note: the billing information is inside a seperate group called Billing information, hence why the field is just called Email.
In our workflow we have chosen the send email option and set the Email (Enter the receiver email) field to be {email}
As the alias is unique for each field name, I would have thought Umbraco > Workflow > Send email would have been coded so that if a setting included {xxx} the xxx would refer to the alias of the input field but it appears to refer to the field name.
Has anybody else experienced this and have thoughts on the matter? As the process still works, I do not believe this is an issue, hence raising the topic on the forum instead.
is working on a reply...