Hi everyone. Welcome to our presentation of Sitecore XM cloud forms so Kamruz and Mike will demo as well as present on this topic. Take it away, guys. Hey, thank you, Akshay. So welcome everyone. Thanks for joining us. So we're going to be introducing to you Sitecore XM cloud forms. This was released, like just a few weeks ago. So my name is Kamruz Jaman. A lot of you will know me from Twitter and socials as Jamie Kam. I'm a 12 time Sitecore MVP, and I've been working with Sitecore since the end of 2009 and I started working on Sitecore since I Version 6.0 My name is Mike Reynolds. I am known as the Sitecore junkie in the community. I am a 10 year Sitecore MVP. And I started working on Sitecore 17 years ago, on version 5.2, and I've worked in every version ever since. I hadn't even heard of the Sitecore at that point. Mike, I don't think I even knew what to say, muscles, to be honest with you at that point, but you went for it. All right, we're going to jump into this, and we're going to talk about the history of forms and the site, core ecosystem and layout as it existed over iterations of many years. And also talk about this new product that we're featuring here, XM cloud forms, and why you'd want to use it, key features and benefits that come with it, and Kamruz is going to give us a nice deep dive in a demo and future enhancements that are in store for us. Alright, so here's a timeline that we came up with, but I think what's missing here is a brief historic view before 2009 in asterisk that almost were kind of kind of not. Anyways, MVC support came out in 2014 lots of bells and whistles, lots of additions. Eventually, people wanted more. So Sitecore came up with a new product called experience forms, completely a rebuilt solution using MVC, and it was built into XP later on, as the world moved ahead this, we started to people wanted the ability to do this and react and other places like that, other front end frameworks. So Sitecore came out with JSS react forms. Today, we now have XM cloud forms. So of course, we, we did, yeah, 2018 we were in Germany. We're up on a stage in front of 600 people. You know, we're up there. Couldn't see anything. The lights were dark, but we were up here showing experience forms, and that was a pretty deep dive. And I know when I we were discussing about this earlier, I reminded you that you push me. I don't say bully, but you did push me into presenting a very deep dive into web forms of marketers, or it's actually Michael West had been asking for some information on it because it was not very well documented, or the way to expand, enhance, etc., wasn't, you know, there's barely any documentation.

 I know you have extensively blogged on web forms or marketers. I learned a lot from you actually on creating this custom submit actions and things like that. But, yeah, that totally slipped your mind that you present that, and you joined that presentation. I did forget all about that. And you know, I started to remember it after we discussed this, like, oh yeah, I did do that. Michael, if you're on here, I actually coaxed them to do it because I didn't want to present. But anyways, I. Yeah. And I think as each of these versions went on, the documentation obviously did get a little bit better. And I know when we had presented on the experience forms, we had discussed the fact that it was the very first release people were comparing web forms and marketers to, or what was the end, the very last version of web forms for marketers to the very first release of experience forms. And we're talking about, you know, well, they don't have this, and they don't have that, and this is missing, and that is missing. And we had talked about the fact that was a very fast release at that point, right? I mean, to be fear at the time web forms for marketers had been around since 2009 we did this in 2018 forms came out in what 20 was the 2017 2018 and it's just like, okay, multiple years had elapsed. Of course, there were lots more features and experienced forms. Was a brand new product. It wasn't going to have all the bells and whistles that web forms for marketers had. It would have taken too long to, you know, roll that out? Yeah, and certainly it was a great improvement, especially on the user interface and the development of that so, I mean, you'd obviously mentioned that the prehistoric view. So why do, why do the forms matter? Why do, why do authors want these things at the end of the day, it's because they want the ability and the empowerment to build forms without a developer. Why? Because, well, developers are busy that we have to build lots of different things. Things have to be prioritized. There's competing priorities. 

