Many organizations are finding that the need for innovative processes and automated work is continuously growing while even the most flexible tools are no longer fast enough when they don't work toget...
Published 5 years ago
Version 1.0
Blog Post
MarkShnier__You
Qrew Legend
Qrew LegendYou can certainly trigger with a formula URL button by just having the button toggle a checkbox field. As for a dialogue box, well that may be your real question.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
Let me ask it a different way for Rhett...
(1) Today an Automation is triggered by a QB created/stored/somewhat-hidden Webhook that packages up every field in the record (whether needed or not for the Actions) and ships it off to the Automation engine for processing. Are Pipelines essentially using the same methodology? or is it a tighter integration?
(2) And Mark, I'm with you... I believe Rhett is really wanting to know if a Dialogue box could kick off a Pipeline and then perform an Action after the Pipeline is finished running.... providing a path away from Javascript / IOL solutions. High level use case:
a. User clicks on Pipeline trigger button (new field type?)
b. QB App presents dialogue box with progress bar / spinning wheel / etc
c. App triggers appropriate endpoint Pipeline configured in the QB PIpeline trigger field
d. Pipeline Success = dialogue box shows "Success" and then performs an action (refresh page / redirect / etc)... possibly configurable returned data payload so it can be utilized in the Action
e. Alternately, Pipeline Failure... display the error to the end user
------------------------------
Kurt Johnson
------------------------------
(1) Today an Automation is triggered by a QB created/stored/somewhat-hidden Webhook that packages up every field in the record (whether needed or not for the Actions) and ships it off to the Automation engine for processing. Are Pipelines essentially using the same methodology? or is it a tighter integration?
(2) And Mark, I'm with you... I believe Rhett is really wanting to know if a Dialogue box could kick off a Pipeline and then perform an Action after the Pipeline is finished running.... providing a path away from Javascript / IOL solutions. High level use case:
a. User clicks on Pipeline trigger button (new field type?)
b. QB App presents dialogue box with progress bar / spinning wheel / etc
c. App triggers appropriate endpoint Pipeline configured in the QB PIpeline trigger field
d. Pipeline Success = dialogue box shows "Success" and then performs an action (refresh page / redirect / etc)... possibly configurable returned data payload so it can be utilized in the Action
e. Alternately, Pipeline Failure... display the error to the end user
------------------------------
Kurt Johnson
------------------------------