Thank u Victor for the awesome explaination. Just wanted to add one thing. We can use Aggregate Source option in Datapage when subsequent API calls are dependent on each other
We can execute the same with the run in parallel option on the connect rules with the connect wait option, but I prefer the data page asynchronous option. We can also do the same by executing the activities asynchronously with the async activity method and with the connect wait option. But to do this the activity should be of type aync.
Indeed, but doing it with a Data Page enhances modularity of the code , compared to pushing an activity into the child thread... Run In Parallel in Connect-RULE is not a good approach in my belief, as the Request-Response mapping is still done in sequence.
Did not feel like a 20 min video. Great explanation . Rightly explained and stated all key points . Thank you
Thank you !
Thank u Victor for the awesome explaination.
Just wanted to add one thing.
We can use Aggregate Source option in Datapage when subsequent API calls are dependent on each other
Thank you !!
Yes there are several ways of handling dependent API calls : I did not go into the details because that was off topic :)
Good job
Thanks !
Good info bro.Thnq
Welcome !
We can execute the same with the run in parallel option on the connect rules with the connect wait option, but I prefer the data page asynchronous option. We can also do the same by executing the activities asynchronously with the async activity method and with the connect wait option. But to do this the activity should be of type aync.
Indeed, but doing it with a Data Page enhances modularity of the code , compared to pushing an activity into the child thread...
Run In Parallel in Connect-RULE is not a good approach in my belief, as the Request-Response mapping is still done in sequence.
@praveen siva : thank you for letting us know other options too
what if one the 3 api calls fails and does not load data, how do we handle such scenario,