You know, they want to roll things up quickly. You know, just think of like systems out there, like, what is it? Survey Monkey. You can just build a form really quickly and just put up a survey, you know, drag and drop, do all kinds of crazy stuff. If you need to rely on a developer to do everything, you'll never get your form out there, and you might get, let's say, left behind, because somebody else is going to release something. So it's all about empowering content authors to build these forms without a software engineer, developer or an architect or somebody technical. They also can make changes on the fly without having a developer make those changes for them. You know, for instance, I want to change a label on a form, I should be able to do that without a developer. Also, you can have this integrate with multiple different systems, you know, we're going to go into this a little bit using web hooks and show that, but you can have it integrate with disparate systems and have things happen, you know, without a developer doing it for you. And likewise, you want to be able to throw your form out there quickly, because you might want to get more leads, you know, you might want to find more customers, or you want to open up channels for customers to talk to you, then you want to do that really fast so that you don't lose those customers to competitors. Yeah, absolutely. And I recall, like on some of my earlier projects, Sitecore and non Sitecore projects are deployment like deployment practices just say we're not as mature as they are now. And so making a change and getting that deployed into production would often take several weeks, I know, obviously, with automated DevOps tools and things like that that most people have these days. It can be much, much quicker, but it still doesn't hold, you know, change management processes and approvals and QA rounds and all these different things that you know, yes, it might be faster, but still you can be stymied. You want to get that thing out, like, right now. You don't want to wait, like, to the end of the week or the end of the sprint or whatever. You work that out immediately, absolutely, yep. And I have to say that of every single Sitecore project that I have ever worked on, this is a module in web console markets or experience form. This is a module that every single one of them has used, without effect, without fail, they always want this, and it's always included on every single project, right? Forms, a report, yeah? So, yeah, we're going to talk about XM cloud forms. So I have added a link to the documentation down here, there is some user documentation available on this already. They are pretty quick with getting these documentation at this state. These days. It is just a user documentation at this point, but it's take a look through it, and what is this? QR code on that screen. It's just a URL, okay, yeah. All right. So XM cloud forms is a SaaS based product built into XM cloud. Things in the cloud so that you just integrate it into your cloud based solutions. It's composable, so that means you can integrate it to different disparate systems. And it's definitely all driven by a headless paradigm. 

So it's all API driven, which is great, low code, no code, basically what I've seen so far, you don't need to write any code, but maybe there are, there would be a case we have to do some but for I would say nine times out of 10, you probably don't have to write anything. And honestly, like I just mentioned, since it's SaaS, you're going to delete this and create some site work. They control the whole thing. You just have to go use it and have fun. Yeah, and we've seen with XM cloud already, that Sitecore is constantly releasing updates and enhancements to that system. They've already stated they're going to be doing the same with XM cloud forms. We'll talk later about some things that we think would be nice to have in here, and something that potentially are missing right now. But again, given that it is a cloud SaaS system, I don't expect those things to be sitting there. Unlike experience forms, where you're waiting, we were waiting basically a year before the next release, for the most part. And there's other modules, you know, we don't have those issues with upgrades and well, even just the upgrades itself, right? If they release the module, you've got to go through the entire upgrade, split system across maybe Dev, test production, go through all the QA. You don't have any of that, right? This is the beauty of SaaS, or composable. Yeah, you get the latest greatest immediately. Once it's released, you have it, you know, it's going to be 100% tested already, hopefully, and then you just go have fun with it. And even if there is bugs. The great thing is, of course, those things can be fixed very, very quickly by Sitecore and rolled out without you having to do anything about it. Great. All right, so we're going to take a look at this in a demo. But, you know, I can attest that there is a very slick Form Designer, builder. We can just drag fields, form fields right onto a canvas, change labels, do all kinds of stuff. There's multiple ways of putting your forms together. We'll go into a little bit more detail, like a little bit, but you can easily, like, test this in different device views, different view ports, like a tablet or mobile device, or you can see it on a desktop, or maybe even, like a big service. I don't know, but you know, there's lots of this. It's easy ability to do that. This buttons on the canvas where you can view it and see things like that. You can also just hook a into so there's no more submit actions. Everything's through a web book. So you can have your data post somewhere else, different system. Maybe you can have it post a Sitecore, or connect, or something like that, and just have that handle it. You don't have to worry about building those things anymore, because I remember in experience forms, that's the only thing I worried about, was building the Submit action that had to integrate with different systems. And you know, that could be hard if you didn't know what you were doing. 

