Partner Academy Live – Shift Left

Share with


Description

In this inaugural session of the Partner Academy Live series, Partner Technical Account Manager Jenna Rios introduces Gearset’s new virtual teammate, Cam, and demonstrates how it helps partners implement a ‘shift left’ approach in Salesforce DevOps.

You’ll see how Org Intelligence allows users to investigate existing Salesforce environments, understand complex metadata dependencies, and document automations more effectively.

The session also covers how Cam assists in the development process by streamlining code creation, and how Gearset’s native UI testing tools can automate user-facing experience validation to catch regressions early in the development lifecycle.

Practical demonstrations follow a real-world customer scenario many partners experience on customer engagements.

Transcript

Partners, welcome, and thanks so much for joining us all today.

I'm really excited to officially kick off our Partner Academy Live. This is our very first session in a new series of partner exclusive enablements. We'll be hosting three sessions or these specific sessions, excuse me, bimonthly along with road map updates and other learning opportunities.

These are all designed to help you get the most out of your partnership here with us at Gearset. Now today, we're kicking things off by shifting all the way left. So welcome to shift left with Gearset's newest virtual teammate, Cam.

Today, we'll explore how Cam can help you better understand customer environments, streamline DevOps assessments, and ultimately make customer delivery a little easier.

And this is just the beginning of everything. As I mentioned, we're continuing to build out our partner education program, so we are excited to have you along for the journey.

So let's go ahead and get started here today with some intros. Just a quick intro. My name is Jenna Rios. If, you have not met me yet, I am the technical account manager here with Gearset.

I've been working the Salesforce DevOps space for just under ten years now, and I spend a lot of my time helping, partners like yourselves, with technical guidance, enablement, and customer projects.

And joining me today, you could see him on the screen here, is the lovely Jan Navratil, our amazing alliances manager. Between the two of us, we're here to help answer any questions that you might have, whether they are technical or nontechnical.

And speaking of questions, we're making sure that you have access to a questionnaire spreadsheet. So I wanna make sure everybody has this handy. What I'm gonna do is I'm gonna start to add this to my chat so everyone will have access to this. This is our questionnaire spreadsheet, sending that off right now.

Please go ahead and open it. Make sure you have access to it. The reason why we use this is so that if you have any questions throughout the session, you can jot them in the questionnaire sheet. And if we don't happen to get to every single question today, you can refer back to this questionnaire sheet. And by the end of the week, we'll be answering questions until then. So always check back in. Your question will be answered, and then we'll save that, and we'll send that off to you so that you can keep those facts with you at all times.

So, please, again, if you need questions, refer to that spreadsheet, and myself and Jan will, take some time, some breaks in between the session here today to answer some of those. And at the end, we'll open up the chat. Okay?

Alright. So if you had... Let me just double check. If anybody has issues getting that questionnaire sheet, just jot that in the chat for me. Okay? Alright. So let's get kicking off here with our agenda for today.

So first off, of course, today's session is all about Cam, so we'll be exploring Cam, which is our newest virtual teammate. This includes Org Intelligence, a little AI assisted development, and some UI testing. Then at the end here, we'll finish off with a Q&A and a fun little survey if you don't mind. Now this isn't gonna be just me talking to you for an entire hour as fun as that sounds. We'll have a few polls, some questions, and a customer scenario that we'll work through together today.

And a little bit of a background for those that are newer here to Gearset. I wanna give you just a very quick introduction to who we are, what we do, and then we'll jump into our shift left approach for today.

Now Gearset is a Salesforce DevOps platform. This platform helps teams manage their Salesforce changes throughout the entire DevOps life cycle.

This includes everything from understanding your environments, building changes, to testing, deploying, and keeping things running smoothly afterwards.

Now our goal is to make Salesforce delivery easier, more reliable, and a lot less time consuming.

And for partners like yourselves, that means helping you deliver better outcomes for your customers, whether you're working on a new implementation, perhaps an existing Salesforce environment, or providing ongoing managed services. Okay? Alright. So we gave you a little bit of a background.

