Back to Blog
Servicenow ariba integration6/19/2023 ![]() ![]() ![]() For example, calls to the ImportFromPackage API can be synchronous. If a custom service is used to look up on-hand inventory, business logic is immediately run as part of the JSON/SOAP call, and an inventory sum number is immediately returned.īatch data APIs are considered asynchronous integration patterns, because when these APIs are called, data is imported or exported in batch mode.If OData is used to insert product records, the records are immediately inserted as part of the OData call.UserSessionServiceGetUserSessionInfoAsyncīoth OData and custom services are synchronous integration patterns, because when these APIs are called, business logic is immediately run. The caller might not be blocked, depending on how a call is made. You can't assume that the caller will be blocked when the Open Data Protocol (OData) is used for integration. The following examples illustrate this point. Patternīefore you compare synchronous and asynchronous patterns, you should be aware that all the REST and SOAP integration application programming interfaces (APIs) can be invoked either synchronously or asynchronously. The following table lists the inbound integration patterns that are available. An asynchronous pattern is a non-blocking pattern, where the caller submits the request and then continues without waiting for a response. Often, the type of processing that you must use determines the integration pattern that you choose.Ī synchronous pattern is a blocking request and response pattern, where the caller is blocked until the callee has finished running and gives a response. ![]() Processing can be either synchronous or asynchronous. This is currently available on 7.2, platform update 12 build. For on premise deployments, the only supported API is the Data management package REST API. ![]()
0 Comments
Read More
Leave a Reply. |