This is a standalone product. It is not integrated with Sitecore, 100% per se. It is its own contained form builder and form solution. It is completely different than site or experience forms or any things that came out with site or like that. It is just standalone product and definitely easy embedding onto web pages. Yeah, I can't believe this. You're saying there's no more submit actions. Mike, because that was like I used to do. What am I going to do? Exactly? What are we going to do now, I know, save time to go to the movies. So this product comes with a bunch of pre camp field types, or form fields. You can just take them, drag it right onto the right, into your Canvas, and just build a form. You know, I saw different things, like date fields. I thought, like drop downs. I saw like things for integers, numbers, just radio button lists, things like that. You can also set validation on these fields, and it's very easy to set that change the labels of your form fields very easily. And also, there's a ReCAPTCHA field so you can prevent robots like me from filling out your forms. And also, definitely, this is something that probably should come with lots of forms, is a way to lay out your form so you can have different columns forms and things like that. You don't have to worry about setting CSS classes or anything this. This is already done for you. You just drag it on to your canvas and start putting form fields into different boxes. Very simple. Yeah. And I remember with experience forms that the form build over there was, you know, much more flexible than we. Add in by console marketers, right? But you had to start going in and knowing bootstrap classes and things like that, right, to get your 5050, widths, and you know, 1/3 2/3 widths and so on and so. So this one seems much more intuitive, right? Even as a developer, I struggled with that. Yeah, yeah. And definitely, you can see things in different like viewports different screen sizes. It's very responsive, you know, you can have it work on a mobile device or a tablet or your desktop or little tiny laptop screen that I have in front of me. You know, it's responsive. And this is my favorite feature of any form builder, is multi pages, or aka wizard form. So you can have different pages of form elements, so you can step users through, let's say multiple pages of form stuff. Let's say you, you know, have five pages of stuff. You don't want to put everything on one big screen, because they'll be scrolling forever and probably fall asleep while scrolling. You want to have them stuck through it, so you can group things together and have them be kind of like together, you know, make it easy and digest it, and then, as most form builders, at least this one, definitely, you have pre canned form templates you can use. You can create your own. But these give you the ability to start with something. It's just like a here's something out of the box. I can actually put it onto a page and start changing things. So I don't have to go remit the entire wheel and just start using it. And, you know, some people need that as a startup point, because they don't know what fields they want. They know they want something similar to what's already there, and they just use that as a baseline. Yeah, it's great for also branding, right? So keeping your brand on theme, on target, and making sure that they you have brand consistency across your forms. And you know if you again, just very, very allows you to very, very, very quickly just set up a new form, change a few little bits that you need to for the specific use case, and just get it up and running. Great. I uh, in web hooks. So no more submit actions. You're just posting to an API somewhere else, and that's all through web hooks, interfaces and things like that. It's basically just a URL you post into a URL, and that for that system that you're posting to will handle everything, and you have the ability to put it behind authentication, so that you won't have any hackers still in your stuff. You don't have to worry about sent, you know, storing sensitive information.

 Another system is going to do that, and somebody else probably already made that iron client and it's ready to go. You don't have to worry about doing any of that stuff. Yeah, we were, especially when you're when we had the forms, you're always worrying about the data, the storing on your own systems, security around that, the PII, implications of that, and depending on which, which country you're in, which location you're in, which state even you're in right, that that has different legal implications around people's right to access that information and for you to give them that information. I mean, there will still be those concerns here, but you are not storing it on your servers, and you not having to worry about all the encryptions, and you know, the ability for that data to potentially get hacked. For I remember, at least for web forms for marketers and experienced firms, I wrote code to encrypt data to store it into the database. I don't have to do that with this, you know, I mean, I enjoyed writing that code, except, you know, you have to worry about, what if somebody can crack your encryption algorithm. You don't have to worry about that with this. But do you do you remember on web forms, marketers, there was a credit card field? Yes, I do, yeah. I do remember that, and that was stored in plain text in the database, yeah? Yeah. You know, hackers dream, right? Hackers dream Exactly. It's a trip down memory lane, and you have the concept of pages, which is exactly what it sounds like. It's just a page, and you're dropping a form into it, yeah, super simple, right? Super easy for anyone to just throw that in there. I was surprised at how easy this was. Yeah, all right, let's crack this thing open and take a look. Take a look. Let's do it. All right. So here's an instance of XM cloud for. Button. First, there's new on the new instances, you'll see the forms button. Surprisingly, this was pretty much exactly where the forms button was on the on prem, X and XP. So it should be that unfamiliar for you all that will take us to this, to this new forms builder application. You'll see it is a separate application, forms, dot Sitecore, cloud.io, it is, as Mike mentioned, it's not tied to your XM XP instance, like the old experience forms. Or it is a separate, standalone application. Really, really intuitive. We were able to just go in without really having to read the docs, obviously, but just go in and start playing with this, start creating these forms. Straight off the bat, Form Builder, as Mike mentioned, there's the layout sections on the left. You can start pulling those sections into the start adding those onto the form. And then you can, again, just build up your form as you need it, then start adding in whatever sections of content and things like that that you, that you however you want to build up your form. As Mike mentioned, there's a number of out of the box field types in here, and again, you can just start dragging and dropping those in here. Or you also have the ability to add, to click the Add button. And then from that, you can start to also add the fields in that way. Number of different field types in here, Mike mentioned a few of the special ones. There's that date one that you had mentioned Mike that in here. And then let's grab an email one, right? So pretty simple, pretty straightforward. Click on those. It gives us an entire property spin. I can set up a name for the field, update labels there is some placeholder text you can update, and you'll see that it's very, very quick, right? Like I can see all of that information is just being displayed straight away. I'm able to preview exactly what I'm building without having to hit any saves without having to hit any refreshes. Simple, some of these, but there are a number of options here. You can set like prefilled values, like essentially default values. You can make fields hidden required, and again, as you can see, as I hit required, it's populating those up very quickly. I can set character limits. I can also update field styles individually. 

