Expose process or object as web service

[RichardLoughins]

Hi, Just looking to get some opinions regarding whether it's best to expose a process or an object as a web service for the following scenario: I want to create a connection with another application, which sends a SOAP request to Blue Prism whenever it completes a particular task.  All the Blue Prism process/object has to do is add this new request to a work queue, and send back a success or failure message to the external application. What's the benefit of exposing a process over exposing an object in this scenario, or vice versa?  Is there any real difference? Thanks in advance for any advice.

[AshishEasow]

Depends on what functionality you want to expose. Your objects cannot contain your business logic, your processes do. So if you want to expose small actions without any business logic your objects can do that, but you should try it first, because you would need to initialise it before calling, think about sessions logs for the calls, license considerations (when you run multiple web service calls) etc. And obviously since the objects should not contain business logic, then the application which calls it should be the one which does the business process bit. If you call processes, the complications are less, but of course the process would need to contain the required functionality.  The difference between them, would probably how you call them (initialise, license etc) and calling a full functionality vs calling granular building blocks for a functionality.