Hi ,
Today I got an opportunity to test the composite API in our Sandbox . The idea is great , I love the roll-back feature which will make integration platform using Salesforce for process orchestration more efficient. Composite API will certainly minimize api call outs & avoid junk records being created during a process failure in a integration with the rollback feature .
One good use case that I can think during the first trial is to enable a conditional execution of a subRequest especially for write operations (POST,PUT,DELETE ) to
- skip records being created/updated based on the reference-record created from another subRequest
- avoid roll-back or composite API failure in case of an expected validation error message in one of the subRequest based on the reference-record
Please help with the below question as well ;
- Can a SF custom rest API be invoked from Composite API request ?
- Is RESP APIs provided by managed package supported ?
- What is the maximum timeout
- What is the order of execution ? I believe the approval process,flows, WF email ,field updates ,apex triggers will be kicked-off only on successful execution of composite API .
Great job team , eagerly waiting for the release .
Thanks
Sathish
1. No, currently you cannot include custom Apex REST APIs. There is a fine line here, as we do not want to build a programming language out of composite. for advanced operations, you would want to use pure Apex
2. No, since managed package APIs would be custom APIs, they would fall into #1. Now, if you are talking about accessing Objects in managed packages, then that will be possible, as they are exposed as SObjects
3. This is the same as the REST API timeout, and varies per call.
4. The order of execution is the same as any API call when involved with platform logic -
https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htmKeep the feedback coming!
