First Stab at Pipelines: Observations
I tried the turn Automation into Pipeline thing today.
When I did the convert function some things worked others didn't. That is expected.
Looked at the converted to pipeline processes that worked and all were done by Pipeline Automation convert service account. Ok, where did that come from?
Noticed there is a Query parameter named "Is Set" and "Is not Set" not sure what that means. Searched the Internet and didn't see any reference to this terminoligy so I sent a support ticket to QB asking what it means.
The convert thing took my "when a field changes update another field" process and turned it into a bulk record upsert with steps. ummm that's weird. After a while I started thinking that it takes less effort to learn how to write a functional Webhook.
I added one Pipeline that appears to make sense and turned it on and then thought, ok how to I test it is working? So I need to figure that out before I come in to find the entire table is update.
They seem like they are working. I feel like I am going to need to set up some tables with data and smash around with things for a while.
When the drop down lists show up, make certain the DDL is in the middle of the page because there is no way to scroll down and the ddl just goes off the bottom of the page, so lots of positioning prep required.
I think the query thing would be more useful if you could click a little preview pop-up that does a top 10 results. So I can see what the query is returning.
The whole, make your results as minimal as possible so it doesn't cost you a lot of money is nerve wracking and distracting seeing as how I'm not really certain if there's a charge being applied. Also ours says the steps reset date is November 18th, wondering where that date came from???
I can't see anyone else's pipelines on my team. I can see all the Webhooks everyone created on a table ever in one view.
I'll keep playing with it when I have time but I'm not ready to adopt this as a working solution.
That's all I got.
------------------------------
Jim Harrison
transparency = knowledge + understanding : The Scrum Dudes
------------------------------
When I did the convert function some things worked others didn't. That is expected.
Looked at the converted to pipeline processes that worked and all were done by Pipeline Automation convert service account. Ok, where did that come from?
Noticed there is a Query parameter named "Is Set" and "Is not Set" not sure what that means. Searched the Internet and didn't see any reference to this terminoligy so I sent a support ticket to QB asking what it means.
The convert thing took my "when a field changes update another field" process and turned it into a bulk record upsert with steps. ummm that's weird. After a while I started thinking that it takes less effort to learn how to write a functional Webhook.
I added one Pipeline that appears to make sense and turned it on and then thought, ok how to I test it is working? So I need to figure that out before I come in to find the entire table is update.
They seem like they are working. I feel like I am going to need to set up some tables with data and smash around with things for a while.
When the drop down lists show up, make certain the DDL is in the middle of the page because there is no way to scroll down and the ddl just goes off the bottom of the page, so lots of positioning prep required.
I think the query thing would be more useful if you could click a little preview pop-up that does a top 10 results. So I can see what the query is returning.
The whole, make your results as minimal as possible so it doesn't cost you a lot of money is nerve wracking and distracting seeing as how I'm not really certain if there's a charge being applied. Also ours says the steps reset date is November 18th, wondering where that date came from???
I can't see anyone else's pipelines on my team. I can see all the Webhooks everyone created on a table ever in one view.
I'll keep playing with it when I have time but I'm not ready to adopt this as a working solution.
That's all I got.
------------------------------
Jim Harrison
transparency = knowledge + understanding : The Scrum Dudes
------------------------------
