Name: Feature Focus: The Quickbase Summer Drop
Uploaded: 2026-07-16T18:31:32.789Z
Duration: 1 h 2 min 4 s
Description: Feature Focus: The Quickbase Summer Drop

Transcript for "Feature Focus: The Quickbase Summer Drop": Hi, everybody. I'm Evan, and I'm your host today for the Quickbase Summer Drop. We're gonna be taking a dive into some of the recently released features and enhancements that we've had that you wanna make sure to get on your radar as a builder or an admin, and just kinda go through a little bit of, like, what's been going on at Quickbase since Empower in the spring. I hope you've all been enjoying your summer, and you are also, for those of you who are in the path of it, staying out of the smoke, and hopefully getting to, enjoy your summer otherwise. If anybody who's joining us today is having any audio or visual issues, I recommend you take a look at the bottom. There's a light version option. If you're having any trouble hearing or seeing me, feel free to jump into the light version option, and that will let you take a look at it'll basically make it a little bit easier for you to hear me and see you as we follow along. For those of you who haven't joined joined us before, for a webinar, we are on this platform, you can see the chat just next to me on the right. That's where you can chat with everybody else in the, session. You can also use the documents up right above the chat to look at some of the links we've provided. Just follow-up is information for some of the things we're talking about today. And super important, the very last option is q and a. That's where you can drop any questions you have during the course of the webinar. Say we talk about a feature and you want to get a little more clarity, you want to follow-up, jump drop your question in there. We'll be doing a q and a section at the very end. But, otherwise, we're just going to give folks another minute to start to filter in. I'm seeing plenty of people jumping in the chat already sharing where they're joining in from. That's always great to be able to see everybody joining us. We're just gonna give folks a second to finish their lunches and set the funnel in or grab their lunches and funnel in. And just for those of you joining us today, in the past, we've done some of our feature focuses that we've also referenced things like Fast Field or Pave. Today's feature focus is just going to be on Quickbase. So for anybody who is a Fastfield customer joining oh, hey, Sam. Nice to see you. We're just not gonna be covering Fastfield today. We're just going to be focused on Quickbase core. Alright. It looks like we have a good number of folks in, so let's get started. So as I mentioned, I'm gonna be I'm Evan. I'm your host for today. I'm a member of product marketing team here. We're also going to be having Rina join us from our, product management team. She's gonna be joining us to talk a little bit more about, native solutions. So what we're gonna cover today is we're gonna have Rina join us to do a demo and walk through of what is changed about the way you can think about, application life cycle management in Quickbase and how you think about managing those changes that matter the most on the on the applications you have that matter the most. We're gonna touch on grid reports to now GA, making sure that everyone feels comfortable when they're ready to make the change from our previous version of reports to the new grid reports option. We're gonna go over a bunch of smaller builder and admin enhancements, and then we're just gonna rev review some information on our intelligence package and extensions. We've added a few things to them and also made a few small changes. So we just wanna bring those up for folks so that they're aware if it's something that's kept them, like, on the fence, and then we'll wrap up with some q and a. In order to give her the most time possible, I'm gonna move us on to native solutions with Raina, and I'm gonna hand it over to her so she can walk you through. Hello, everybody, and thank you, Evan. So as Evan said, I'm Reina. I am from the product management team here in Quickbase, and my focus is mostly on governance and more specifically application life cycle management. And, I've done a lot of talks about application life cycle management before, and a lot of them have been quite theoretical about what is ALM and why do we need it and why do we wanna use it. But today, we actually wanna focus much more on just a demo and, what do we have in the product, what you can use, and how you can use it. So I'll try to go ahead and share my screen now. Just a second. Evan, maybe can you give me a hand with sharing a screen? Oh, alright. So, when it comes to application life cycle management in Quickbase, everything starts with solutions. If you're not familiar with solutions, solutions are a packaging of apps and pipelines that work together in a functional system. So a solution would look very different from for each of you depending on how your, business processes are structured. But for the purposes of our demo, here we have one solution that has one application and one pipeline. Both of them are working together to represent one business process. And the goal of having them in one solution is that now that we'd start on the journey of creating development and testing environments, making changes, and then testing those changes, we wanna make sure that while we are working in isolation from our production environment, we are still testing everything together. So you do not just test the app or just the pipeline, but we can test the entire workflow and make sure that the changes are really having the outcomes that you desire and they don't have some negative impacts that you do not expect. So for our solution here, where we have the one app and one application, what we can now do with some of the latest capabilities we have released is create environments. This action really expects you to create a development and for testing and production environments. You have some options to select from. So you can select the only development and production or dev test and production. Let's do three for the sake of the demo. And you can also choose if you wanna carry over some of the data from production to the lower environment for testing purposes. You can choose if you wanna do a sample dataset with 50 records per table, or you can copy the entire data from production. Also, you can select if you want only, in the test environment or the dev environment or both of them. In this case, let's only do a test environment. Once we click next, we are going to enter the next step and actually the latest feature that we released recently, which is what we call environment configuration. While environments and the environments for each solution are really, mirroring the same solution that you have in production two times to make your development and testing environments and inside there, everything is the same. You have the same apps with the same fields and tables, the same reports and charts. The only difference is really users and who can access the different environments. There are some aspects of of those apps and pipelines that you expect to have differences across three different environments. So a very simple example of that would be things like names. So if you have an application that's called digital marketing lead tracker in production, you expect to have a different name in the lower environments to just make sure that you can differentiate those apps and and you're not mixing them up. We have parameters to manage those differences. We have parameters for things like names and app icons and colors and, that kind of things. You can basically select different values for those different items to make sure that the environment's differentiated enough. But environment configuration really goes way beyond that in into a functional direction. So, for example, if you have a pipeline, that is connected to Salesforce, for example. As we know, Salesforce is typically a business critical system. And, let's say you're making changes to your pipeline in Quickbase in a dev environment and, obviously, you want to test those changes. Most likely, you do not want to test the changes on the pipeline against the production instance of Salesforce. You don't wanna trigger Salesforce workflows or to pull production data or to push the production data in there. You would want to actually connect your dev environment to in Quickbase to your dev instance of Salesforce. And environment configuration is one of those features that enable you to do this. Basically, the same pipeline can have different connections, to the same system in development, testing, and production environments to maintain those differences, to keep things compliant, and to make sure that you're always testing in a safe environment without mixing up production, resources. So here in this, feature here, we can basically select our different values for three environments. And when we're ready with our selection, we can go ahead and create environments. In this case, what really happens is that the system is copying the app and the pipeline two times over to create our development and testing environments. This action might take a couple of minutes, especially if we're talking about bigger applications, But it would never be more than two, two and a half minutes for for any given solution. And once we are done, we now have our development and testing environment creation created. So if we go to our dev environment, for example, we can open our dev application, which is going to be the same as our production application. Initially, when it's just created, I am the creator and I am the app manager for this app, but I don't have a a role for it yet. So I can assign myself a role. I can start adding other users in here, and I can make sure that we have all the right users added in here. We do not copy the data to our dev environment. That's why we're seeing empty charts. But if we go to our testing environment, for example, we expect to see all the same data as in production in here. So we're going to do the same as in the other one, assign ourselves a row, go back, and we'll see the same charts that we have in production we have in here. Going back to our dev environment. So how do we actually wanna use this? Now that we have the three environments, the first thing you would really wanna do is start managing your users and who can do what in each environment. Our general recommendation and also the best practice from application life cycle management is to make sure that in production, you keep users without permissions for making changes, and you only assign changes, schema change permissions in the dev environment. This way, you can streamline your process and make sure that your, all the changes are always going to go through the ALM process, and they are always going to be tested. And you're never going to create some conflicts between changes done in the dev environment and in parallel development directly in production. So now that we are in our dev environment, we can basically start making changes. It would look just like any regular building exercise. Nothing is different here. You build and you test just like you normally would. The only difference is that we are isolated. We are not working with our production data. If we're triggering pipelines, we're not triggering them against production records. We are working in this safe environment. Alright. We're going looks like the when you changed over to the Denver test environment screen, it's still just showing the, solution Oh, alright. That's good. Let me do this then. Okay. So we think we're looking at our dev environment application right now. Let me know, screen. Evan, please, if that's not the case. Yes. I see it. That environment with, I see your mouse moving around now. Alright. Thanks, Evan. So now that we are in our dev environment, we can really start making our changes the very regular way. We are going to do some really simple changes because we're doing demo. So we are going to create one new table, and create that. And let's also rename white table. Alright. So let's say we've done our changes, and we're done with this set of changes. Now we wanna start moving those changes up the chain, and now we wanna send them to our next environment, which in this case is our development. So, we go back to our solutions interface, to our development environment, and from here, we can, initiate the review changes and deployment process. When you click on review changes, we are going to start a comparison between your development and testing environment and present all the differences between the two, which is basically giving you the list of things that are going to be changing with this deployment. So what we did, we added a table. So we can see this table here. We can see the full description of the table with all of its, properties. And if we scroll further down, we'll see the role permissions, which are default since we never touched them. If we scroll more, we'll see the fields that we added and so on and so on. And we see the name of a table that we also changed. So we see the old value and the new value here. So we can observe the entire set of changes during this process. And if we're happy with the set of changes, we can move on to the next step, which is, again, the what we saw in the beginning, the familiar environment configuration, which gives you the, opportunity once again to change something in the configuration between the environments. So, we created something with, predefined values for those parameters. But if we want, we now we can again change the values. If we have created additional parameters in the meantime, for example, we added the pipeline with new channel accounts that we wanna switch now, you would have the opportunity to do it here during the deployment process and make sure the new values are going to match or your expectations. And once we're happy with those selections here, we can hit publish. A publish is now going to basically transfer all of the changes we did in the development environment to our testing environment. Deployments are strictly happening from development to testing and from testing to production. This is the only flow that we allow. We do not allow, for example, from production to development or from development straight to production if you have a test environment. If we go to our test environment now, we can open our test application and observe the changes that we made have been transferred here. So now we have our test table created in the dev environment in a matter of seconds, and we have the renamed table. So this is really the real the the short version of what, application lifecycle management features we have. A few other mentions here, those workflows that we just saw in demonstration, they also go hand in hand with a versioning feature, which allows you to store backup versions of your schema, so your apps and pipeline schema. You can store a backup version here and keep it as a backup in case something goes wrong. So a best practice would be before a deployment to production, make a backup version, store it here. In case something goes wrong, something is not working as expected, you can always, roll back and basically bring the schema back to the state that you knew it was stable and it was working as expected. And last but not least, all of these goes application life cycle management always goes hand in hand with, with, an activity. So, basically, it needs to be transparent. You need to see what's happening. So we have an activity log here where you can observe, records for each deployment, from which to which environment, who executed it, and soon you will be able to also observe the change set that was applied with this deployment. And with this, I will stop this demo. I invite you to add any of your questions you have in the chat. If you have if you wanna more do a more, thorough dive into ALM, you can always contact your CSM, customer success manager or customer account manager, sorry, and, ask them questions. Also, I'm available to talk to anybody who is interested in the topic. Thank you so much for joining us and and, taking us through that today. There's actually a couple of quick questions. I figured we could jump in and and address a couple of them, and then we'll save anything else that comes in later for the q and a. But there's a couple good ones here. The first one was, is there an ability right now or is there is there ability in the plan to clone an app through ALM on the road map so that they could develop an app and then deploy it multiple times? Oh, that's a great question. Short answer is, you can do that, but not with the user experience that we saw. We have a set of, APIs, what we call solution APIs, that will enable you to do a system like this, a one to many system, where you can set up one template and deploy to multiple instances of the same solution. It is a little bit more technical task, and so we have not given it this nice user experience, but it is technically possible. And, again, if you wanna export that, I would encourage you to talk to your, CSM about it and and, talk about options. Awesome. And then, Amanda had the question of, she came a little late. What plans are, are these is this available on? Was it she was curious about? Right. So, application life cycle management features are available on business and the enterprise plans with a few small differences in the feature sets. So for example, a copying of data is, available to both plans, but on business, you can only copy the sample datasets. So set up fifty fifty records. And on enterprise, you can copy the entire dataset. And separately, the solution APIs I mentioned that enable all those more advanced and more customized use cases are only available on the enterprise plan. Awesome. And then I I know this was a question that came up some earlier with, versioning as well. So, Marin was curious with, or is it possible for a pipeline to be part of only a single solution, or if they wanted to have an pipeline that connects multiple applications together, do they all need to be together in the same solution? That's also a very good question. So we only allow an app or a pipeline to be part of one solution. Imagine having the same pipeline in three different dev environments contributing to changes in parallel. This would be a nightmare for everybody, so we do not allow this. Generally, we recommend if it's, a a a system of, let's say, two apps and a couple of pipelines, you can try having them in one solution and working that way. If this is not an option because you have a bigger team, different apps, that require different permissions or something like this, choose which one you wanna have the pipeline in, and that one should be the one that you test more often and that requires more, just testing on the regular, you should keep those resources together. Alright. Thank you so much. I I think that we're gonna pause the questions here and save the rest for when we get to the q and a section at the end just so we can make sure we hit everything today, but I wanted to get a couple of the ones that came out out of the way. Thank you so much for joining. Thank you. Alright, folks. Let me just jump us forward. So what we're gonna talk about next is we're gonna take a quick we're gonna take a look at a quick demo for grid reports. For those of you who are familiar, grid but might not be familiar. Grid reports is basically a revamp we did of our report default. So when you open up any of your tables dashboards and you see a a report of all of your records, We did a big visual re visual and functional update with grid reports. Some of you may have already, opted in and started using them. They just officially hit GA recently, which is really important for a lot of organizations that may have chosen to wait until they hit generally available for their own reasons or because they weren't quite ready to make the jump. We wanna make it really clear what's changed, what grid reports are like so you can make you can make the decision to start moving over today. And so I'm gonna show you a quick demo of what grid reports can do in Quickbase. Hi, everyone. Thank you for joining us today. My name is Maria, and I'm a product manager here at Quickbase. Over the next few minutes, I walk you through what's grid reports can do today. So to start, grid reports are the next evolution of Quickbase table reports. If you are used to working in Excel, a lot of this is going to feel really familiar. They are generally available now, so if you haven't had the chance to turn them on yet, it's just one simple setting in app properties. Keep in mind that there is no deadline and nothing is forced on you, so you can turn them on whenever you're ready. So here is the report we'll be working with. You will notice the header looks a little lighter than before. That's one of the small visual updates with it. So let's go ahead and and make an edit. With a simple double click, I can edit right here in the grid without ever leaving the page. I'll now have to go ahead and add a bit more detail in here. And I also want to reassign this task because I'm not working on this task anymore, and I will not be following up on that. But I will go ahead and update the typo that I made in here and assign this task to me. And I'll also flag it for follow-up. You'll notice there is a small blue marker that appears on any cell that you've changed but haven't saved yet. That's a gentle visual cue. Once you are happy with all the changes you've made, you can save on top using the save button or undo if you would like to back out of a change that you made. Since I'm happy with my changes, I'll go ahead and save them. And now just a quick moment on layout since this is what makes a real difference day to day. As a builder, you can set a starting column width right in the field property so your users aren't stuck with a column that is too narrow the very first time they log in to a particular report. Let's do that for our assigned to column. Let's go to the field properties, find the default column width, and change it to 200. Good. It's now saved, but let's make it two fifty, just for the sake of it being a bit bigger. And from there, users can still drag to resize things themself, or they can simply double click the divider and outsize the column. That's very similar to what you'll do in Excel. And happily, it remembers those preferences the next time you come back. Row height works in the much same spirit. You can set a default and your users are free to adjust it to their liking. This can be done via the more actions menu. And currently, it's set up to condense pen spacing, but I'll switch it to normal. But it does look a bit bigger than what I would like for my report. So I like my reports a bit tighter. Let's move it back to condense spacing and, yeah, it looks much better now. And now let's talk about filtering because I think you are really gonna like this. Every column today has its own filter built into the header. Once you hover over it, you will see all of the operators plus a pick list wherever that's helpful. You can also combine multiple conditions together, which wasn't possible before. So in our case, I would like to see all of the tasks that are not assigned. So I'll select the blanks, and I'll also select all not started tasks. And now I can go ahead and assign myself to some of those non started tasks and change the status in here because I'll start working on it, mark it for follow-up, and save it. This is giving me a completely different report. Once I save it, I can also reset the filters and go back to the original report. And let's also take a look at the columns panel. From here, you can also show or hide any field. You can also drag to reorder things or drag the field down here to group by it. So let's group by status, and you will now see all of our tasks being grouped by status. And you can also pin a column so it stays in a view as you scroll. So I'll go ahead and pin the task name to the left. And this can be done via the pin column option, pin to left. And now you can see all of your tasks names. I also want to touch very briefly on performance since we've put a lot of care into it. So grid reports now run about 10% faster on average than our fastest legacy reports, which is a lot more capability behind the scenes. And you also notice one more thing at the bottom, obviously. There is no more pagination, so everything just loads as you load your report. The next part, that I want to show you, it's one of the most requested features that we've heard from our customers. Grid reports are now fully editable when they're embedded on forms and also dashboard. So let's open a project for me to show you. Let's go to our projects, and select any project we want, and you will see we have all the tasks that are being embedded. And we want to change the status for one of the tasks. So, obviously, we can go ahead and directly do it in the form. So I'll change it to, in progress because this has now been marked as in progress, and you can double click edit the same way, as it works in grid reports today, and just save it in there. So bring it together. Again, let's go back to the grid reports. Grid reports are generally available today. Any new app you create, you have them by default. And for your existing apps, you are welcome to turn them on whenever the timing feels right for your team. There is no pressure or no no forced migration. Thank you so much for your time today, and feel free to reach out if you have any questions regarding grid reports. Hi, everybody. And we're back from the demo. I wanted to jump in, and, Marie was kind enough to pass me on some notes of things we can expect going forward. So as I mentioned, grid reports are now GA. There's no forced migration for anybody. People can choose to migrate over their applications as they would like to, and there's still work going on to make sure that they will continue to get that. She had mentioned it, when it comes to, immediate priorities are really focused on, like, continued quality and publishing. Looking for fixes that need to be made for bugs, looking for any issues that are coming up. Alice, who is one of the PMs also for Quickbase, is in the chat encouraging any of you that are having problems today. Definitely reach out to us through support cases to let us know where you're running into issues. We wanna get into any issues that are still persisting and see what we can do to help you with them. As well as, another immediate priority is accessibility, ensuring that screen readers and keyboard navigation is used very much for folks who have, you know, different needs when it comes to being able to access data. That is something that is on our radar as well for making sure that grid reports continue to deliver well, support you in the ways that you need. And then looking forward further to planned enhancements, I saw a couple of you mentioned that you could run into some errors, some issues. Smarter error handling is a 100% off your radar so that you can have an even better experience with grid reports, understand when things aren't working the way you expect them to. Enabling file attachments editing as well as the way you basically the way you can edit file attachments stay in the form would be supported, at the grid report level, and then cross app embedded editing. So enabling you to make use of grid reports the way that you do in an app when you think about cross app embedding. Essentially making them more stable, more reliable, and a little bit easier to, like, put everywhere. You don't have to worry about, what you can expect experience wise from them. And then to wrap up, she passed me on two great tips to get, more out of your grid reports. First of all, who may be really helpful is if you are concerned about making the switch because you use a very big, very cluttered, very specific report, and you're thinking, like, grid reports gives me all these great new options, but I wanna make sure I'm taking advantage of them. You can go in and set your columns and your field properties. So you can set default row heights and inline editing before you switch over to grid reports. So if you're worried that the, a field might show up super smooshed or the field might show up and eat your entire report because it's full of a lot of data, you can go in and pre preemptively do that stuff before you change over. Or don't worry if you if you don't always know that ahead of time, you can also always make those changes on the file like she did in the example. A little prep up front can make it a little bit easier for you. I know I had a couple of, like, simple fields that had very short names that got a little smooshed, and I made sure to go in and give them more space so that I could read all my data comfortably. And then with, your tip two is you can use a multi condition column filter to narrow down to exactly the rows you need, then update one cell and fill it down, like Excel. So for example, somebody has left my team and I need to I need to move all of their tasks over to somebody else. I can filter down to just that person's, user, go in, change that user to the new person that may be taking over and fill it all the way down and pass all of that work from one person to the other in a couple of seconds instead of having to go in and hunt down every single ticket. Similarly, if you need to update due dates, if you need to update some pieces of information, it can make it really quick to do kind of, like, some of those bulk updates that are really nice in a grid or, you know, a spreadsheet like experience. Alright. And that is grid reports now available. And now we're gonna go into some builder enhancements. These are some smaller but really helpful things that have come out the last few months that we wanna make sure people are aware of so that they can take advantage of them. We're gonna start with, pipelines. For those of you who are familiar with pipelines, one of the first things that's really helpful is we've now had to created a handle errors block that's now in GA for pipelines. It allows you to get more control over what happens when your pipeline hits an error. Now you can drop this block into an existing pipeline and you get to choose what happens on error on success and even pull in error details like message step name, step index directly into your future steps so you can create your own workflow for what happens when a pipeline errors. For example, you're reaching out to another source and the source says, like, I'm out. I I can't help you. I'm down right now. And now you're worried that perhaps the data you're pulling over from an important, reach the data source like Salesforce isn't going to work, and you wouldn't necessarily know. You can now say, well, let's take that error message and let's use the Outlook step later on to send the error message out to my team to make them aware of this or even just throw it into Slack to make me aware of the fact that my pipeline turned into errors. This is all about making it so much easier for those folks who are managing a lot of pipelines that do a lot of integrations or automations work in the background for them. Know when things don't go quite right, and you can kind of make your own decisions. What's great about these is that existing pipelines are unaffected. None of your existing pipelines will have changed, but you can now drop the error block into your existing pipelines or build new pipelines being able to use this. This is gonna give you a lot of, opportunity to to simplify the way you think about managing your pipelines. A little more confidence, a little more ease. As a new tool in your toolbox, don't worry if you're listening to me talk about this and are like, I don't have any plan to use this. You're not required to. It's basically just a new choice that you have available to you. And then continuing in the theme talking about pipelines and making them feel a little more reliable, there is now the option to do a pipelines run preview. You can basically, go into a very specific pipeline and preview a run. It combines all the activities associated with the run and lets you run through them quickly. You'll see the execution pass will kind of open up in this image on the right or as a little pop out. You'll see the path of everything that's been executed in green as well as all the inputs, outputs, and setups for each steps. This allows you to basically quickly open up and preview your pipeline and get a feel for what's going on there without having to be like, oh, I need to go and trigger this pipeline in order to see if this pipeline works, and then I need to go backwards and read through everything to to make sure it worked the way I wanted it to. It just gives you a little less, running around in order to get to a simple, like, I would like to know what happens on this pipeline. The way I've built it today runs. How do you do this? It's pretty simple. When you to open up a preview, you can just select preview pipeline run on the activity log for your pipelines. When you're in there, open up the activity log, you'll be able to see the option to run this preview. This is just gonna be, again, making it easier for you to build them, do a quick test, make sure they work. If you want, throw in an error error block so you can make sure it happens when they don't work. But it's just giving you more ability to, flexible and rely on these kinds of workflows. And then continuing, there's a bunch of little things that I pulled up that I didn't give individual talk tracks to, but I wanted to make sure folks were aware of. Moving steps and pipelines no longer breaks your references, so you're not going to immediately have to worry about needing to go back and update other steps that reference steps when you move them, making your pipelines a little more resilient, a little more ready to be changed. Also, field name changes in the past. If you changed a field name in your app and you didn't go and update your pipeline, the pipeline wouldn't know it was looking for which field it was looking for. Now going forward, when you go and change your, field names in Quickbase, your pipelines are made aware. They are immediately update for you. So that's another, big admin task that used to drive people crazy, that they don't longer have to worry about. It'll make it much easier for them to be able to do that. Similarly, if you're collabing with other builders and you're wanting to share your pipelines, you can now export and import with account information, making it easier for you to share pipelines between your users. This can make it easier for if you are trying to give people, like, here's my pipeline. I would like you to use something similar in one of your apps, or I need you to manage this application now. I want you to take over some of the pipelines information. This is just about making it a little bit easier to collab. And then lastly, copy pipeline steps now include copy of in the name by default. This will just help you find steps that you may have created by copying other steps. If you start making changes to a pipeline and then you get pulled away and you come back if you're trying to remember what you were working on, this just makes it a little bit easier to track where you have copied steps and may need to make edits still. I always think of it as I leave the copy of it until I'm a 100% sure I like the way things have been done so that I can always go backwards and find out if there's something that I just didn't configure correctly. You know? Copy a pipeline step, make the necessary changes, do a run preview, make sure it all works, and then I can change the name, afterwards. And then moving on from pipelines, we also have done similar to, the work we did with grid reports. We've done some visual refreshes for your builder pages. If you're an active admin in Quickbase, you might have already noticed this is happening. If you've been in your builder and admin pages, we've given them a nice visual refresh with a slightly cleaner style updated font. Basically, this is just to make sure that all those nooks and crannies of your Quickbase app are more in line with what the Quickbase is supposed to look like today. What's even better is all your settings and functionality stay exactly where they are. They stay exactly the same. This is just a quick visual update to make them more pleasing on the eye and make them more consistent with everything else you're seeing. This will also make it easier when new builders come in. They won't be like, why does some quick base look like this and some parts of quick base look like it hasn't had intention in a little while? This is just making sure that everything looks nice, and consistent. And then another helpful thing for our app admins, you can now customize the message your user sees when they encounter an app level access denied error. What this basically means is if someone goes to open up an application because someone sent them a link, there's a default message that used to show up that would say, like, you're not allowed to access this application. You can now customize what that message is for each app. This will allow you to give people better guidance. For example, if you have a, finance app that you're trying to be a lot more secure about who can use it, you can say, hey. If you need access to this application, you should reach out to Jeremy. Here's his email address. You could say you need to go into this other application and make an official request. You need to go into Okta and make a request of some sort. You can basically think about, how do I make sure that I'm accessing everything, making it secure but also easy for my users to know what to do next when they run into some kind of error. And so this has just joined your app settings, specifically under branding. If you go into the app settings for your application, go into your branding section, you can then, see there's a new block for custom app messages and you can basically add a custom message including some more guidance and you can also hide the default request access button that typically shows up if you don't don't want to encourage people not to use the in app experience, but you just want them to go to another resource. Make them go to another web page, make them go to and put an IT ticket in, for example, if your IT team uses. And this is just for that app level access. So this wouldn't be on things like they don't have access to a specific table, They don't have access to a simple specific report. This is when they don't have access to an app overall, and it's just about making the provisioning process easier to control. You feel a little more in control in, of this process. And then similarly on the same train of, like, things are getting GA and are now out, we've had AI spreadsheet import out for a little while. Some of you may have tried it already. Basically, this gives you the option to build your application directly from the spreadsheets your business runs on. If you've been with Quickbase for a long time, you might be familiar with importing a spreadsheet where you can import a sheet in a spreadsheet. This, you can actually take a complex, more robust spreadsheet, that you can then upload to create your app. It could have multiple pages. It could have more than one set more than one table of data on each page, and it'll be used as the basis for generating your application, giving you a faster start. Like I mentioned, it hit GA. This is important for many folks. Their companies prefer that they don't make use of AI features before they hit GA, so they've been holding off or not using the feature until they're comfort they're comfortable with using it. Also, it has overall gotten an update to be more reliable, more robust. So you can expect that even if you use AI spreadsheet months ago when it was, still in, beta, you can expect a different experience today. So encouraging folks who are building applications from a spreadsheet they already exist, this is a great starting point. It can get you to an app that you tailor faster rather than needing to spend as much of your time on just building the structure of your application to even get started before you make it better. So just wanna make sure folks are aware. AI spreadsheet, now generally available. Or do I sorry. AI spreadsheet, now generally available. And then in that same vein, for those of you who are active Quickbase builders, you've probably heard about Quickbase Intelligence. Our intelligence package basically allows you to look at a suite of different features that help support your applications and help support you as a builder. Today that means our AI control center, app intelligence, AI agent, actions, and data analyzer. They are all they these are all features that allow you to to go from sort of unstructured data and work that might be more complicated to work that's a little bit easier for you to dig into. I think the one that I call out a lot to folks that it can be helpful for people, AI app intelligence, fantastic for if you are going into an application that is not yours, and trying to understand what it does. You know, someone's left the team, and you know that this whole process works through the app that they built. They are gone now. You need to catch up. AI app intelligence can tell you a lot about who, what, where, when, and why of your apps, giving you really contextual information on the application. Also AI actions, that that complements our pipelines, that I was talking about earlier. These are the automated workflows where you can talk to the agent and get help building out pipeline workflows if you're not as familiar with the concept of automating and integrating work. It can give you a starting point where you chat with it and you end up with a pipeline at the end. It may still be customizing. It needs your input, but it basically can help you identify common patterns. And then lastly, data analyzer. That is a great one for if you have an application full of years of data that's rich and got a lot of insights, but you might be wondering how do I get that insight out without having to hire a data scientist. Data analyzer can start pointing out important trends to you, pointing out things like, how what this manager is always assigned to work work orders that run long. I should potentially use that as an opportunity to train them. The big thing and then all of that is accessible through the agent. All you have to do when you're in a Quickbase application, as long as it is enabled for you, if you look in the upper right hand corner, you'll see a little sparkle. That is where the Quickbase agent lives. These skills are just part of the intelligence package. So some of these things will be available for you if you sign up for the intelligence package now or if you go into the package at a later date. And they solve all kinds of helpful, problems. For example, simplifying even invoice processing or risk calculations, creating formulas and pipelines to help you along on your app building, helping with budget forecasting. And these are available as an add on to your Quickbase package today. So they're available at all levels. They are an add on. Some of you might have used them previously when they were still in beta, but this is just to make sure people are aware of the fact that they are available now on GA. Then there's the knowledge layer, which will be coming in the future. And then lastly, there is, yes, for Austin, for your question, the, AI app builder using spreadsheets, that is separate from the intelligence package. That is available as part of Quickbase. Lot of you the the AI features that are about building a new app, those we keep separate because we want those to be accessible to everybody. It's more of the features that are really about, like, digging into data, automating work. That's where you're gonna see those be part of that, AI intelligence package. And then, I wanted to call it some product enhancements that are coming up. So we've already done it so that you can copy chats. In progress is your chat history, entity deletions, as well as file attachments, and then we're looking into things like traceability, saving AI generated charts, prompt suggestions. Essentially, we're looking at how can we make sure that when you are interacting with the chat, it's easier for you to trace back where things came from, and also who is asking what from your chats, as well as give you some suggestions to make it easier for you to know even what to ask for. And then also, our knowledge layer, which will be coming in the future, it's about getting answers about your business operational data without leaving Quick Base. You can basically upload, SOPs or documents that your business runs on and then use that as, you can basically interact with the intelligence package and with the agent to pull that information back up, reducing the number of times you need to leave to find that information. And then last topic, I will keep this one shorter because we're running slow on time, is extensions. Quick extensions are used to be part we basically pulled any one of our partners, Juiced, to be in house and be part of the Quickbase family. They brought a whole bunch of awesome features they had been developing for years to expand the usage of Quickbase. That's all the time that they had been working with Quickbase. That basically allows you to bring a bunch of, workflows farther than they used to be able before. Things like a more complex document generation that plugs directly into electronic signatures, messaging solutions to allow you to customize emails that go out more more comfortably or even use SMS messaging, all kind of under the same roof. Because they've joined us, you can get them as part of your quick base plan. They are an add on, so you would wanna think about, if these things make sense for you. And the biggest thing I wanna call out is when we first launched earlier this year with the, extensions, it was, Exactforms plus, Excel docs, Courier, Maps, TextMyClickbase, and JuiceSign. Since then, at Empower, we announced the the addition of PDF stamper, package builder, and PDF merge. They all just joined the package. So if you're already using extensions, you now have access to those. If you're thinking about joining use getting extensions in the future as part of your plan, these are now just part of that same package. They have simply just joined the existing package of extensions. And I believe that, is let me share this last bit. If you wanna try extensions for yourself, they are available on a trial. So don't worry about needing to be sure you want them. You can actually take out a trial. It would need to be, anybody can request a trial, but we will always need to get the trial approved by one of your account admins. So as the builder, if you wanna speed up the process of getting extensions trial for your account, you probably wanna just go to your account admin and say, hey. I really like to do this. This is the reason why. Can you go and get an extensions trial? There is a quick based extensions trial page out on the web that you can access, and we can help you work through, like, trying them out before you buy them. And, yes, as of right now, the extensions bundle is an all in one. You've if you get extensions, you get the full bundle. And then there's a certain amount of, like, usage between different plans. And that brings us to the q and a section where we can go over some of the questions that we have that are still unanswered in our q and a section. If the folks who are from product joining wanna join me up on, to help answer any questions. Otherwise, you can just kinda go through some of the stuff we have here. Hey, Yeah. Evan. Thanks for joining. Yes. Happy to. Glad to be here. And I wanted to jump in since you are since you jumped up first, do we wanna dig into some of the questions that were coming in about grid reports? Absolutely. Let's do it. Alright. So is there anything in grid rip grid edit reports that would allow us to change a field to read only when a criteria is met was the first question I can find. Criteria is met was the first question I can find. Not at this time. We have been exploring the idea of pursuing a a rules engine, basically. So, basically, like form rules, but for grid reports, it's a little bit of a different challenge. There are a couple different, vectors that that has to exist in rather than just seeing one record. Right? When you have, you know, 500 records on the page, it gets a little bit hairier. But that's something that we're thinking about. Nothing firmly on the road map yet. Okay. Oh, sorry. I should mention one other thing there. Sorry. I is one other workaround. Right? I think that's another question that's coming up in the q and a. You can use what's called custom data rules. It's not gonna give you exactly that, same functionality where it's dynamic based on another input in a field in that moment. But when you do press save, it wouldn't be able to block the save under certain circumstances that you define. So might get you part of the way there. Okay. Okay. That's good to know. That's good to know. I'm gonna say let's first know. Would cross app embedding embedded editing create a cross app dependency for a good a? good question. Those are, quite frankly, details that we haven't yet worked out with that particular enhancement. I anticipate the answer would be yes because we would require you to create a report link between the two applications. But, honestly, that's we're still, in the early stages of that enhancement, so I don't know the firm answer on it. Mhmm. Okay. That makes sense. Let's see. I have a question from Shane that I not a 100% sure I understand, so I'm gonna ask it to you. You can say you might. need more details. Is there any talk about a developer being able to assign one field on a report to auto adjust the row the row based on that one field? Similar. to how I do know more about this. Yes. great. Great. Great. I was I read it, Yes. and I was like, Yes. I'm. not quite sure I get what he's asking, so I I'm glad that you do. No. But. I think just the row based on one field similar to how old embedded and formed rows behaved. yes. So the let me try try to translate. I think this is probably born out of some, conversations that I had at Empower with folks. But the idea would be one limit one change in behavior that grid reports have that is, not shared by our legacy experiences is that we offer a fixed row height. So instead of dynamically adjusting row height based on your content, you choose a one row height that applies to all your rows. That was an incredibly intentional decision that we made, in order to make things performant and expected. I won't go into some of the details there, but one of the ways that we're considering working around that is allowing you to choose one field that would allow you to say, okay. We're not dynamically calculating every cell, you know, for the row height for each each, each row, but we're gonna allow you to choose one field where you can say, this is the one that should determine the row height. We have some, technical, exploration upcoming for that. No guarantees that that's going to actually yield the functionality. We're gonna explore, is that just as bad as, like, allowing it, everywhere and from a performance perspective, which was honestly the challenge. So we're gonna explore it. No promises yet, though. Similarly, for some of the old the long term Quickbase users, a question I have that's coming in is, will we ever get show expanded URL for this report on new styled reports? If we do, it will be different. So I hear the demand. I hear you, and I appreciate the feedback there. Moving we are intentionally moving away from the pattern of showing every, you know, field ID and then the actual data that you're filtering on, shoving all of that in the URL because that's not really secure. So if we do provide this, it would be a little bit different. It would allow you basically to see, like, the JSON that it would allow you, the JSON that we would generate for that report so that you could most main use cases, are are here are from copying things over into pipelines where you wanna understand what are my filters here, what are the fields that I'm using. So that is how we would probably handle that in the future. If we do, it wouldn't be quite the same, and we don't have that firmly on the road map yet either, but I hear the feedback. Okay. Cool. I'm gonna jump over to some of the questions that came in on, solutions, but I will get back to you if there's some more as we keep going through the list. Let's see. So, Ryan, if Ryan, for you, can a application be restored after an application was deleted? What if someone accidentally deletes an app? Can we restore the app no data from solutions? So from solutions, not really. If you if that happens, open a tech support, ticket, and tech support will help you with restoring your application together with the data. Yeah. And in general, I assume this the devices, if people run into issues with solutions, they should just think about opening cases with our teams so we can make sure that we understand what's going on. Yep. And then, Sam was curious. Is there a way to overwrite dev with production? Oh, that's another good question. Not at the moment, and, generally, not something that I would recommend. So we keep telling everybody application life cycle management is part two set power part process, and the process part is really important. So the process means make changes in dev and deploy them, to production, not the other way around. However, that said, we are currently working on a solution, for refreshing the lower environments with the latest QBL versions. If you're familiar with, the technical setup, so, environments get created, based on what we call QBL or quick based language. And since we continue issuing new versions of QBL with new schema we start supporting, or, for example, new schema that get created on the platform, sometimes you need to refresh your lower environment with the new stuff. So we're working on something about this, which will include any other workflows. But, generally, I strongly recommend keeping changes down up, not the other way around. That absolutely makes sense. Try to keep yourself from having multiple streams going up and down. Similarly, for versioning, someone was curious. Are they automatically created or do they need to be triggered? Oh, yes. Right now, it's all manual. So you need to go and store your backup, and then you can do, a a restore. However, we are also have it on the road map to make it automatic. Basically, before each deployment to production, we will start, snapshotting the the backup, automatically for you. And, when we're thinking about the environments, are they available for app admins, or is it only for realm admins there? Oh, great question. Right now, anybody in the realm can get access to solutions as long as their, app admin allows it. So there is a permission in, the permissions page in admin console where app admins can enable, solutions to be available to specific users or to groups of users. And then, doesn't matter what role you have, you get access. And as long as you're an app admin, you can add your applications to a solution. And someone was curious for the environment creation step. How does it handle formula slash formula queries that reference table IDs, for example, what if which are very likely different in the dev test environment? Oh, another really, really good question. So, generally, if you create, lower environments with the predetermined process, that we saw in the demo, the IDs are going to match. So we are going to end up having the same IDs in the lower and different environments. In those cases, of course, respectively, formulas are also matching. Now there is a an edge case scenario, I would say, where you can end up with having different IDs, which would happen if you start making changes in parallel in your production and dev environments. If you start making the seemingly the same changes in the two environments, you might end up with differences in IDs. And in those cases, then formulas get messed up and everything gets messed up, and you need to, open a tech support ticket, and we need to find a way to help you. That's one of the really big reasons we do not recommend making changes in production. It's the best practice is to avoid this in any software development, including in Quickbase, and, the ID conflicts are one of the main reasons for that. Absolutely. And then I I'm gonna move on to some of the questions we have about some of the other features. I'll come back if we have time to any of the customers that are still out there. But just anyway, we'll look through all these questions as well. I just wanna make sure that everyone gets a a fair split during our little little bit of time we have left. So someone had a question inspired by Mark, but they're also curious. Do a recent pipeline changes facilitate moving pipelines to a service account? And I will say that the being able to copy and share those app those pipelines is one way that you could say I want to move an app a pipeline from one person to the other. Sadly, there's not a one for one move. It is still a I wanna kind of, like, pull the information out of a pipeline, hand it to somebody else that could plug it back in. The other option that I think is a common reason people ask this question, what happens when someone I really relied on and built a bunch of pipelines for me leaves the company? Service accounts do have the option to, take an existing account and transition it into a service account that brings along things like pipelines. So, if you're probably asking this question because you've already explored this, but, it's a little bit easier because you can say I wanna take it away. I wanna take the pipeline information from an existing user and hand it over to the service account. It speeds up the process. There's still some manual work to be done. But that is an option. And then, obviously, like, for those of you who are wondering what a service account is, you can basically, it is a user that can be shared among multiple users that has need can be given very specific admin permissions. If you are concerned about things like centralizing who runs all your pipelines or centralizing who changes all your apps, can create a service account, give it the permissions to maintain all these pipelines, and then you can give it out to your admins who should have access. And that helps you avoid someone goes on leave for for, you know, two months and suddenly you have no idea how to change your app your pipelines. You can now have a central place to go. And then I know I saw one that I wanted to get to that was on I have the realm set to only allow specific users to use AI. Turns out when you add a user to permissions to have realm support access, the default behavior is use AI is set to true. Ideally, this would be set to false. Yes. So, Maren, with regards to the AI permissions, you wanna dig you probably wanna dig in a little bit to do if you have intelligence package or not. The intelligence package itself offers more granular controls for the permissions through the control center. So it depends on without intelligence package, it's a little bit more like, yes or no with in regards to access to pipelines. With the intelligence package, there's more granular controls to dig into. So I think that would probably be, like, the first place to start with access. And then, let's see what else we have here. Some of the same questions. I'm gonna just go through and make sure I didn't miss anything while we have one minute left. Oh, this is a good one for reporting, Alice. Is there going to be a way to see what reports are being used as embedded reports, dashboards, etcetera in the future? Yes. I was just digging into that on the side because I was trying to see what the limitation is today because I always I actually always get this confused. Right? So if you go to manage reports, you can see how often and, like, how recently a particular report has been used, but there is no way to say, hey. This is actually in the same way that you can in field usage, see that this field is used on this report or it's on this form. There is not a way to go and see if, where this particular report is used. We don't have anything on the road map right now for it, but I definitely see the value. So thanks for the feedback. And I think I've got one last question I'll I'll I'll I'll bring up, and then we're gonna wrap because we're if we're over time. So someone who's quest who's curious with JuiceTech in the past when you purchase some of these things like the SMS setup, they would help you with this. So today, what's happened is that's just transitioned where you if you have purchased it, you would start we're working with the, tech support team. So you would open a tech support case, let them know what you're looking to get access to. There's still some work we have to do on our side. There is work I know being looked into to simplify those processes so you wouldn't even need to go through tech support. But as of today, if you are using them, tech support now provides the support for any new implementations of these, they're they're the starting point at the very least for any new implementations for Joust. Alright. So we've reached the end of our time. I appreciate everybody who joined us here today and everyone who put questions in. We're also gonna make sure we look through any of the questions because we didn't get to all of them. And if anyone has anything urgent, we'll make sure to follow-up. Otherwise, we really appreciate you joining us for a future focus, and I hope you can join us again in the future for future webinars. Otherwise, I hope you have a great rest of your day. And thank you, Allison. Thank you for alright. For joining us. I know it's especially late for you, so I really appreciate you taking the time to answer questions. Awesome. Thanks, folks. Alright. Thank you, everybody. Bye,