Design Studio - Allow additional BPMN Activity TASK Types

[smsjames]

Allow the process map to display the following additional activity TASK types.

• Send
• Business Rule
• Script

They should all be linked like a Service Task to a "Automation Service".
This allows for a cleaner and more descriptive process map, where the key purpose of the task can be clearly identified.... 

[Karen_Hunter]

Would this be more applicable in the Service Model Design rather than at the Process Level?

[smsjames]

Hi Karen, 
The task types are defined under the BPMN specification and it is these that I am suggesting we should add.  More information can be found in the BPMN poster http://www.bpmb.de/images/BPMN2_0_Poster_EN.pdf or the full specification https://www.omg.org/spec/BPMN/2.0/PDF in section 
10.2.3.1 Types of Tasks.

As we do not have a direct template for the receive task (fundamentally rendezvous queues) I would suggest that we  dont add it.
However, the Send, Business Rule and Script Tasks all can be articulated in the form of a Automation Service.  
The manual task is irrelevent as all parts of the actionable process are sitting inside Chorus so none would be classified as a "Manual" Task.

Adding additional "Service Types" into the Process Modeler to mirror those Tasks might make some sense, however I'm not sure it is fully required.
Give me a shout if you would like to discuss further.