Records, Pipelines, and Callable Pipelines clarification
Hello! I am a new user, and I'm looking for some clarifications on some of the specifics about how records, pipelines, and the callable pipelines action relate.
I have a complex pipeline trigger by a user record creation. The pipeline runs through a substantial decision tree and updates records and sends notifications depending on the path through the decision tree the record takes.
However, I have run out of actions and need to set up a callable pipeline to do some record validation (instead of adding those steps into the main pipeline).
So, I am working on setting up the callable pipeline, but I want to make sure that the pipelines are only updating a given record, and not ALL records.
-
Update: before you read the next part of the post, consider that I may be overthinking this whole thing and I just need to pass through the record ID(s) for the records I want my called pipeline to validate.
-
- I assume that when a pipeline runs with the "record created" trigger that the pipeline will run only with relation to a given record; i.e. is the context of the pipeline run a single record?
Is that correct, or does it evaluate the whole table of records?
Or do I need to set a record limit on the trigger? - When I use a callable pipeline, does the calling pipeline maintain the context of the call; i.e. for a single or batch of records?
Depending on that answer, does the pipeline evaluate each of those records individually, or does it evaluate the entire table with respect to the called field(s)? - For example, here are my two actions. I thought I had them set up correctly, but I can't call the fields from the calling pipeline in the called pipeline (third screenshot). Update: this may be because neither of the pipelines are turned on, and I may be using Jinja expressions where I should instead be using aliases which I can set to the calling pipeline's fields (see this video).
Do I need to bother with passing the record IDs ("a.id"), or are those "implicit"?
Call action:Called trigger:
Not finding called fields:
- BUT let's assume that I get these calls to work. Will the changes to the records made in the calling pipeline have been written to the table when the called pipeline is called? Because that pipeline will need to do evaluations based on the records' data, which is dependent on the actions in the calling pipeline!
Thanks for all of your help!