Automations being phased out?!
With the recent email informing us that automations will be phased out over 6 months, the first person who has daisy chained automations and tries the tool to migrate those....let me know if it works!...
Forum Discussion
I have to say I was really disappointed to see this. I knew at some point it was going to happen but I GREATLY prefer automations to Pipelines for Quick base to quick base functionality and simple things. The interface is just so much easier and faster. Plus pipelines does not support a lot of functionality yet.
On top of all of that, I still have a lot of work to do to get the javascript out of my app and now this is another one I need to work on. As a "citizen developer" where this is not my full time job it is frustrating to stop new development so I can rework functioning parts due to features being removed.
I am all for pushing the platform further but it seems like we have half baked tools (the migration tool failed on the first 6 migrations I tried) and not a full functioning system in pipelines and we are eliminating proven automations.
Just my rant as this is very frustrating to me.
------------------------------
Ivan Weiss
------------------------------
On top of all of that, I still have a lot of work to do to get the javascript out of my app and now this is another one I need to work on. As a "citizen developer" where this is not my full time job it is frustrating to stop new development so I can rework functioning parts due to features being removed.
I am all for pushing the platform further but it seems like we have half baked tools (the migration tool failed on the first 6 migrations I tried) and not a full functioning system in pipelines and we are eliminating proven automations.
Just my rant as this is very frustrating to me.
------------------------------
Ivan Weiss
------------------------------
MarkShnier__You
Qrew Legend
Qrew LegendIvan,
On the JavaScript issue, here's another way to look at it. QuickBase is bound and determined to get a higher security clearance than they had before. I'm not an expert on the different levels but for example SOC 2, is an example of a security level achievement which needs to be passed with a thorough audit by independent auditors. By having that certification it opens doors for them to get into whole industries or sectors where they have been blocked. Perhaps US federal regulated industries or certain healthcare industries or maybe one day industries where financial information and credit cards are stored.
I figure that's a good thing because the bigger QuickBase gets the more engineers they can hire and the quicker we get more features. Typically when they develop new features everybody gets to use them and not just the giant accounts.
As for converting your existing JavaScript, QuickBase is probably obligated to tell you that you have a theoretical security risk by allowing use of JavaScript in your applications. We all know that for most of us that security risk is purely theoretical. Your existing JavaScript will work forever they have not announced that it is ever going to break.
So it is up to you as to when and if you convert that JavaScript. For my clients my focus has been on knowing whether or not if we did need to make a change to a button for some reason would I know how to change the button to make it compliant. But I have no intention of suggesting a project for all of my clients to review all of their uses of JavaScript and remove it from the apps. In my case I prefer to let sleeping dogs lie and I will worry about updating buttons when and if I ever have to change the functionality of that button.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
On the JavaScript issue, here's another way to look at it. QuickBase is bound and determined to get a higher security clearance than they had before. I'm not an expert on the different levels but for example SOC 2, is an example of a security level achievement which needs to be passed with a thorough audit by independent auditors. By having that certification it opens doors for them to get into whole industries or sectors where they have been blocked. Perhaps US federal regulated industries or certain healthcare industries or maybe one day industries where financial information and credit cards are stored.
I figure that's a good thing because the bigger QuickBase gets the more engineers they can hire and the quicker we get more features. Typically when they develop new features everybody gets to use them and not just the giant accounts.
As for converting your existing JavaScript, QuickBase is probably obligated to tell you that you have a theoretical security risk by allowing use of JavaScript in your applications. We all know that for most of us that security risk is purely theoretical. Your existing JavaScript will work forever they have not announced that it is ever going to break.
So it is up to you as to when and if you convert that JavaScript. For my clients my focus has been on knowing whether or not if we did need to make a change to a button for some reason would I know how to change the button to make it compliant. But I have no intention of suggesting a project for all of my clients to review all of their uses of JavaScript and remove it from the apps. In my case I prefer to let sleeping dogs lie and I will worry about updating buttons when and if I ever have to change the functionality of that button.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------