Currently I am creating an Integration using the Application Integration service, one of the main features that are important to me is the call integration task, to be able to encapsulate some functionalities inside an integration and call this as a sub integration then, but using this approach is affecting the performance of the Integration at the end especially if we have multiple sub integrations in the same integration because it’s an API trigger call for each one of them. Is there another way to be able to do the same concept without affecting the performance of the integration?
In addition to @fengwan 's suggestion to use Private Trigger, you can also often make calls out in parallel to other tasks, and then join the flow back together so that you can take advantage of parallel processing. If each task depends on the results of the previous task, you would not be able to do this…but if you do have any independent callouts, they can be done in parallel.
Example: Note, I am using both a Private Trigger and an API Trigger so that I can use Call Integration efficiently, and also make this available as a Public API in case I need to call it externally as well. The two Call Integration Tasks will execute in parallel, and then when both are finished, the final task “Prepare response from Integration Calls” will execute.
@fengwan : In one of the scenario , I have an error catcher which is calling an integration through private trigger with SYNC strategy but no logs are generated in the UI (neither in main nor in sub integrations), but if used with ASYNC strategy , the logs are seen in sub integration.
But if I understood the document correctly, the logs of sub integration should be visible in the main integration. Am I configuring something wrong or is this a bug?