Always reach out. If you want more information on Gearset features, we'd love to provide that. So always, even if it's in the questionnaire sheet, jot some things down. We're happy to answer those for you.

Now let's go ahead and let's shift gears, to the main reason why we're here today, which is why shift left? Right? When we talk about shifting left, what are we really talking about?

Essentially, we're looking at how we can move some of that investigation, validation, and problem solving earlier in the development process.

Because we all know what happens when, we discover something a little too late. Right? Suddenly, we're troubleshooting, we're reworking changes, or we're trying to figure out why something isn't behaving the way that we'd expect it to. Right?

So what if we could catch some of those challenges before we get started building? Right? And that's what I want us to think about today. How can we use Gearset to understand more upfront, make more informed decisions, and catch issues earlier?

And to help us with this, let's put this into a real world scenario.

So let's imagine that you're starting a new project with a customer.

They've been using Salesforce for years. They've got plenty of customizations and automations in place, and perhaps documentation isn't exactly up to date. And this probably sounds pretty familiar to most of you out there. Now let's check this ticket here. On the screen here, the customer submitted a Jira ticket, okay, requesting a change to their existing account automation.

Now, currently, when an account industry changes, a flow automatically moves related opportunities to the Needs Analysis stage. Now the customer wants to update that process, so those opportunities move to Proposal/Price Quote instead. Seems like a pretty simple request. Right?

But there is a catch. You're new to this environment. Right? You didn't build the flow, and you don't necessarily know what other automations or dependencies might be involved.

So before we start building anything, we need to figure out what we're working with. Right? And that's exactly what we're gonna explore later today. And before we jump into that, I wanna get everyone involved with a quick poll.

Now we've got our Jira ticket. Right? And our customer wants us to update that existing flow that changes the opportunity stages when the account's industry changes. Right?

So if you were stepping into this customer environment for the first time, what would you investigate first? Right? And there's some options here. Would you start by looking at the existing flows in automation?

Maybe you'd want to understand the dependencies or check permissions or perhaps see what other processes might be impacted.

So give that a thought.

I'm gonna go ahead and post this poll right now, and I'll let you guys decide here. Alright.

The Zoom poll is out. Go ahead and cast your votes there.

I'll give you guys, 30 seconds here. Alright.

Alright. Slowing down. Lovely, guys. I'm gonna go ahead and end this poll here. I think we got most answers in. Yep. Slowing down.

Let's share these results.

Alright. So the results were in, and this is a big one. Dependencies on the fields and components involved.

This is usually our biggest use case. I'm not surprised that I'm seeing the dependencies on the fields here. This is this is a big use case that most teams come to us for. Of course, keep in mind, there's no wrong answer here at all. I think we can all agree that all four of these options are important things to consider before making changes.

Right? And there's other things involved in that too, such as, you know, connecting with certain individuals, the architects, right, the developers, the admins. You're investigating, throughout all these different, personas as well. Okay?

So great. Thank you. Let's go ahead and move on here. Alright.

Now this is where I think things start to get a little interesting, for partners like yourselves.

Think about now how much time, right, just looking at what we just did in that last slide, how much time you typically spend getting familiar with a new customer Salesforce environment. Right? We're digging through metadata. We're trying to understand dependencies.

We're checking permissions and figuring out how everything interconnects. Right? And sometimes, you're doing all of that before you can even make a recommendation. Right?

So with Org Intelligence, we can start asking Cam questions about the Salesforce environment and investigating what's already there. So instead of manually searching through everything, we can explore the org, understand those relationships between components, and identify areas that might need a closer look. So let's actually take a look at an example today. So let's dive in.

Now we're looking at a Jira ticket here, that our customer, right, we've already kind of, looked at earlier. Our customer wants us to make a pretty simple change to, their existing account automation.

