templates are a great tool for us, however two functionalities are missed in my organization:
1) loop characteristics
E.g. we use sequential multi-instance external service tasks to send e-mails. It’s possible to define implementation, topic, input and output variables in the template. When the template is used however, it’s no longer possible to configure the multi instance characteristics, namely the “Collection” and “Element Variable”. It’s also impossible to define those in the template.
Effectively, we can’t use templates for our e-mail tasks. Which is a pity.
2) boundary events
Less critical but still nice to have would be the possibility to define boundary events in the template. We want to make sure, that certain boundary events are not forgotten, e.g. an error event on a database-query-call activity. It would also make the template more useful in general.
We would really appreciate if the mentioned functionalities could be implemented in future versions of the modeler. We would write something ourselves, but don’t posses the necessary resources.