Operation of this method can be affected by Dynamic System Settings. See More about Connect SOAP rules.
This method operates on a named clipboard page that is the source and destination of data mappings. Make sure the Step Page column that calls this method contains the non-blank name of such a page.
This method has four parameters:
Enter the Service Name (second key part) of a Connect SOAP rule, an instance of the Rule-Connect-SOAP rule type. The system uses the class of the step page as the first key part of the rule.
Select to indicate the timing of execution
Optional. Enter an endpoint URL value to override the value in the Connect SOAP rule.
The Connect-SOAP method works as follows:
Run— Executes the simulation activity synchronously
Run In Parallel— Executes the simulation activity in a separate requestor
Queue— Queues the simulation activity
Run In Parallel— Executes in a separate requestor. (This temporary requestor has the same access group and clipboard as the original. At most 10 such child requestor sessions can be active at once.)
Queue— Creates a queue item based on the class and other characteristics identified in the Connect Request Processor, for later background processing by the Pega-IntSvcs agent.
This method updates the pxMethodStatus property. See How to test method results using a transition.
Design the activity to detect and handle exceptions. If the Connect-SOAP method with the Execution Mode of
Run In Parallel fails in a way that causes the Connect-Wait method to be skipped, the child requestor can be left hanging. If the limit of parallel requestors is then eventually reached, the parent requestor fails as well. By default, the limit is 10 requestors in parallel; you can establish a higher or lower value in the
prconfig.xml file or Dynamic System Settings using the
|About Connect SOAP rules
Creating Connector Simulations
How to detect long-running connectors
Methods and instructions by function
Open topic with navigation