Connector vs Task's execution in relation to BPMN's methodology
In Bonita, a flow will actually give the same indication on your diagram : what will be the next step of your workflow.
Tasks are activities in the process, as you can see in details in Bonita Documentation . You have different types of tasks : human, services (performed automatically by Bonita engine), script, call activity, send or receive tasks and each of them drives a type of "action".
When you define a task, it will be combined with different input or output items. Among others like messages, variable, connectors will be defined to access external systems to read or write information.
I hope this helps. Delphine
Thanks for your clarification.
As a newbie to Bonita Studio, I was "confused" by the Connectors In, Operations and Connectors Out choices.
I understood a BPMN task is supposed to perform A (ie single) activity; this might be a subprocess which can drill down to multiple tasks. In other words, I was expecting only 1 place to define what to execute.
Although it lends great flexibility (Connectors, Operations), it does throw warnings when you use both Connectors "More than one connector is defined on . You should have only one to have a BPMN2 compliant design."
I was just wondering the design philosophy/rationale behind such a setup.