1. The answer to this question depends on the context of your app and what the pipeline is being asked to do. Generally I don't care to control the number of records updated unless I'm testing the pipeline and want to limit the time and processing bandwidth used. If there should never be more than one or two or 15 records updated then you can apply the limit as a stopgap, just in case, but again, it depends on what you expect the Pipeline to do. I hope others chime in on how they use and get the most value out of this feature.
2. See #1, it depends what the trigger is and what directives the called Pipeline is given. Your video basically follows the Callable Pipelines FAQ tutorial. If you don't apply conditions to your function it will apply to all the records from the caller Pipeline. Notice the blue "add conditions" button that appears after you define your function inputs.
3. This is where you start to lose me. I think you're still asking the same question but I'm not 100% sure of that. As of my last use of Pipelines, you did want to pass in the key identifier for records you want to transform which is often {{a.record_id#}} I believe this is still the case.
4. Yes, the 1st Pipeline will complete the preceding steps before it moves to the subsequent step of calling the callable Pipeline. While requests made to Quickbase can execute out of order, a Pipeline follows the logic outlined in the order it was defined in. It could be that the request sent from the calling Pipeline has not completed processing all it's records yet, but the calling Pipeline did execute that step before moving on to the next one.
Hopefully, some of this made sense. I'll look forward to hearing how others here clarify what you're looking for.
Quickbase University resources:
Possibly related community posts:
