Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Comparing stateful and stateless services

Updated on March 18, 2019


A developer asks:

  • What is the distinction between Stateless and Stateful in the Service Package form?
  • What is the impact of the End requestor when done check box on the SOAP Service rule?


On the Context tab of the Service Package form, select Stateful when you want to maintain a clipboard across second and subsequent service requests.

Select Stateless to perform a simple calculation from inputs: the service request arrives, your activity performs a calculation, then send the response, and nothing you've done is needed to process later service requests..

On the Service tab of the Service SOAP form, the End requestor when done check box has no impact on stateless services. Regardless of the check box setting, when a service completes, the requestor is not destroyed so that Process Commander can re-use it for later service requests, thereby avoiding the overhead of creating another requestor.

For stateful services, select the End requestor when done check box only on a service that is the last one of a series of requests.

This indicates that you're finished with the requestor, so that it can be destroyed. Earlier requests in the series have the box cleared, so that the same requestor is used throughout.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us