Automatic email

[sven]

@sylvia.debaeremaeker,

You should add a result tag in the template so you can reference to it from somewhere else, like this:

| {% t “Conclusie op basis van professional judgement” %} | |
|-------------------75%-------------------------|----20%-----|---------+
| {% t "Continuïteit is " %} {% input custom.detail.bedreigd as:select options:“bedreigd|niet bedreigd” %}.| |{% if custom.detail.bedreigd != blank %} {% assign ind = 0 %} {% else %} {% assign ind = 1 %} {% endif %} {% unexplained ind as:indicator %}
| {% input custom.letter.Commentaar as:text size:mini %} | |

{% result "bedreigd" custom.detail.bedreigd.updated_at %}

So this part was missing from your code:

{% result "bedreigd" custom.detail.bedreigd.updated_at %}

More info for result tags can be found here:

CASE reference values across templates by using result tags

If you want to reference a certain value or variable from recon template A in another template, there’s a way to do it with the so-called result tags in STL. They work like this ( just type in result and press TAB to get this preformatted code ): {% result 'name' content %} where the name is a shortname you can choose, and the content is the value or variable you want to reference to. Let’s say we have this variable done_prepayments in our recon template Prepayments (which is al…

PS registers can only be used to take in values, so this code:
{{ $30+custom.detail.bedreigd.updated_at }} can never work as well.