New Feature: Task Template #566
Description
Some organisations don't want to give too much freedom to anyone who might have access to the code of the tasks. Also, it would be useful to be able to update a task just once while its multiple instances are automatically updated accordingly.
To solve those issues, I suggest the introduction of "Task Templates": instead of replicating a task definition into multiple workflows, a "master" task is defined. Then that task can be used through "proxies".
That task definition should be hidden by default. However, to provide flexibility, any part of that task can be a) revealed, or b) editable from the proxies.