We recommend designers instead use web APIs and the Start Process smart service to expose process models to external systems.
You can configure your process model so that it can be launched by a web service call. When the model is published as a web service, a WSDL is created that describes the parameters that must be passed and the protocol used to pass them. Authentication credentials must be passed as parameters to the web service.
Click Publish. The following WSDL URL is published for your process model
1 http://... /suite/webservice/processmodel/<SERVICE_NAME>?WSDL
<SERVICE_NAME> refers to the name you assigned previously (in step five).
Systems wishing to start a process published as a web services need to pass in a valid
password to successfully start the process. These fields should be part of the SOAP request message.
Usernames and passwords are passed in plain text. We strongly recommend using this feature with SSL enabled.
The username and password submitted when calling the web service must be those of the Appian user account that is intended to start the service.
The user account must (at a minimum) hold initiator rights for the process model that is exposed as the web service.
The user account must not be configured to authenticate via SAML
Credentials used to start a process must be stored on the remote system. Take precautions to ensure that these credentials are stored securely.
Credentials stored on remote systems must be kept synchronized when user account passwords expire.
If you have a third-pary Single Sign On (SSO) solution configured to restrict URLs by redirecting unauthenticated requests to the login page, the URLs for the web services (suite/webservice/*) must be excluded so that calls to the WSDL and endpoint are not redirected.
The following formats must be used for date and date/time values passed to an Appian process using a web service.
— For example —
— For example —
On This Page