So I can update the field styles in terms of background, colors, borders, fonts, font sizes, font styles. Same thing for the labels. I can show the labels. I can hide the labels. Updated placeholder text, same with the help text. I can do that individually. You've also got this applied to all which will you see. But just applied it just hit all of them. Pretty useful when you want to make quite generic form style changes, like if I want to make the label, update the styles of the labels, and I want to do that for all the labels, and I want to go into those individually. It's very, very quick to go and do that. Mike also mentioned that there are some basic UI elements in here as well. So I can go in start to add text here. I can take the styling on there. I can take the font colors on there, I can add multiple of these, set that in there. Pretty neat. And then we can add those other special things in here, like the reCAPTCHA. That gives me a basic form very, very quickly set up very, very flexible in its design and its layouts, different column widths, different column sizes. We can go and then add another. Page in terms of the multi page setup, you'll notice that that submit button that had been added up here, probably not the best place for that, down here, has now become the next button down here, this way of setting up the multi page, it was really, I really like this, and it's taken my first page, pre templated. Pre templated it for me, and just created a almost a duplicate with the placeholders and everything in there. I was pleasantly surprised by this and how easy it was. But, yeah, we'll take it. We can individually, obviously, control, control these. We can remove what we don't need in there, and then we can start to add our fields back in again. A couple of different options. We can go in and add the fields, click on the field, type. This gives me another set of fields, and then we can add in that in there. This gives me different options for different types of fields, different selections of fields. Right with that as an example. So that's quickly set me up a multi page field in here, you will. So I've got a couple of select field types in here. One again, I can go in, change all the styling, change all the labels. I can make them required or not required. And then I have the option to, then have the ability to add selections to these right and you will notice that I can only add static lists of static list. Here in experience forms of my formal market is when I have these multi list type things, I have the ability to either set them statically or to go and select a data source location from within Sitecore. We don't have the ability to do that. Here it is a separate, standalone list. And the reason is, this is a composable solution. It's a standalone solution. If they start to start to make things integrated with Sitecore, through data sources and so on and so forth, it defeats the purpose of it being a composable solution. I can't just, you know, it's hardwired and tied into Sitecore, if we do that so the standalone again, you know each field can have different each field can have different options, different selections, different requirements that you as you need. And then we can add as many of those multi list, multi pages as we need to need a lost my page on here, but so number of different fields, number of different options that are available.

 It's very, very easy to create these. I have an error here. It's quite Inc as it is quite intuitive in what it's doing in terms of, you know where it's adding the next buttons for the pages where it's adding those buttons and things like that. And it's quite intuitive in showing you when you have issues on the form. So I'm getting an error here, and it showed me a warning that the recapture field should always be on the last page, which makes sense, right? I don't want to recapture on the very first page of a multi page form, particularly given that it will then just essentially expire, right and the user won't be able to submit that recapture at that point. Let's get that recapture in here. We can add a new text field. Inc, clean this up a little bit. Haven't removed too much. Again, we have the ability to add character limits and things like that. I do know limit of 2000 characters for the long text field. Did I fix that? Action Buttons? Missing action button so I can then save and exit that and my form is now. Are available on the list that I've just created. Pretty neat, right? Very, very quick to do. We can add multiple labels already have a label set up, and I can create new ones if labels do not exist. And that makes it quite neat, nice to be able to then start filtering my list of forms by different by the different labels, or you can also filter by status and by name as well. Now these are all inactive and in draft mode at this moment, so they're not available to use right now. But it did want to before I do that, I want to just show you that. Yep, ability to for the template library. So we have this template library. There's five out of the box templates available, sample templates available. I do have the ability to add favorites and save some ones myself, but these are the five public templates that are available, maybe it would be I can preview the templates to see, give a quick look at what it looks like. It's just the ability to preview those in in the different modes. And I can obviously just use that template. And that gives me, straight off the bat, a way of creating a template using, using one of those predefined templates, I can still go in and, you know, update this layout. I can still go in and add additional fields or text or whatever I need in here. That's not, that's not a big problem, but it gives us me, gives me that really, really quick starting point to work from what I can do, which is quite neat, is this template, this template that I've just designed very badly, but I've designed none of this. I can actually go and save that as a template and pull that I'm template. Give that a second. Let me save that. Template has been saved. Let's go and create a new demo form. Go back to the template library. Go back to the old templates, not the public ones. And this is a demo that I had. This is a template that I had created a little bit earlier, right? Let's close that. Let's just use this template. I have a brand new template created from the original, original one. I can make, obviously, make whatever updates I want. I can add, remove fields to this. I can go and add additional fields to that. Not a problem. Super easy, super quick.

 Once I've got the branding assigned to this, it gives me a very, very consistent look and feel to everything easily to spin up new templates for whichever landing pages, sign up pages that I need, which one also just pull out this styling section, so we saw the field styling earlier. This gives me form styling. So this is for the entire form. So I can set like the width of the form, borders of the form, backgrounds of the form, including the ability to add background images. I can select files local to have a local, recent one here, direct links from the website. Nice, nice little integration into Unsplash. Give you some, some royalty free images in here, Giphy, because I love some Giphy. Not sure it's always going to be relevant for the business forms and the lead Collection Forms. But we love giving nonetheless. And you can also hook those up into Facebook, Google Drive, Dropbox, Instagram, OneDrive as well. So if you have you know, you'll meet your existing media assets in some of those, you can at least hook those up and select it from there without having to browse from those locally. Again, no integration into the Sitecore media library. And again, for the same reason, it's a composable product. You don't want to have that those hard ties back into the XM XP system, and then you also don't want to worry about I published this form in. Are those items in site for also published? You know, whether that's the media library items or data source items for fields and things like that. So this is a correct approach. It's different from what we've been used to. But in my opinion, this is a correct approach for a composable form builder, application. There's a number of different things in here. Check those out. It will give you some nice consistency across your forms. You want to set, like the default fonts and things like that. Set it here that will then sort of be inherited by the by all the form fields and things like that. One, including things like button colors and things like that. One thing I did notice is you have to set these first. So I change the button colors here, for example, scarish, it doesn't, doesn't apply to the forms until I add them on. And in this case, I'd have to remove it and then add it back in there again. But it's now following that starting. So if you set the styling first, save it as a template that will then give you some more brand consistency. There's also the appropriate the ability to add your social media links. There is a component in here, the basic one, I think, or social media. So again, add those in, and then that will give you the links and things for social media and things like that. In there already. There's also validation messages. If you want to edit those, it's very generic in terms of the messages. You don't have a perp field validation, but you can have, you can override the validators and things like that. Another nice thing within, within this builder as well, is there isn't a workflow, but you can go in and add comments. So if you're not here to know what's going on, just did this again. Get rid of that bugginess. Yeah, so the commenting, so you can, if you hit the comments, you can go in. This gives you a new commenting field so you can update. You can add comments on the different fields. 

