Forum Discussion

Re: First Stab at Pipelines: Observations

That is my understanding so far.

------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------

1 Reply

  • JimHarrison's avatar
    JimHarrison
    Qrew Champion
    I asked Support and here is my interpretation with embellishment.

    The "Set" or "Is Not Set" function is a trigger filter. For example when a field in a record changes from "Set" to "Is not Set"  or the converse the Pipeline is triggered and runs. 

    When a User enters data and saves - the trigger is called and this allows the "Builder" (you) to filter which changes start the Pipeline. This is good because otherwise anytime a change is made all the Pipelines run and that is bad.

    Pipelines are all about knowing when data changes and doing a thing. In an effort to limit how often the Pipeline runs, you have to apply filters. In this case "Set" = "Present" =  "NOT NULL" and "Is not Set" = "Is not Present" = "NULL" does the thing when the User makes the change and saves the record.

    Jim Harrison
    Portland, OR

    ------------------------------
    Jim Harrison
    transparency = knowledge + understanding : The Scrum Dudes
    ------------------------------