Bizagi features a generic SOAP Web service connector (the "WS Connector"), which you can easily configure, without writing any code, using a graphical mapping interface.
This feature is designed to allow you to configure application integration in your business processes, as described in Application integration.
About the WS Connector
This feature is accessible from step #6 of the Process Wizard in Bizagi Studio (Define integration interfaces).
When moving into step #6 of the Process Wizard, you can easily configure invocations of web services in integration points of your processes:
When you select an integration point in a process, the WS Connector presents a 4-step configuration wizard that lets you to input the service's URL and rely on auto-discovery capabilities to further configure the invocation of a given web method.
The graphical configuration lets you easily configure mapping for inputs, outputs, transformations, and optional error handling.
Standards supported by the Web service connector
The Web service connector is a powerful generic tool which consumes any Web service, whether in the corporate ESB, in the cloud, or as an external application.
The following SOAP Web services are supported:
•SOAP 1.1 compliant Web services.
•SOAP 1.2 compliant Web services
•When invoking SOAP Web services, you must use POST as the Web method.
•When invoking REST services, you must send and receive information in XML format.
•WSDL version 1.0. is supported but version 2.0 is not supported.
These additional Web services extensions (WS-*) are supported:
•WS-Security: Authentication by Username tokens, and by Binary security token (version 1.1 spec).
The service is required to publish a public key in its WSDL for authentication through binary security tokens while observing message protection (encryption).
If you need to invoke a SOAP Web service which uses definitions from a standard not listed above, such as WS-Discovery, or to satisfy a requirement not supported by the connector (such as X invocations of a service once per each record of a table), you need to use either Bizagi Connectors (preferred), or the Component Library feature in Bizagi.
This also applies if you want to invoke a RESTful service which uses OAuth in its authentication.
For more information, refer to Integrating APIs or custom code.
For more information about this feature, refer to its comprehensive documentation at Web services connector.