Return to main navigation Page
XML and Real-Time Integration
Real-Time Integration is the mechanism that sends transaction
XML to a 3rd party server when a transition rule is fired. This is the
most standard, out-of-the-box CPQ Cloud functionality for implementing
For more information, see Standard XML Output for the basic XML structure. See attachments for a Real-Time Integration Sample Document XML.
||Triggered during workflow
||Synchronous, however CPQ Cloud can't parse the result.
Setting Up Real-Time Integration
- Navigate from Admin Home Page > Integration > Integration Settings
- Enter the Host URL address of the Host that has to be accessed.
- Enter the User Name of the partner server.
This is only required when posting to a site that requires a secure login.
- Enter the password required to access the partner server. *Only required when posting to a site that requires a secure login.
- Determine if you would like to enable authorization during the HTTP Post connection method by selecting:
- Specify whether or not to integrate Users by selecting Yes or No.
- Enter the connection timeout (in seconds). This indicates the duration after which the connection will be closed.
- Enter the maximum number of retries that are allowed.
- Specify the Connection Method by selecting either Web Methods or Http Post.
- Click Test Connection. An error will
be thrown if the connection cannot be established. For example, if you
use the wrong username, it will tell you that you entered the incorrect
- Click Accept to accept the information and return to the Admin Home Page or click Cancel to return to the Admin Home Page without saving changes.
All fields should be filled in to enable two-way communication between your partner server and the CPQ Cloud trading hub.
When using the "HTTP POST" integration
method, CPQ Cloud will attempt to send data to the URL that you specify.
To confirm reception of the data, the receiving URL must respond with
the word 'success', all lower case and without the quotes, and nothing
If CPQ Cloud does not receive this response quickly
enough, it will attempt to re-send the data, up to the number of retries
specified in the integration settings. If any response other than
'success' is received, it will be considered a failure and the
integration data will be sent again. In most scenarios, it would be
ideal to respond first, then process the data.