Hi everyone and welcome to today's FirstSpirit Product Office Hour. As we have a packed agenda, let's get going. On the cramping side of speakers, we have Matthias with us. Matthias is the team lead customer support FirstSpirit Germany and he's going to cover the section about customer support. I am Timo and I'm going to cover product for FirstSpirit specifically. You might have noticed that we have two more speakers in today from our partner Formcentric. They will introduce themselves in a few minutes when they go through their section. On today's agenda, we have the following items. We will start with a short intro for the ones who are joining for the first time, cover a few maintenance and setting related items. Then Formcentric will take over and walk us through the newest advances in their product. Customer support, that is Matthias, will then talk about best practices and how to get the most out of their service. I will then take over once more and talk a bit about modisite management, the newest advances there with back transport of content. Also new in AI, that is going to be the assistance. But also something that we call agentic AI plus AI workflows. At the end of the session, we will then have a look at the roadmap and I will give you a bit of an outlook also in terms of upcoming events. As always, the session is recorded. And as always, we try our best to monitor the chat. So if you have any question, please reach out there and we will do our best to answer that. In the session itself, if we can't do that, then we will do our best to provide an answer afterwards. With that said, let us have a look at the sun setting items. So here we have OCM2 that we will stop maintaining because OCM3 is here. If you ask yourself, what does that mean for you as you're using OCM2 today? We have a migration guide. We have documentation. You see that we have a migration guide behind the QR code here on the right-hand side. Fragment creator is another one. The fragment creator will go into maintenance mode, is already in maintenance mode. And the thing that we are doing is if a critical bug or a security relevant topic comes up, we will address that. Other than that, we are not touching that anymore. Also, most recently with the March release, the cloud availability is happening on request for fragment creator. And we will stop providing it. And we will stop providing it altogether by the end of this year. If you have questions about that, don't hesitate to reach out. Then on a general note about Java 21, and we will talk about that a bit when we speak about Smart Search in a minute, this is the next default JDK that we are aiming for across the board when we speak about First Bird. On Smart Search, the team has released the newest version. That is version number five. It is here already. It's been here already since the beginning of the year for on-premise customers, for cloud customers. It will be made available very soon. What does Smart Search 5 entail? It entails improvements in terms of performance, security, and also full Java 21 compatibility. That means solar, Zookeeper, Zookeeper, all of the components, all of the libraries, all of the libraries, full compatibility with Java 21. What do you have to do as a cloud customer? Nothing. Because we do the update for you. There's one thing we recently sent out an email about that topic. If you're interested in exporting, storing statistical data related to Smart Search, because we will introduce a cutoff date with the jump from the recent version to the newest one. The email tells you how to do that. The email tells you how to do that and how to get active if you're interested in that. Home-centric. Before I hand over to Andreas and René, I wanted to touch on the timeline here because we are cooperating on that topic as we have a shared customer base. We want to tell you when, what will be available. So we aim for making the form-centric, so that is the 7.x, and our partner will tell us much more about that in a minute, a version available after we've done the latest update to Webform 6.6.10. We aim to do that with the patch day in April, so with the first spread release in April. You see down here the date for that. We are aiming to make that version available because this sets us up. two, two, update to form-centric, and that is excluding customization. That is crucial to emphasize here, excluding customization. If we talk with customization, again, we need the Webform 6.6.10 version, and we aim to provide that in the April release. And this then sets us also up to have the form-centric, including customization version. That not during the month after, but rather at the beginning of the second half of this year as our current plan. And then we also have the headless scenario. So headless we treat as neither a part of the vanilla, so that means without customization, nor the customization update, so the one that you see here on the left and in the middle, but rather this is an ongoing topic that we are treating as a separate Web app. So here we are aiming for a second half of the year release. I'm going to give you a second here if you have questions or remarks about that before I hand over to René and Andreas. All right, no questions about that. So please take it away. Thank you, Timo. Let me share my slide. I hope you see the slide. Looks good. Okay, thank you. So my name is Andreas. I'm managing director at FormCentric, and with me is my colleague René. René is the team lead for the SPIRL team. And he will answer the questions. So that I'm not disturbed and I can tell you whatever I want to tell you. So I will give you today is a very short introduction to FormCentric. There will be something new for customers that already know Monday Web Forms, respectively FormCentric. And especially there will be something new for customers that already know Monday Webforms, respectively FormCentric. And especially there will be something new for customers who don't know FormCentric or Webforms at all. So there will be everything, something for everybody of you. So we'll show you what is FormCentric, then topics about migration to FormCentric 7. So what has to be done or why should you migrate, etc. And then I will show you a short demo, and then we will have an outlook what will come next. First of all, I want to clear some confusion, which may be around because we changed the name. You probably know Monday Webforms, our product was known as Monday Webforms orms until version 6. With version 7, we changed the name to FormCentric. We did this due to mainly two reasons. First reason, Monday Web Forms is a very much too generic name. For example, you can't get a trademark on the word Webforms. And therefore, we change it to FormCentric. The other reason is that in addition to our logo, Monday Consulting, so Monday Webforms was developed by the company Monday Consulting. But especially because of our logo, there was often a mix-up between Monday Consulting and Monday.com. So we changed the name to FormCentric. And during that, we founded the FormCentric as a company, FormCentric GmbH, which is 100% daughter of Monday Consulting. And during that, we changed the logo from Monday Consulting so that it separates from Monday.com. So in short, FormCentric 7, formerly known as Monday Web Forms, is a product developed by FormCentric today and in the past developed by Monday Consulting. I hope this was not confusing. But yeah, it's often we get the question, what is Monday Webforms or what has Monday Webforms to do with FormCentric and so on? So FormCentric is a new version, formerly known as Monday Web Forms. So what is FormCentric for those of you who don't know FormCentric? FormCentric is a form builder, which enables your editors to create forms on their own without developers on a very easy way. And they can create dynamic forms. Dynamic forms means that they can create forms that adapt to the user input. For example, it can be fields that are hiding or displaying again or in total pages. So you can create a business process that includes 10 pages and the student only sees three pages. On the first page, the student only sees three fields from 10, for example. What makes it for the customers, for your customers, makes it much easier to fulfill the forms. In addition, we've got inline validation, which means that the form fields are validated immediately after the user and has added as input and therefore you'll get a good data accuracy. With FormCentric 7, we have accessibility, which means reader support and full keyboard control with the new templates and with our headless server. I will explain that later on. Then we have a component called analytics. Then we have a component called analytics. With that you can track the submissions of your users and you can analyze then completion rates and so on and so on. And our editor, as mentioned, is a no-code editor with functionalities like drag and drop. And you will see that later on in the demo how easy it is to create complex forms with our editor. So that's FormCentric. So that's FormCentric in a very short overview. FormCentric integrates into FirsSpirit very deeply and very seamless. It integrates in the cloud and on-premise. It integrates in the content creator and in the site architect. So wherever you want to use FormCentric in your FirstPirit system, you can use FormCentric. And that's bring with it that the forms are stored as content, which means that you can do everything you can do with content in FormCentric, you can do with the forms. For example, things like version control or rights management and so on. You can do that with the forms in the same way as with every other content. And the analytics data. And the analytics data. So the data your user submits can be stored even if you're in the Crumpy Cloud, can be stored on-premise. So the analytics component can be stored on-premise on your site. And so you can host it so that the data is only owned by you. This picture shall give you an overview of the development. Timo just explained the timeline regarding the Crumpy Cloud. It just says we've got Monday Web Form 6 and FormCentric 7 in the wild at the moment. Most customers are on Monday Web Form 6 or on the verge or have just migrated to FormCentric 7, especially or only on-premise. Timo just explained the timeline for the cloud. And if you want to have analytics, you can deploy that on-premise. So regarding the migration to FormCentric, why should you migrate? One reason that is not explained on the slide, but which is quite obvious, is we are developing from FormCentric 7. We are going on with FormCentric 7. So Monday Web Forms 6 will be at one point not supported anymore. Not next month. Not this year. But at some point, of course, we will go on from Monday Web Forms to FormCentric 7, FormCentric 8, and so on. So at one point, I think you will have to migrate. But you get a lot of things with FormCentric 7, for example. And the most important point is you get a lot of things with the most important point, and the most important point is you get a headless server, which gives you much more opportunities. We have got a bunch of new functionalities. I will show you on the next slide what is, for example, part of FormCentric 7. User-friendliness, especially in the editor, is very much better. I will show that in the demonstration. And so you get out-of-the-box accessibility with the new headless server and the corresponding corresponding templates. So in detail, improved data editor, and we've got support for capture, recapture, and friendly capture. Age capture is coming. We've got new form elements like a signature field, which will be enhanced. We will see that in the roadmap, form element for pictures. We've got new sliding themes. I will show that in a demonstration also. So another kind of theme. We've got new validators for page level validators or credit card validator. And we added support for Elasticsearch as an alternative for SOLAR. So when you're using form-centric analytics, you can choose whether you want to use Elasticsearch or SOLAR for the search functionality in analytics. And analytics got a facelift. So what do you have to know if you want to migrate from or to FormCentric 7? You need a new license file first. Feel free to contact us or Chromepeak to get a new license file. The forms will migrate automatically. And after they have migrated, you can use your forms with the standard or with the new Headless Web App. So they are both compatible. So they are both compatible. You can use whether standard, old, the actual web app or the new Headless Web App. And the Chromepeak will also have an automatic update. If you've got to migrate your development workspace, we have a guide for that. You can find that on our homepage. But we offer to migrate the workspace for you. We made the experience that it's a good idea that we migrate the workspace. Not because it's not possible for you, but because it decreases the number of tickets in our support. Therefore, this fixed rate is so low because we've got an advantage. You've got an advantage. I think it's a very good idea. What you get there. What you get there. What you get there is a migrated workspace. What we can't do is everything afterwards, for example, the testing. So if you want to migrate, please talk with your supplier and we can do the first steps and the next steps will have to be done by your supplier, of course. Okay, then let me switch to the demonstration. The well-known smart living. We've got a self-service here. And here we've got some forms, contact, appointment. Let's start with the appointment. See a typical form with a dropdown and some text areas which are mandatory. Telephone number where there's, for example, a telephone number validating. So we can't see data. We can't add text here or something. Email address, date picker, and so on and so on. Typical form elements. So how does this look? Let's look in the editor. Now see the editor. On the left, we've got a tree view where all form elements are displayed in their order as they appear in the form. You can change the order via drag and drop. And on the right side. And on the right side. You see all properties that are necessary for this form field. For example, text field test. Is it required field? Is it read only? What's the maximum length? Default value and so on and so on. For every property, you have a hint. So if your editor is not quite sure what this property is for, he can have a look at the hint. Or of course, you can have a look at the hint. You can go to the plus. And simply choose one of the form elements. For example, input field. This is a good way if you only want to add one or two fields. If you've got more work to do, you can pin the element selector. And here it's very easy to choose more. And here it's very easy to choose more fields. Let me remove this. Otherwise, I've got too much errors. So, then if you create an error, for example, there's no technical name, You can see the error sign on the upper right. And if you are, for example, on, oh, no, that's not what I wanted to do. If you have, for example, somewhere else, and you can't find the red dot, which is quite helpful, that indicates where the error is, you can open the model where the errors are displayed, click at the error, and you are right at the point where the error has been. So, you can see the error has to be fixed. Fix the error, and you are fine again. And you can close and save the form again. What we've got in addition to the creation of the form are actions. You can pin this also. I will do this so that you can see them. We've got an email action, which obviously sends an email with the submitted data to whoever you want the email to be sent. We can choose which form elements the email should contain. Select all and then all form elements are included into the email. You have got an analytics action, which sends the submitted data to analytics forward action media store and data source action. These actions store uploaded data into the media store or into a data source. Obviously, we've got a PDF action. There are PDF can be filled with the submitted data. There are PDF can be filled with the submitted data so that you get a ready PDF and this PDF can be sent to you or to the customer and or to the customer. And a webhook action. Webhook action can be used to connect form-centric to other applications. Same system on the left side, you see what actions you have and on the right side, you see the properties with the end. You see the properties with the end if you need them. And the same functionality. If you are on your way to create the form, you see, oh, I've got errors. Open the error, click to it and you are directly at the point where you have to fix the error. Now we'll delete. So I don't have errors. What we have to fix the error. What we have new in form-centric 7 is that you can change the theme. Just to remember, this is how the form looks now and now I will change the theme. For example, a box CPR. I will save form. And tada, it looks completely different. Just by changing. And then I will change the theme. Dark. And now it's dark again. So let's go now to the career. What we've got here is in form with a different theme again. Different theme again. And this is a sliding theme. Oh, mandatory field. So you can go back and forward and have a sliding effect, which is quite nice for forms that you can separate in smaller parts, but where you have more than one or two parts. So what I want to show you in addition is that the, that we can add some fields here. If I choose here advanced certificate, these both fields are added, which are not shown by any other. And how's this done? This is done by a conditions. Can see the condition in the editor. Condition is quite simple. So it just says if the form element is selected. It's selected. It's selected the advanced certificate. Then show this form element and show this form element. Form element. So it's quite easy. For example, let's add new input field, which is called hobbies. Give it the name hobbies. And then I add a new condition. Add a new condition. And I say, if what's your name? Starts with A and D. Doesn't make any sense, but just to show you, hobbies is visible. Now I remember I wanted hobbies to be a required field. I've got no errors. So I can save the form. And now what you can see now. And now what you can see now is I add a and D and the field hobbies appears. Hobbies is now a mandatory field, which does not mean if I add that. This one mandatory. The field is not visible. But it's not mandatory. That would be a problem if it's not visible. But you don't have to think about that the system does this for you. You don't have to add a condition that says if it's not visible, don't make it mandatory. That's a part of the logic that the system does for you. So that's all I wanted to show in the demo. In this very, very short demo, there's much more, which we don't have time for now. So if you want to have a demonstration that shows everything, just contact us and we will make an appointment. So let's now have a look at the roadmap. What's to come. We will add a single sign on integration for analytics. And we will add front end development workspace. The front end development workspace makes it much easier for front end developers to create new themes and templates. Yeah, they will be very glad to get this. And we will add new form elements. And we will add new form elements for geolocation, for example, or a new form element for data privacy field. That's shortly to come. And we will enhance the signature field so that you can add certificates so that you can create real secure documents. And that was a very short introduction to form-centric. Thank you. Thank you very much. Thank you very much, Andreas. Let me just have a look at the chat here. If you have questions or remarks, please do bring them up. Also, if a question comes up at the very end of the call, Andreas and Rene will stay. And I see the first one from Francisco. He asks, is it possible to customize the form style in greater detail? My answer is yes. And Rene can give you the wrong answer. Yes. So in support of Andreas' short answer, yes. In both versions, in the classic versions, in the classic version, it's mainly free marker or JSP templating. And in the headless, in the headless, in the headless world, there is a JavaScript library with specific hooks where you can hook yourself into and style everything. So every form element, there will be a callback where you can register yourself and completely style your elements the way you want to have it. Thanks, Andreas and Rene. And thank you, Francisco. Do we have more questions or remarks? All right. As they say, sometimes silence is golden. So let us go back to our presentation. And you should see the Crown Peak Customer Support slide here. Because Matthias is going to take over. Matthias, please. Hello. I'm Matthias. And I'm the team lead of the German FirstSpirit Support Team. I work for Crown Peak for over seven years now. And it doesn't get boring so far. The customer support team is on the road with its employees in different time zones, thus ensuring 24-7 support. We are here to help you. And this applies to all Firstspirit products. And we do not shy away from accompanying topics like Tomcat. With a very broad knowledge base, we cover a wide range of topics. But our core competence lies in finding and solving errors. I would therefore like to briefly mention here that topics such as templating, best practices, or module deployment, are better dealt with by our professional service. However, we will not turn you away directly when it comes to such topics. Our expertise is only more limited here. If in doubt, submit a ticket and we will assess it. And we will give you an honest feedback. Next slide, please. There are things you can do to help us help you faster and more efficiently. For example, a description of the problem that is precise as possible helps us to get straight to the analysis. If the description is too briefly or too vague, we may make unnecessary rounds in the ticket to obtain this information. The same applies to a step-by-step instruction. If you know how to reproduce the problem, such instructions help us to speed up the analysis. And this helps us to speed up the analysis. And this helps us help you faster. If you specify the version, for example, it helps us to decide whether it's possibly a bug that has already been fixed or something completely new, be it in First Spirit, Tomcat, whichever module is affected. And not an important point is often forgotten. If the urgency changes, the urgency changes, please let us know in the ticket. Please let us know in the ticket. A short information. Hey, this is urgent for us now because x, y, that this helps us to shift the focus to your ticket. It's not always clear for us to know is a classified ticket as high classified ticket really important or more important than another high classified ticket. But the reason you give us will help us to assess the situation much easier. Next slide, please. These points also help us to find the entry to the ticket more quickly. If you have an error message, you're welcome to provide it a screenshot in the ticket, but please also copy the text. Our developers, for example, can quickly move through the code with the stack trace. It's much more difficult with the picture. For cloud customers is always helpful to specify the instance, the project and the element you're looking at. The same applies to the browser address bar. We can in the address bar, you can see the instance project and the page reference. This helps us to find it more easily in details. And it's all according to the motto, Help Us nor help you. Thank you. And we are happy to help. He followed you to purchase from the audience. Any Marks to Matthias. None so far? Perfect. Let us move on then. And I'd like to spend a few minutes on modi-site management. Modi-site management, of course, is all about distributing content from a main project to a target project and the other way around with our newest version of modi-site management. So you have your content bundle in your main project and as you're quite familiar, most likely if you have many, many projects like 30, 40, 60 or even more, you can put text and media, think of images, think of files and also the paid structure into those bundles. Usually what you do then through modi-site management is you have automation and there you use your scripts and your workflows which help you, for instance, trigger a translation. in your target project or push the content to a live page right away if you're confident about the content. And also in complex scenarios, you might have cases where text in one target project is just as you send it and then text in another project might have been changed. And you see this indicated by those two highlighted bars here because the editors, the editorial team in your editors, the editorial team in your target project might find a translation that is slightly off or the content itself is outdated. And so what we have launched recently is what we call back transport of content. So all the way back to your main project, you now have with modi-site management, a user interface to decide this change coming from the target project, now arriving at my main project, is going to be accessible. Because think about a scenario where you have two target projects and each target project is saying, look, this translation is off. Here's my proposal. And then you have a proposal on the very same paragraph, on the very same page, being sent back. And it's then on the main project. And it's then on the main project's editorial team to make a decision which version of those two to add to the bundle for the next distribution for it to be sent then to the target projects once more. All of that is nicely shown in a one hour, almost one hour long demo in our webinar. You have the recording here on the right. It sits behind a code, so you need to input that code as well. If you're interested in learning more about modi-site management in terms of features and functionality, but also in terms of best practices. In that webinar, Daniela and I walk you through how big enterprise customers are dealing with these global scenarios of, for instance, 70 projects with 50 locales and how they manage to distribute their content with the help of modi-site management. Additionally, as we've received a long list of questions. Additionally, as we've received a long list of questions, also in that webinar, we've created a new FAQ. You'll find that down below here behind that QR code. So that is a page where we do our best to answer the most asked for questions. On the topic of AI. We, of course, have our assistant suite. So that is the content assistant that follows you as you go through your pages and edit and enhance and generate textual content. You have that bubble of AI actions. Part of that, part of those are coming from Crown Peak. If you want to configure them, and have your list be added by another translation or a different way of generating keywords, you can, of course, do so. We also have already launched the Analyze Assistant. This assistant, powered by AI, goes through your whole page and has a look at, for instance, tone of voice and will make recommendations. So let's say your tone of voice is saying that you want to avoid passive constructions, the passive voice. shouldn't be on that page. Analyze Assistant will pick up on that and then suggest as to how you can rephrase that very sentence. It also has bulk actions. So if you say that you have 10 of those changes recommended by AI, you want to apply all of those in one action, you can do so. Then we have Image Assistant. Image Assistant is here to analyze the subjects, the objects, the content of your image. image. It's going to generate tags. It's going to generate tags. It's going to generate all text based on the context of the page that the image is sitting in. Recently, we've launched Code Assistant. Code Assistant is the fourth assistant in our AI Assistant suite and it helps you find those issues in, for instance, your HTML, which are all about accessibility, performance, simplicity, and other factors. It will highlight those. And through our development capabilities in Content Creator, you can easily click on that finding and it jumps directly to that very element and even to that line of code, again, highlighting the issue. So you can mitigate right away. And last but not least, we also have the Assistant API. This one is here for you if you have a super specific use case for which you need a very specific model, custom model, custom model that is, which we don't natively integrate with. Going to talk about that in a minute. You can use Assistant API and with a bit of project implementation work, you can connect to our AI Assistant suite. So this is today's offering. What we also recently added is prompt management. Prompt management helps you edit and add and duplicate and assign and show and hide those prompts that are sitting behind the AI actions. Our approach to this. Our approach to this is we want to give you all of the configurability and the depth of customization that FirstBird is known for. Because here in the domain of AI, we think it will help you with compliance and with scalability. Think of a scenario where you have multiple projects, multiple groups of users, and not all of those might even need to see all of those AI actions. For some groups of users, in some projects, it might make sense to only have a look at the SEO related AI actions. For others, those might be about a text generation. You can do that through our prompt management. Now, if you're interested in seeing the AI Assistant Suite in action, we also have a webinar on that. Danila, Justina and I walk you through the functionality. Again, it's going to be about this one. This one is about best practices. It's also about how you get the most out of our AI offering. You find it behind this QR code. And again, you need to input that code to access the recording. I want to emphasize that what you saw here today so far is our current offering. To show you how much the teams are looking to the future and to show you what they're currently thinking about and working on, I'd like to walk you through AI So, let's start with AI agents and AI workflows. So, let's start with AI agents or agentic AI. How do we see this? For us, those starts with the large language model. We don't own this. Of course, we use a third party for that. Most of our demo use cases are based on OpenAI's offering. Others can be, as I said, using the Assistant API connected here as well. And we provide focus by prompting. We need that because as we see AI agents as an addition to your workforce. We want to create experts in their domain. So, through prompting, we, for instance, create the SEO agent or the image agent. And that agent now analyzes content and that content might be sitting inside or outside the CMS. The prototypes, which we, for instance, the prototypes, which we already have, and I'm super keen on showing those to you as soon as possible, then go through the tasks that are defined by users, also within Code and Creator or Spirit. And those agents act on those. And they do so by picking certain tools. And a tool here might be an assistant that we already have in our offering. And then at the end, a certain output is generated. I'm going to pause you for a second. Do you have questions or remarks about that? All right, then let's dive into the topic even a bit deeper. Because our thinking here is that we want to offer this year work on certain projects that is done by human beings, as we have it today. Sure. We also want to offer to you being able to work on a project where you have next to you an AI agent. And then we are even looking further ahead, thinking about those projects, which are AI powered only. And the idea here, thinking about the roadmap is the following one. As we've started the year with Content Assistant, it's out there. And we've started with prompt management and UX UI improvements. Those are out there as well. We are thinking about AI and workflows. I'm going to talk about that in a minute a bit more. We are thinking about AI and DQM. So the accessibility and data quality management tool that through DQM Connect also sits within FirstSpirit. We are thinking about fine-tuning models. We are thinking about, again, tone of voice that is trained on the data that you provide because on your website, you are already adhering to your company language. And we would use that for text creation, leveraging the data that has been trained on your company language to create, for instance, that new paragraph or that new page. And then in the second half of this year, we aim to launch the first agents. And yes, we are also thinking about beta phases and trial and all of that. And then based on your feedback, at the end of the year, more Crown Peak owned prompts are on the table plus the SEO Assistant. The SEO Assistant I want to highlight here because in the surveys, which we did during, for instance, the AI webinar that we spoke about, a minute ago, the SEO Assistant came in first, most asked for Assistant. And of course, we have already a team working on that. In a nutshell, when we speak about the AI Assistant Suite and the AI Suite in FirstSpirit, we fully support you being in the cloud or you working on premise. We fully support you bringing your own AI API key or Crownpeak providing one. And we also support you bringing your own AI API key or Crownpeak providing one. And we also support you bringing your own AI API key. We also support you bringing your own custom model, connecting through the AI, the Assistant API. If you want to natively integrate with our suite, you have today three options. You can do this via OpenAI, Azure AI or AWS Bedrock. And what we need here are two things. We need the endpoint and we need the API key. So pretty straightforward. And then if you're interested and want to test this out, we offer a trial phase. We align on a timeframe, usually a certain number of weeks, the AI works best. It is free of charge. It is free of charge. You don't need to pay anything. You can try it out. And what also worked quite nicely in the past is whenever we had those clear goals defined and those check-ins and wrap-ups, the success of the trial phase was much higher. And if you're interested, here's the email address from Marcel. He's your contact person for all things AI. And if you're interested in the Assistant Suite trial phase. And if you're interested in the Assistant Suite trial phase. Since we're focusing quite a lot on AI, of course, we don't want to forget about all the other innovation that we are going to bring to you. And so what we have here now is, in addition to AI, other items that are on our roadmap. So for the first half of this year, we will bring more improvements to the language-dependent release. We have already something out there that is API-based. And is appreciated by customers that have been waiting for that for quite some time. Here, the idea is to provide at some point an interface to make it even more straightforward. As I mentioned, AI and DQM is going to come. And here, the idea is to provide an executive summary that is AI-powered, looking at the most impactful issues to tackle. Also, we have a team working on making content creator. Also, we have a team working on making content creator more accessible. So that is not about DQM or DQM Connect, but rather content creator itself, the product, being more accessible. And of course, the European Accessibility Act does play a role here. If we look at the second half of this year, what we have as a prototype, and again, I'm excited to show you that at some point, is a collaboration and commenting feature. So you see here on the left, the sticky notes, we are thinking about synchronous and asynchronous work on a page, which would also be the basis, as you read earlier, for AI agents to pick up certain tasks. CAS improvements. So think about, for instance, fallback languages, support for that, more GraphQL enhancements, performance gains overall. And then as always, something I want to emphasize is that we try our best to work in a data-informed manner. That means the insights that you provide, for instance, through our roadmap, we'll talk about that in a second. Those come in, those come in, and we score them. You see a few criteria here. They get a final score. It's a long list of feature requests. And then the different teams have discussions on that. So we always have that, let's call it wildcard, or that openness towards your feedback. And so if you're interested in providing feedback, you can do so via our roadmap. You'll find a submit new idea button. button at the top right corner, which leads you through the process. You describe the feature that you're looking for. You provide an email address and your severity. Is it a critical or a nice to have or an important item? And then this one gets sent, and we read about it a second later. I want to inform you about upcoming events as we close off today's session. We have these three. First, the Friday Insights session on AI agents in German is coming up. René, and that is René Voss, the team lead of the FS Core team. And I will talk about agentic AI and workflows. So what you heard about in theory today, you will get a demo on that. If you decide to join that webinar, you see it here linked. Also coming up is a session together with our partner, Logic Joe, on the CMS as the basis of a DXP topic. Also in German, you'll find the link here. It's a webinar happening at the 10th of April. And then a bit further along in the year is the DMX Co. We have already secured a booth. Looking forward to having again so many partners, so many interested customers on site. And then we will see you on the next slide in Cologne on the 17th and the 18th of October. Now, I want to say thanks a lot for today's session. Thank you for joining Andreas, René and Matthias, of course. Once more, are there any questions or remarks from the audience? On the slide stands September, not October. Thank you for the correction, Matthias. All right, then it's a wrap. Thanks everybody for joining. Have a good day. Bye.