It then gives the list options, and that builds up the list of items, and somebody can come in and then fix those. Then you have the resolved and the unresolved tickets, and then you can obviously add to yourself individually, comments individually or within groups. And gives you a nice way of having that workflow without having to do a huge workflow implementation on those forms are responsive, so we can go back, so when I'm editing, I've got a desktop view and a mobile view. I've also got this preview view as well, again, some data, but that will give me a mobile view, tablet view, desktop view, very, very quick, very easy. I've got, you know, all my history of the different versions of this site that I had, and the ability to look at some of the settings come back to this web hooks in a second, but the Submit actions again, as Mike said, there are none, pretty much if you've got two which is redirect to a URL, again, a hard coded URL, and not something that you select from within Sitecore itself, and A success message, which you can and show success message. You can obviously edit that, and that will then show a success message in place if you don't want to redirect to a separate Thank You page or something like that. Obviously, if you are selecting a redirect to URL, you can set whatever URL you want with whatever parameters you want. So if you have like UTM codes and things like that. You can add that into a Google direct URL and send that over to a thank you page so you know that that form has been completed. So submit actions. The Submit actions are now web hooks. So you can go ahead and manage web hooks and add as many web hooks as you like. You have authentication. You can, you can set different types of authentication. I'm going to show you a quick one for this one, I'll probably pick up a demo so you can, for demo purposes, I'm. For testing purposes, you can check this site out called webhook, dot site. It will just give you a unique URL, and you can post your forms to this for testing purposes, go and set like this, define this one, this one that Ben brings my demo web hook and I can save and exit that probably okay. This is going to be an easy one to do. Demo, so I don't have a web hook on this one. So if I try to submit this one, it's going to tell me that I don't have a demo web hooks. I try to preview this one sometimes I don't have a web hook set up. So I can go ahead and do that, select that demo one that I just did. Let's go back to preview. I'm so used to hitting save, it's becoming a little bit weird. So, all right, so I've got a name, I've got a email address, I've got a thing so I could submit that. It tells me what it's going to be submitted, what it's going to submit, the payload is going to send, where it's going to send it to, and the headers it's going to add, I'm going to hit submit. This has submitted this number. Thank you. Set up. Now, if I go to this webhook dot site, you can see I've just had a post come in, and you can see the data that it just submitted. Really, really easy, really quick, to set up email address, keyboard layout. There you go. I submit that sent and look, there's a another one that just comes super easy, super simple. Now with the web hooks, let me show you this little, nice, little demo set up. So, as Mike mentioned, with the web hooks, with the Submit actions, I think we spent 95% of our time just working with creating custom submit actions and pushing that out to different systems, whether that's email, whether that's a Salesforce, whether that's to some other custom application, some other database, etc, that was, I think, the majority of the work that we used to do. 