When that account's industry changes, they want their open opportunities moved to that Proposal/Price Quote. Right? And as I mentioned before, this sounds pretty straightforward, but we're stepping into an existing Salesforce environment, and we didn't build this automation. Right? Before we start making those changes, of course, we need to understand what's already there, how it works, and what else might be impacted. Excuse me.

So let's put Cam to work. Alright? So let's jump into our Org Intelligence here. We're gonna use Org Intelligence in Cam to investigate this existing flow, explore its dependencies, and see what we can learn before making any changes.

And as I go through this... Let me go ahead and jot this down real quick.

There we go. As I go through this, I want you to think about how you could use these same capabilities during customer discovery or possibly a technical assessment with that customer and perhaps helping to scope those conversations.

Alright. So let's see what we can dive into here.

So let me ask a pretty simple high level question to Cam. Find the existing flow that updates related opportunities when an account's industry changes.

Nothing in-depth here. We just wanna see, hey. Where is that flow? And perhaps investigate further on what it does.

So we'll just go ahead and kick that build off. And while Cam is searching and sifting through our Org Intelligence metadata, I'll go ahead and just kinda discuss this page here for you. Now Org Intelligence will essentially take a snapshot of your entire environment. That can be any environment that you have integrated into our Gearset application.

And it's simple to integrate a Salesforce org. It's by OAuth, very simple. Once it's in, can then take that snapshot. That very first snapshot is gonna gather everything in that environment.

And then every day after that, it'll essentially take iterations of your environment.

So daily, it will be updated for you, and you can change that setting as needed. You can also filter anything you'd like. So if you're working on a small subset of metadata and you don't want a whole snapshot of the environment, although that is probably best use case, you can definitely make some exclusions as well.

So we can filter our metadata types through here if we'd like. We can click on anything here and have a visual representation of that metadata type and its dependencies.

But looking at Cam, Cam's built everything out for me. So now what has Cam brought forth? The flow. So this is what I had asked. What is the existing flow that updates related opportunities?

Well, it's provided the account industry change. It's also providing what it does and two things to check on.

And so, again, this is relevant information based on just a very simple question.

So let's start investigating a little bit. Now, of course, I can ask Cam for the question, which I will soon. But let's dive into this flow because we wanna understand this flow a little bit more.

Now let me log this out there. Now there is a beautiful visualizer called our Flow Navigator. Throughout Gearset, even through our comparisons from org to org, we're able to have access to Flow Navigator. And what this does is it gives us this great and wonderful visual representation of our flows. Our admins love this. This is a very exclusive feature to us. And the nice thing about this is not only can I see it here, but I can go into a full screen, zoom in, zoom out, and I'm able to select any portion of my automation and see the logic within it?

So I don't have to now go into my Salesforce environment, find the flow, and then make sure it's the correct flow that I'm looking for, and then, of course, start digging into the logic within it. I can do all of that here.

Cam can even start digging in deeper depending on the questions you provided so you don't have to go all the way into this space. But, of course, this is going to help you understand, the points of logic that it points to. So something important to note.

Now, of course, this is something we would typically see. So just so... For some reference, we end up seeing this XML file, which is very hard to navigate. So very happy to have this. This is very useful.

Now aside from this, we also have the access to its dependencies. What is what is this flow dependent on?

You can select anything in here and also read the same values as you see here in our header, for any of these dependencies listed.

We can also see permissions and change history.

And the lovely thing about our change history is any changes that were made in a past deployment here within our application, you're able to see exactly what those changes looked like. So it essentially gives you the comparison for that.

Now another nice thing is documentation.

Now a lot of the times, and I think I've mentioned this prior in one of our slides here, is when we're working with a new customer, a lot of the times, their, documentation can be fairly stale, and they haven't updated it in quite some time.

So the individuals that were working on it kinda have the knowledge of it, but what if they're not there anymore? Right? We don't have anything updated for us to refer to. So the nice thing about this is our documentation lives here in our documentation space, and we build that through utilizing this Explain item tab below. And what this does, it essentially sifts through, this particular metadata type, and it it explains for us what it does, how it works, and any technical details that we should be aware of.

