Glad they have made updates. Now if they could just make updates without taking AWAY things, that would be awesome.
Some of the improvements they have made mean that there would need to be a full rework of apps, and possibly entire realms. It makes a person think, "Humm, should I spend all this time reworking everything I have on this platform that doesn't seem to care about how the end-user actually uses it, OR do I transfer it to something else like AWS, eat the heavy cost now, and have it on a platform that, although harder to use, won't ruin / restrict my app functionality?".
Can customers choose if they need the most secure everything and have restrictions? I know most of my realms have been, and will be, just fine without NASA level security. But sure, give the CHOICE. That would be fine. But don't just knock out perceived insecurities just because 2% of your clients need all the security certifications on the dang planet.
"... we all need to get used to the new table reports, but that is being done with recognition that a new technology was needed for table reports to allow for enhanced performance on large record sets..."
Yeah, great. Still like the old format better. Personal preference. And that is the thing. How about you just leave it up to the customer on how they want to see things? How about adding some report css styling options? Wow! now that would be something! I want the header Red. I want the columns all the same size. I want to make the last column Blue. I want the font to be h5. I want my gridlines white. Why can't I do this unless I hack the css through an Exact form? Why can't I make another page my table's home page? So many other things as far as formatting and report improvements that I feel are much more useful.
Oh, and speaking of large data sets... let's talk about table limits. WTH? How many of your clients would pay anything just to get more table space? This BS limit has to go. If you are wanting to be Enterprise, than you HAVE to work this out.
"... they are starting to roll out Platform Analytics - the ability to see which apps are being used by which users."
Ok, where to get stated on this... I think this request has been on the stack since the dark ages, so I don't really know how to applaud this one. I know as part of that featured request, customers would like to know if someone messed with a field's code, and when (like full history). What fields are being used, by whom (maybe even what their role is). Who uploaded data, when, how (full history)? Currently if some "Bozo Bob" goes in and changes the code on a field, and I don't know about it, I don't know what is going on, who did it, or when they did it. It is just broken, and that is all I know. That is a big problem.
"To their credit (after listening to customers), they must have reconciled their need to achieve a certain security certification level of the platform with the desire of users to extend functionality with iframes."
I am glad for this reversal, as I probably would have just burned the place to the ground if they had taken this away. SOOOOO many apps rely on the wonderful code that Kirk has given us. Again, if this is just a security thing, let it go. Let us keep our iframes, colored buttons, and icons. I don't know if they don't understand how much this kind of code is used or if they are just trying to start a riot, but this will surely do the latter. Same for nixing or IOL. If you want to piss us all off, just play with our code that were work arounds for features that QB didn't have to begin with. Again, SOOOO many forms, buttons, etc have this code in it, not because we wanted to spend hours learning the ways of Dan, but because we HAD to in order to make our apps work the way we NEED them to. If QB kills any of this without a damn good and easy replacement, there will be an absolute riot. So you can just bring that up to the Dev Team to tread very carefully on this.
"There is other useful stuff to like being able to natively pop up a no code pop up window as opposed to a new tab. That is probably in response to the intention to block javascript later in the year."
Yeah, once again, how do I applaud this? Good? Yeay? You are taking away a feature that we use. They better have a replacement. Duh. You also could already do that natively in forms with "display a message" for the most part, soooo trying to figure out why this would be such a "wow". Also hoping that it is not just something that is annoying and that we have the choice of conditionally displaying it.
"Plus, of course, more Pipelines features as they are dedicated to improving them."
I will have to agree with you that Pipelines is getting better. Need a lot more documentation and examples on it (like a LOT more), but all-in-all it seems to be going in the right direction. The visuals really need to be condensed, and it would be nice to be able to have a customizable title/description for each step that shows when it is collapsed but all in, it is getting better. However it is not a reason to kill Automations. Automations still have their place. I think is going to anger many, many people when you start messing with these. Honestly, until you have a much larger library of learning and forum posts on Pipelines, Automations need to be left alone.
AllI am saying is that they best talk to all their customers, not just their biggest ones, before they start making these "kill feature" announcements. They may be unprepared for the backlash at EMPOWER...
------------------------------
QuickBase Girl
------------------------------
