While a process is running, invoked web services cannot return a message. Instead, the SOAP Connector Invoke activity maps the outbound data to the list of Java objects that are saved as a parameter on the parameter page. The connect activity calls the RequestProcessor queueConnectRequest method instead of calling the SOAP service. This method creates a queue item instance in the PegaRULES database, saves the primary page, parameter page, and dequeuing options to it, and sets the status to “scheduled” for an agent to resend the message.

To enable web service queuing, you must complete the following steps:

1. Open the SOAP connector rule to specify that the request must be queued instead of processed immediately.
   1. In the navigation pane of Dev Studio, click Records.
   2. Expand the Integration-Connectors category, and then click Connect SOAP.
   3. Click the SOAP connector rule that you want to open.
2. On the Service tab of the SOAP connector, in the Processing options section, in the Intended for field, select queuing (response will not be available).
3. In the Request processor field, enter the request processor that you created to define the queue location and dequeuing options.
4. Open the connect activity.
5. On the Steps page, expand the step that runs the web service.
6. In the Method Parameters section, in the ExecutionMode field, select Queue.
7. Add a Commit step in one of the following ways:
   • After the web service invocation step in this activity
   • In the parent activity that calls the connect activity
   Queuing a connection request is a database operation. Even if the activity does not contain any explicit database operations, you cannot save the queue to the database without a Commit step. For more information, see Configuring steps in an activity.