And so now not only do I have an updated, documentation type, I also can add this to my documentation, which you see here in the background, or I can copy this, and I can update my customer's knowledge base.

So now everyone in the company has access to a refreshed knowledge of, this particular metadata type, but also everybody that utilizes the Gearset application, who is investigating something similar in their environment or perhaps they're working in the same environment, they have the same information across all personas.

So very useful, very big use case.

We get that quite often that teams do use this to update their content. So that's very nice, good to know.

Now, of course, we have this short description as well. We can edit this, or we can have our AI, which I already did, update that for me so that we just have a brief description here. And then, of course, we can move forward with our investigation once we've gone through everything in our flow.

So what's next? Right? Well, what's next is now investigating further. So I've I've found the flow.

We've looked into the flow and the logic, the dependencies. Everything seems satisfactory. But I wanna investigate a little further. I wanna check for dependencies, and the potential impacts of changing anything, to those dependencies or this flow.

And I also want to ask Cam, hey.

You know, Cam, when we're finished with investigating, can you kick off a build for me?

Perhaps Cam can build this for me, and then I won't have to worry about actually making those changes.

So if everything looks good, let's do that. But first, let's check for these potential impacts.

And I'll go ahead and kick this off to Cam.

And this is a good point in time for me to pause and just see if there's anything in our questionnaire sheet that is outstanding.

Alright. No questions thus far? Alright.

I'll just remind everybody, refer to the spreadsheet any questions, and don't worry if we pass the subject. We'll come back to it. And then perhaps if you have questions that linger and, you know, tomorrow you go, oh, I wanted to ask this. You can still put it in the spreadsheet. We will answer it all the way through to Friday. Okay? Alright.

So let's jump back in here.

And we have our... There we go.

Lost my page there for a second. Alright. So what did we ask? Check for dependencies for potential impacts of changes. If we're to if we were to make changes in this flow, what happens?

So what Cam did is they found nothing in the org that should block this change. So that is good to note. So right off the bat, I think we're...

We have some solid changes that we can go ahead and start building. But Cam also checked a few things. Values exist, so provide that result. What uses the flow, other flows on opportunity, etcetera, etcetera.

So it's providing a pretty in-depth response for us, so that we can have our checks to make sure that when we start building, perhaps we should consider these other things. The change that could occur, it'll provide that and things to decide first. Okay? So it's providing some suggestions that are orderly when we start making changes.

Okay? Now the lovely thing about this is once we've decided to move forward, everything's been investigated. Well, I asked Cam, if everything looks good, can we kick this build off? Well, we're getting ready now to build this.

So Cam's saying, of course, let's build it. Which environment would you like this to live in? So I could simply select this space.

I can then go ahead and I can select my pipeline. So through Gearset's pipeline and automation, CI/CD, we're going and choosing which pipeline, you'd like... You'd prefer this to go into.

Then the environment. So, obviously, we'd like it to go into a specific environment, a dev environment, that, will then move into your integration dev work. From here, you can connect that, and we can simply kick that build off.

Alright. Now before we go further, let's go ahead and jump back into our slides here.

Alright. So let's take a step back here.

So now that we've used our Org Intelligence to investigate our customer's environment, We now have a much better understanding of the existing flow, how it works, and what might be impacted by our changes.

So what's next? Right? Well, this is where Cam can help us move from understanding the environment to actually making those changes.

So Cam can assist with development, which you just saw me kick off now, helping us create or modify supported Salesforce code and metadata.

And while we also have... And keep this in mind, I put this in the spreadsheet, An MCP connected development workflow available now.

We're gonna kinda stick to what Cam can do, on its own. But keep in mind for those of you out there that have interest in that, yes, we do have access to external AI connections through MCP. Okay?

So let's start to see where Cam takes us next. Okay?

So we'll jump back in now if my cursor wants to let me.

And I have a... I think I have a question here from Fernando. Yes. We will have a recording available for you, Fernando. Thank you.

