Hello!
Well, using a mail template I'm naturally relying on the notify parameter specified in the task node xml definition, like this:
| <task-node name="Draft"> |
|
|
| <task name="program_defined" swimlane="PM" description="DRAFT" notify="true"></task> |
|
| <transition to="Active" name="validate"></transition> |
| </task-node> |
|
As such, I'm using an xml template in which I can invoke my processInstance properties and variables.
I.e. with #{taskInstance.actorId} to obtain actorId in my mail template.
By the way, my issue was solved as I thought. Infact, if you carry a set of variables with your taskInstance, you can retrieve them by calling them in this way:
#{taskInstance.variables.variable_name}
where variable_name is the key name used to store your variable in the taskInstance.
Hope this can be useful to someone else!
Cheers!