Description
In the body of “send mail” I can combine text and fields.
In the body of “compose mail” this is not possible!
Outcome: link in “compose mail” body is not active (clickable)!
Why it is a bug: because composing the body in both actios should have the same functionality!
How to replicate
compose thew body in “send mail” combining text (custom) and fields (e.g. Current Screen URL)
Very interesting: if I compose the mail body with URL in the template and use this very same field in “send e-mail” and “compose e-mail” actions, I get different results. In “send e-mail” URL is active, in “compose e-mail” URL is pure text!
I think template isn’t supported yet for “compose mail”. The workaround is to use a template column to build the output you want, and use that template column in the body.
Tnx a lot, I read once more my question, so I am not sure whether I explained the issue clearly enough:
There is clear bug (in design or in programming) defined exactly in your answer: “template isn’t supported yet for compose mail”. Unlike to this, in the action “send e-mail” there are template functionalities in the mail body. This is a bug because these two instances should have the same functionality. I am bothered with such pooq QA inside Glide development team.
Your suggestion for workaround is well described in my post: this of course functions, but the link transmitted through template column as an output gives URL which is a pure link text (not active link, not clickable), which is the poor experience for mail recepient!
Glide development has to improve QA in their processes!
in the e-mail body!
I solved it with workaround for the mail sender with instruction: “add space after URL aimed to get clickable link for recepient and delete this instruction!”.
Dirty workaround needed because of Glide development flaw!
I am a kind of expert for business processes. Here I can give the following advice: the issues are discussed here in the community, without bothering the support/development team. If something is thoroughly discussed like this topic and definitely considered as a bug, support should be automatically allerted for bug fixing. Asking to post the problem once more speaks against good process practice. It is standard beahavior of beaurocratic bodies whose intention is to discurage the users in their endeavors!