Alright.

So we've kicked off that job from our Org Intelligence, and it's providing that, hey. And you might need a little bit more context so we can actually include more into the messaging.

Or if we take a look at some previous assigned work that were created, if you were suggesting certain certain motions in your build, our agent will also prompt you to answer some questions, so that it can continue building accurately. You can also ask it something else. So this this next step is essentially the build to help you move forward and streamline that coding process, that development process.

And once it's complete, once we've built everything out, we'll build it through, and we'll open it up for review.

So once our Cam agent has built, you can then go ahead and review. Again, we can have insight into anything that it has built. You can still see that logic within it just to double check everything. We have code quality checks as well.

So static code analysis is...

Some of you may not know we have our own, static code analysis tool, code reviews that will...

If implemented, it will check those static code analysis for you. So any Apex issues, SOQL issues, things like that, and it'll let you know if it passes or fails. And then, of course, what changes were made. Last but not least, we're gonna go ahead and insert where we want this to go.

So if you wanna make sure that this is in the correct space for your branching, you can, you can maintain this as that's what we start with, or you can change it if needed. Then we can create that pull request.

That pull request then takes us into our pipelines, which will then have... Be set up already for you to go ahead and move forward to your integration space, which then you have all of your automations to take place.

And that includes everything from UI testing to Salesforce tests, etcetera.

Okay? Now let's sift back.

Now we've seen Cam, help us investigate the existing Salesforce environment and assist with that development process.

But now I'm kinda curious here. Thinking about your own customer projects, what would you want to ask Cam? Maybe there's an existing flow that you'd like to understand, perhaps a dependency that you're trying to investigate, or a change that you're maybe not quite sure, how to approach yet. So what I'd like to ask the team here today, is if you can drop your ideas into the chat.

I'd love to hear what kinds of challenges you're running into with your customers.

And while you get those responses, we'll go ahead and get ready to start moving into our final piece today.

So I'll go ahead and just give you guys a brief minute or so to pop those into the chat. While we do so, I will check our spreadsheet. Alright. Alright.

We got something. Here we go. Automation chains. Fairly easy to understand what happens when one record changes, but far more complex to understand what changes triggered by that change trigger respectively.

By that change trigger respectively. Yes. The whole chain of triggers and flows that are called ah.

This is great. I think this is an important thing to think about.

There's a ton of different use cases, and I think that this is... This brings me to, like, the next piece too is, you know, if we haven't had a chance to look into our cam, these are the types of use cases that we would really, really want, especially partners like yourselves, to utilize, because your feedback, really does help our teams, our internal teams continue to build, better processes. So, absolutely, thank you, Patrick. This is... If you haven't if you haven't had a chance, let us know. That way, you know, we can have that discussion with you to provide the trials that are needed. Our partners, anyone that partners with us, you you have a chance to, gain access to these Org Intelligence to Cam, and trial that out. So lovely. Thank you so much, Patrick.

And, again, if anybody's interested and hasn't used Cam yet, you can jot that in the spreadsheet as well.

Alright. Cool.

Let's go ahead and move into UI testing.

Alright. So we've investigated our customer's environment. Right?

We've identified the existing automation, and we looked at how Cam can help us make the requested change. Now we need to validate it. Right? And this is another important part of shifting left. We don't wanna wait until UAT or production to discover that something isn't working as expected.

So with Gearset's UI testing, we can automate testing, of the user, facing Salesforce experience and catch potential regressions earlier. So let's go back to our account industry scenario and see how we can we can validate this. So let's move into our UI testing. And before I get in here too, keep in mind, this is native to Gearset.

We built this to make the lives of our...

Of all personas easier. Typically, we would need, someone to develop a script, to create these processes. And so what we're doing is making this more accessible to all teams, okay, and making it simple. So keeping in mind, this depends on the specific environment that we need to test.

So if this is integration before you hit UAT, we wanna check this out, make sure everything's working as it should for potential profile or a specific user, of course, because at the end of the day, UI testing is about what that end user sees and if it's accurate.