Now, the neat thing about web hooks is you just push it to some somewhere else, an integration platform, and it's then the responsibility of that integration platform to handle that data. As part of our presentation for subcon in Berlin, we had created a web hook Save action which posted into Slack. So in honor of that old presentation, I did want to just go ahead and show that I built that essentially that same integration, but with absolutely zero code. See them now, robots and in this case, I've got a web hook into Zapier submit that submitted this the success message shows here, rather annoyingly. It does show at the end of the form, and it doesn't hide the existing form and then just show the message. I think that's an improvement that could be made. Now if we head on over to Slack, you can see I've just posted that message using my company integration, again, zero code, exact same way, exact same thing that we had posted in Berlin, but zero code and this integration, from a forms perspective, I have a web hook set up to point to Zapier. In Zapier had this web hook with just, really, just two events. I got a trigger event which captures, which is that web hook URL that I added in in forms, and all it's doing here is it's just capturing the event, and then it's then going and posting that into Slack, and I've got a payload, and I've formatted that payload using the fields that have come through from the. From my Sitecore. Forms integration, webhook integration, the fields are the fields on my form. These names do matter, so when you are setting those up, make sure that you name those form fields nicely and neatly. Again, if you do this using a template, the form fields will be the same name every single time. So that's using this field here, and then it's just posting that off to Slack, to another API that we have set up in Slack. This integration platform can be anything it could be. I use API here people that use if, TTT, if, if this, then that very, very old and well known integration platform, and of course, Sitecore connect, we did a presentation on this several months ago. So if you're using Sitecore connect, then that's another option. And then maybe in the future, Sitecore will be adding some recipes for connection between these again, with these integration platforms, you can do as many actions as you like. 

