SymXchange Proxy v2

Provides integration with SymXchange through raw SOAP XML. The Node inserts the administrative password from its Connection and returns the HTTP status, headers and response body for explicit Workflow handling.

Revision History

0.0.1.5 - Provides raw XML posting with Connection-owned credentials and HTTP response output.

Connection

Property Type Description
Password Masked Administrative password replacing the selected XML element.
TimeoutSeconds Integer Maximum request duration in seconds. Defaults to 300.

Setup Notes

  1. Use a Local Runtime that can reach the complete service endpoint.
  2. Enter the administrative password in the Connection.
  3. Prepare the provider's SOAP XML with an empty password element. Prefer HTTPS for credential-bearing requests.
  4. Map Response.StatusCode and inspect the response body before treating the operation as successful.

Methods

Post

Posts XML after replacing exactly one password element. HTTP failure responses remain output for Workflow branching.

Parameter Type Description
Connection Connection Administrative credential Connection.
Url String Full service endpoint URL. HTTP and HTTPS are accepted.
RequestBody String Raw SOAP XML containing the password element.
Namespaces Object Optional prefix-to-namespace dictionary. Supply together with XPath.
XPath String Optional expression selecting exactly one password element. Supply together with Namespaces.
Return Type Description
Response Object Integer StatusCode, text ResponseHeaders and raw text ResponseBody, including HTTP 4xx/5xx responses.

Usage Notes

  • Without a custom XPath, the Node selects Credentials/AdministrativeCredentials/Password regardless of element namespaces. Missing or ambiguous matches fail before sending.
  • HTTP errors and SOAP faults do not automatically fail the Step. Check both the status and provider response before downstream work.
  • Transport failures and cancellation throw. Redirects are not followed and normal certificate validation applies.
  • This Node does not add a SOAPAction header.
  • When migrating legacy proxy Workflows, convert _Namespaces text to the Namespaces object and rename _XPath to XPath. HTTP output fields are grouped under Response.

See also

  • SymXchange for structured requests and WSDL-derived templates.