So we'll go ahead and dive into this environment here, and we'll choose the user. So you have the option. You can choose by role, a group, right, whomever the end user is that we need to test for. So we also have individual user as well. I'll stick with just myself as I'm the only one that lives in here anyhow. So on the right here, we're gonna see that we are now connected to that Salesforce environment. We've chosen a user, and now we have some additional steps here that we can choose from.

So right off the bat, we have record screen. Now this is nice if, you want to just get in here and start, creating that use case yourself. So I want to build a new account. Right?

You can go in, and you can select account. You can select new. You can...

Right? And it will record each and every click you make so that you can then use that as your testing, scenario.

However, we wanna make this even more simple with Build AI.

So that's what we're gonna use today. We're gonna build this using our agent so we can create a prompt and then take off and do whatever else we need to do and come back when it's done. So that's kind of the nice thing is we can utilize the agent to streamline our processes for us. We'll get to that in a minute, but we also have reuse existing tests.

Now this is lovely if you've already created some tests. And whether they're the record screen or the build AI, you can reuse the tests, and you can continue to build off of those tests as well. So if you have recurring tests that need to be done to make sure that nothing was broken in the new changes you made, it will rebuild that test for you or reuse that test for you. And if there were any additions that were created to that particular process, you can just add on to it. So that makes it super simple, for us to move forward with any of these tests that we're building.

So let's start with building with our agent. I'll go ahead and select that, and we'll start.

Now let me grab my prompt here, and I'll make it a very simple prompt here today so we can take a look at it. But, basically, what we can do...

And this is nice. They give you some, like, pretty basic use cases that are typically used so you can use those and add to them. But what I'll do is I'll ask my agent to simply create a UI test that changes in account's industry and saves the record for us. Okay?

So what we'll do is we'll just run that. Now as you can see, we're connected, and you can see the agent starting off here. So they'll start to build those changes for us. So start seeing some movement happen in here.

And in the center column, what we're gonna see is that recording of those steps that are being implemented here.

And at the end of this process, we can go ahead and name this. So I'll start now. I'll just put new demo two here just so we have that, and we can save this.

Another thing we have up here, as you can see, is our cleanup. Now this is a newer feature we had, again, from partners like you who help us with the feedback that we get from your use.

We needed something that after these tests, we need to clean up all those changes. So we can actually turn this on. So right after these tests are completed, it will just go straight to your, Salesforce Recycle Bin. So you can turn that on anytime and just keep it on if you'd like.

Now as we can see here, we've built a template of the process that we need to utilize for testing. You can also add assertions. So if there's any specifics that you need to add to this, you can do so as well.

Now what's nice is we can rerun it, make sure we're good and happy with it. Again, you can go ahead and clean up the the test after it's done into the Recycle Bin so we're not carrying any of that, heavy load.

And, of course, we have our test cases here that if we do want to add this to a particular template for future use, we can do so as well.

So with that, I can go ahead and save this.

We can go ahead and, add a description. As mentioned, we can go ahead and clean up the test data post run. That's what we would like to do. I'll maintain that. And, of course, we can add this to any of our folders for whatever tests we're gonna be running, because we can add this to our pipelines. So if you are using Gearset Pipelines, you can add this simply to, one of your folders for the associated environment.

And you just simply save that. Now if I go back into my testing space, I can now go ahead and show you this is where our folders live. As you can see, there's quite a bit living in here.

When a specific folder is added to a test job, okay, which can be in your CI job, okay, Those will run anytime you have a pull request to that, environment. Okay? And this is automatically run. It provides pass fails.

So I'll jump in here and just showcase that. So in this case, I have some core workflows that I run in my, UAT environment, and we can see that we've had some passes and some failures. So this has been great for, partners like yourselves where customers want to understand what failed and why. So we can select these, and you can open up any failures here, and we take snapshots of that.