So I posted to slack. I can send an email. Again, the good thing about these integration platforms is they already have a bunch of integrations. I don't have to write any code. I can go and post it into Salesforce, HubSpot, Marketo, whatever those things are you can. You can go make those integrations happen without having to do things very, very do things manually and in code, we're getting close to time. But last thing you can obviously, then you go ahead and use these Inc Sitecore on Sitecore, XM pages, XM pages. Just be sure that when you do this, you have to go and save and activate your form. Once you have activated a form, you cannot edit that form again. I don't know the reasoning for this, but you cannot edit that form. It's been it's activated. You can't delete it. I can duplicate it. I can create templates from it, but I can't delete it. I can't deactivate it. But to add this to your website, so I did have this pre loaded, but I will just refresh it so they have the component list. Once a form is active, there is a forms section will appear here. Notice that you get the nice little thumbnail auto generated, and didn't have to do anything. You can just drag that in, find a placeholder, essentially, wait for it, and it's loaded Simple as that, right? I didn't have to do anything more than that. It picked up the four bits, XM, cloud and pages in the display instance picked up the fact that, you know, we're integrated with forms. We have an active form available, and it's ready. I'll see how quickly it can publish. But any thoughts on that Mike before we get into the next set of slides? Well, let's say somebody wanted to make a change. What did they do at this moment in time? Nothing. Unfortunately, you would have to just duplicate this form and then go ahead and swap it out. This is pretty, pretty slick, pretty slick, pretty slick, pretty easy, pretty quick. This may take 30 seconds or so before it shows up. So we're gonna, we're not gonna wait it will. It will eventually show up, but it's usually, I've been seeing us within a minute or so. Oh, there you go. Quicker that, right? So this is now in production. I can Okay. Submit that both we success, successfully submitted, and again we can check out into, I bet it's not active, but that will appear in that, in that, in there, in a second, as well, simple as that. Alright, future enhancements. You know what's coming right now, the it doesn't support multilingual. That's on the roadmap, hopefully coming also conditional logic. So you know, let's say somebody selects something here show different form fields based off of what they selected, or something like that. So kind of conditional, like, if else whatever, to make the form do something different depending on those selected before right now, all of the form fields that we looked at are out of the box. We there was a little custom section. It, but there's nothing under it. Hopefully something is coming so you can build your own custom fields. Should be interesting on how that's going to work, since this is a SaaS product, I'm not sure how they're going to do that. Maybe it'll be some kind of JavaScript sort of thing.

 I don't know some analytics right now. There's no analytics on the fields or forms. That was with experience forms and webforce markets. I can't remember if it has something like that, but anyways, that's coming with this. Now, keep in mind, this is brand new. You know, everything they're still, you know, cyber still working on it. More revisions will come, more versions. So you definitely can expect analytics to come with this thing because it had come with previous form builders and then JS embed codes so you can read this on pages in other places. Maybe that will come. That'd be nice for it to come. Yeah, there was some mention of this within some documentation that I saw if you've used things like Marketo forms or MailChimp and things like that, they usually have this, like other script sniper, they can drop in there. So I think that maybe something is going to come. And maybe this is what it's doing in the background anyway, through pages. So I did see mention of that, so I think something might be coming for this. Yeah, that sounds like the next step. This is things that we would love to see wish list. I hope somebody's listening. As we mentioned, you can't change a form once it's activated. You know, once it's active, that's it. You stuck with it. You have to duplicate the form and make the changes on the new duplicated version of that. It'd be nice to edit those, if possible. We would love to see that, because I feel like that's a big pain point that you can't edit the form. Let's say you make a mistake, you know, and I don't know, I'm just making this up. Somebody has a typo in a form label, and everybody just flushed it out the door, and we thought it was great. And then you have a typo. Oh no, I have like 50 fields on my firm in this five pages, five pages of like 10 fields. 

