My question is about how is interpreted a send or receive task when implementing a bpmn diagram in webmethods.
Is it seen as a service task? or can it be either a service task, a user task or a manual task?
Thank you for your answers.
My question is about how is interpreted a send or receive task when implementing a bpmn diagram in webmethods.
Is it seen as a service task? or can it be either a service task, a user task or a manual task?
Thank you for your answers.
This is an excellent question and I'm interested in the experience of others.
I currently use the Service Task only when I have an actual service operation that I need to reference.
In our situation, we never know the service operation when the processes are defined. That's because we have multiple implementations of the process across multiple systems (and even enterprises) and the actual service operation will vary. (Think of it as more of a logical, global process diagram, which are always localized) We tend to use Send Task and Receive Task instead.
But what would be most useful by the eventual implementer?
Conversely, is there a concern that using Service Task would be less "Business Friendly" to the traditional BA seeking to understand the global vs. local process differences?
Please note that the ARIS Community doesn't cover webMethods, which is a different product line of Software AG.
Please post webMethods questions on the TECHcommunity:
http://techcommunity.softwareag.com/ecosystem/communities/public/webmethods/products/suite/
Cheers
Rune