So, some teams, the stakeholders, would prefer to have access to things like this so they can actually provide the steps and they can provide these snapshots to the team. And then what's even more lovely is your team's been working on this. We have a failure. We need to fix it.

Well, we can add to a ticket.

So if you already have an existing ticket for this particular change, you can just add this to the ticket so that they can go back and repair this. However, if this is, something new, and you need to create a new ticket, we add the summary for you, the failed UI test, a description of that, failure, the error, and then we can simply create that ticket. So now our team has a way to streamline the process in which they need to repair something.

So some few things that, again, partners had asked for in the past, and these are just things that we've added into it to make it more efficient for teams to utilize.

Alright. So let me go back here, and let's jump... Actually, let me... Before I jump back into it, I wanna see if there's any questions in our questionnaire.

Alright. Man, this is... Alright. I'm sure questions will come up later. Again, jot them in there. I'm the type of person who ponders quite a quite a while, and then I'll think of something later on. So that's what you have it for.

Alright. So let's jump back into our deck here.

Alright. So, team, we've officially come full circle.

We started with a Jira ticket.

We used, Org Intelligence to understand the environment, explored how Cam can help us make changes, and finished by validating those changes with UI testing. And that's really, what shifting left is all about. It's understanding more, catching issues earlier, and making Salesforce delivery easier.

Now bringing this back to our teams here, to our partners, think about how these capabilities, that we discussed today could support your own customer engagements. So whether you're doing initial discovery, scoping a project, building business cases, or actively delivering, changes, the goal is to help you work more efficiently and deliver better outcomes for your customers.

Alright.

Now we're going to do one last poll, with the team today. So after seeing everything today, where do you think these capabilities could bring the most value to your customer projects?

Let me go ahead, go ahead and ponder that, and I'll go ahead and post our poll. Alright. So go ahead and cast your vote. We're really interested in understanding where you see the biggest opportunities. And as I mentioned already, multiple times, this feedback, from you, from teams like yourselves also really helps us shape the future of, our product, but also this Partner Academy Live, session that will continue to happen bimonthly.

Awesome. Oh, we're getting a lot. That's okay.

Give it a few more seconds when it slows down.

Okay. It's got in that fast. Very nice. Alright. We'll end that poll. I think we're there.

Let's share the results. And the results are in development and delivery efficiency.

Again, this is the... Usually the biggest use case. And, yes, this is very important.

And we're happy to see you. Again, there's no wrong there's no wrong answers to this. There... Every every single engagement is different, but the development and delivery efficiency is usually the number one reason why we need something like this. Right?

So let's go ahead now, team. Let me go ahead and stop sharing those results there.

And let's head to the end here. This brings us to the end of our very first Partner Academy Live session.

Jan and I are, happy to answer any remaining questions that you may have, and we'll go ahead and open up that chat. If you guys if you guys would like to speak with us, I'm happy to open that up.

Just go ahead and raise your hand. Or if there's any questions you want to ask now is your now's the time. We have a few minutes here.

Alright, team.

Well, I think what we can do, as as mentioned, please utilize that that spreadsheet.

All questions are good. There's no bad questions. Any feedback, you're you're you're welcome to put on on the spreadsheet as well.

But, again, thank you all so much for joining us today. We hope you found some useful takeaways that you can bring into your own customer projects, And we'd, really appreciate you taking a moment if you can to complete our feedback survey. So you could take a snapshot of this q... Excuse me, this QR code for that. I'll also send the link as well in the chat and in a follow-up email.

So last but not least, you know, keep an eye out for our our upcoming partner newsletter and the future enablement sessions. Road map series is on deck too, so keep that in mind. If there's things that you'd like to see, just let us know. Okay?

So I'm gonna go ahead real quick, and I'm just going to add our survey into into the chat, and then I will send you all on off. Here you are, team.

Alright, team. The form is in there for the survey if you would be so kind.

And, again, thank you for joining us, team. Please, please join us for our next session. Keep an eye out for that. Okay? We appreciate your time, and we hope you have a great day.