Now I have to duplicate the whole thing. And anyways, it'd be nice to see the ability to edit forms once they're active. Also, we did see the labeling system where you can label things and group them together, but there's nobody to archive a form you don't want to use anymore, just put it somewhere else, maybe, and recall it later and put it out to use later on. There's no way to do that now. Also confirmation messages. Don't hide the form. It'd be nice to hide the form to show the confirmation message, or even the error message or something. Because right now, let's say you have a really big forum, it's going to be at the bottom of the page. It just seems like the whole form should just hide once your form submitted successfully, or maybe even on error, and you can't migrate your forms across different environments. That'd be a nice thing to have, because it's, you have to rebuild your forms on every environment, which some people might not like that anyways, just saying it'd be nice to have that in the future. Also, I'm also not Chuck Norris, right? I don't, I can't just do stuff in production. And, yeah, exactly. You know. I mean, some people with experience from some people were doing that. But for most, you know, places I've seen, they were building it and staging environment first, and package, packaging it up and installing it into pride so that you don't make a mistake and mess things up. Anyways, that'd be nice to have for the future, also building a form using API, you know, maybe like call an endpoint to create a whole form that might help out with some more automation and things like that. And then some kind of recipes of Sitecore connect that just work with web hooks that would be nice to have that, you know, maybe this is a nice segue to enhance Sitecore connect, to offer those that ability. And then, last, but not least, AI generated forms. Now, this almost sounds like science fiction, sort of soft, but it is coming. AI is starting to change a lot of what we do and what a lot of things that we use, maybe AI could recommend form fields based off of what you already had. Yeah, so we'll take the floor for any questions that might have come in. Your mute actually, but I can see the question, yeah. Sorry, yeah. It says, Is it really standalone? Would I be able to use it with inside core XP first and migrate my solution to XM cloud later? If I would? Yeah, so is standalone as a. And like when we were creating the form, we're not going and creating items in Sitecore, like we used to reSitecore experience forms, right? They would create that tree of the form sections and the fields and field options and things like that. So it is completely standalone. From that perspective, like I said, we don't have a way of at this moment in time. 

We don't have a way of embedding it in non Sitecore pages application. But I expect if we, maybe, if we dug in, we find an embed code that we could, we could take and then use that on site, core XP, XM solutions, much and if it's not there already, I think it will come in much like a similar way, to say, a HubSpot form or a market type form. And then the second part of the question is, does it expose forms layout as JSON slash API that you know of, not that I've I haven't looked into that, and not that I know of at this moment in time, but it's not going to be in the same layout, I don't expect, as the current headless layout. Yeah, right. This doesn't make sense to have that tight integration like that. All right, so the next one is XM Cloud Support. Forms data store internally, or can store it in a third party system using web app normally, I think it's probably, he's probably asking something similar to what it does in the Yeah, only externally. Only. It was externally. So you can't, like from the Forms application. I can't download a list of submissions, for example, because they don't hold any data. It's often a bad system. And then you do whatever you want with it. If you're using an integration platform that could be store it in OneDrive or a SharePoint form or Google Docs, and then go and push it into X, Y and Z, right? Again, just be careful with PI data with that case, all right. The next one is, what's the migration path? Migration path is an intern, I guess we could have a hackathon category on this, but I don't wasting time on that. Yeah. And then the next one is, you know, is sensitive data encrypted? Not that I could see. Yeah, it's not encrypted because you need, yes, yeah, basically, you're, I mean, they obviously you want to use encrypted connections with HTTPS and things like that. But it's not, it's not encrypted. You know, before it sends it. And that is all the questions we have so far. Guys, that was a good presentation. I learned something. So Mike, what did you, what did you think about the overall forms and the new experience compared to compared to previous? Well, this is fast. It's very easy to use, very intuitive. There's no messing around with CSS fields or things like that. It just seems like it's so quick you drag things and then it pops the old form builders. Just seemed like it would take a while. 

There's definitely some refreshing going on in some of those older platforms. And saving was fast. It just seemed like the whole experience was quick. To me. It seemed very intuitive. It seemed like what you what you see, is what you get. You drop like, let's say, the designer column sort of thing, onto the form. You saw where things are going to go. You know, that wasn't always the case with the older form builders. I like it. I definitely do like it a lot. And you know, definitely having the data not live in the same platform also makes me feel better, because you don't have to worry about it. Yeah, because, I mean, if people are getting hacked all the time, or comedy is getting hacked? People are walking out with databases. You know, you definitely, I think that putting that over to a company that has, you know, a plan for that kind of stuff, is best. We have one more question, how can we make customers, a customer field types, is it possible right now? It's not okay. Hopefully it's coming in the future. You know, it's definitely on the roadmap, but at the moment, it's not there, yeah, or it might be possible they just haven't shared the documentation yet. So there is user documentation available, but there isn't the developer documentation yet. It'll be interesting to see how we tackle that, but yeah, being just to see how that is done. But it's coming because there is that custom, custom field section right as you say, great. So if that's all the questions, we're back on time as well. Was one o'clock so perfect. Thank you everyone for joining. Hope you enjoyed the session, and obviously feel free to reach out to myself or Mike, or if you need help with any of your Sitecore projects. And feel free to reach out to the Konabos team as well. Speak to everyone soon you.