What is the use case in which we use online type and api type in API task?
Hi @Harshit, The difference between these two parameters is:
Online Type: Here, you will see all the APIs configured in vConnect and here you will be providing all the configurations for the API i.e. Request and Response parameters.
API Type: Here, you will find all the APIs of vConnect that you have configured in the API section of vFlow configurator. These APIs can be directly mapped with the API task as the developer has already provided the request and response parameters in the API section.
@AnushkaGupta in what scenario we use Online type and API type?
In the API parameter, you can use different instances of an already configured API in vFlow Configurator, the request and response can be different for each instance that you will configure in the API task.
In the Online parameter, you will see all the APIs configured in the vConnect here you will have to create different instances of API with different tasks every time. The request and response will be configured as each instance/task requires.
@AnushkaGupta how can we decide which one is the best to use?
@Harshit, Selecting the parameter to utilize can be done on one basis, i.e., how many different configurations/places a single API instance has to be utilized.