It was ‘<’ and ‘>’ everywhere except at the places where I wanted value of the column. But it was not showing buttons in the received email, rather the entire code in the email body of the received email. So, I thought to format it like HTML body template.
<< and >> should only occur around template variable names an template expressions, not around HTML tags. HTML tags should use < and >. For instance, <<form ...>> is not HTML, but <form ...> is.
Even the simplest bit of HTML markup does not work inside of the email body section.
This renders the email notifications to almost strictly plain text and dynamic values only. Not a high amount of utility gained there in my opinion. Looks like the email body template is the ugly stepchild of Appsheet’s featureset.
My point is that html does not render in the expression assistant, which is where you have to write the message that is output in the email.
You could write simply “test” in the expression assistant and it would work, but you can’t add any HTML tags within or outside of an expression.
I could have used a better screenshot to illustrate, but my goal is simply to indicate that there’s no solution for this problem like @Rajan_PACHCHIGAR indicated.
This only seems to work for the Workflow expression assistant.
The Actions expression assistant that generates email doesn’t like HTML. I think you explained this in another post, but ultimately it would be nice if HTML just worked the same in both areas. I got tripped up heavily understanding that the two body sections don’t exactly work the same in this regard.
