Name: Innovation, AI, and the Future of MultiValue – September 2026
Uploaded: 2026-09-16T15:30:52.479Z
Duration: 59 min 32 s
Description: Innovation, AI, and the Future of MultiValue – September 2026

Transcript for "Innovation, AI, and the Future of MultiValue – September 2026": Hi, everybody. Welcome to the webinar. We will get started in just a couple minutes. We're going to give everybody, some time to to, log in. Well, welcome, everybody, to the Innovation AI and the Future of MDE webinar. This is a webinar that we hold a few times a year. We will possibly have another webinar by the end of the year, but certainly the beginning of next year. We do have a packed agenda today, so I wanna get right to it. Starting out with our roadmap disclaimer, basically saying that what we are presenting today is subject to change. And we will let you know about those changes, in these webinars and also on the forum, and we'll have more information on that later. A little bit of housekeeping logistics here. We will be recording today's session and distributing that link later in the forum. We'd like, this session to be as interactive as possible, so there will be q and a. There is a chat and a q a and a to the right. Please put any questions that you have in the q and a, and we will answer them if there is time at the end of the session. We will have a a short post event survey. This really helps us to improve these webinars. It will be active, before you log out, so we do appreciate any feedback that you can give us. So the agenda for today. We are going to start off by talking about the Rocket Multivalue AI, insights betas and roadmap, then we'll go into the products. We'll talk about the betas, roadmaps for the various different products, and we will have, a short product versioning, update for you. Then we'll go into elearning and information development, the Accredited Solutioning Partner Program, the Forum Innovation Library, and the MB Product Lifecycle. And then QA at the end. The team presenting today, Christine Rizza. I am the senior manager for the MV Product Management. We also have Emma Breslin, who is responsible for Universe, Unidata, and the tools associated with them, as well as SBXA and ULPi. Hunter Holmes is responsible for JBASE d three, OpenQM, and the tools MBIS and MB Basic for Versus Code. Our extended team consists of our evangelists, Patrick Payne and Mike Rozalski. And we have a special guest today, Go Chang Soo. He is our director of software engineering. And then e learning is Dan El. Our ID manager is James Hill, and Lindsay Buchanan is our marketing manager. So to start off, the webinar today, we're going to be talking about multi value AI insights and assists. And I do wanna talk, briefly before I hand it over to Emma about how we brand our products. So, you know, just spending a few minutes on how we position our AI offerings. So Rocket has two very distinct AI brands, and each serves a very different purse purpose. The first is EVA, and I know, the the community has heard a lot about EVA. Rocket and that is Rocket's AI enterprise AI platform. So EVA is designed to orchestrate work across multiple Rocket product platforms, and that creates connected workflows that span those different solutions. The second category is our product specific AI offerings, and these AI capabilities are embedded with individual products, and they focus on delivering value inside that single product ecosystem. And examples of those include, multi value, UniFace, Secure Host Access. These are all the the product specific AI offerings that have that product single product ecosystem. So to today, these product offerings are intentionally branded with their respective product names rather than the EVA brand. And this is because their governance, their agentic workflows, their business value are all contained within that individual product platform. They are not currently designed to orchestrate processes or workflows across Rocket products. And as a result of that, the ownership of the AI strategy, the roadmap, the workflow design remains within the individual product teams. So this approach allows each product to innovate and deliver AI capabilities that are closely aligned with their specific customer needs and those use cases. So looking ahead, Rocket anticipates providing, EVA integration for those product specific AI solutions. And that means investments are being made in the AI, products today, and they're designed to be forward compatible and enable that future participation in that broader cross product orchestration and enterprise wide AI workflows as EVA continues to evolve. And with that, I am going to hand it over to Emma, who is our product manager for our AI platform. Thank you. Okay. So as Christine just covered, while Eva, provides the Enterprise AI Foundation across Rocket, MBAI is the purpose built, is purpose built from, obviously, the multivalued platform. So as you can see on the slide, our vision is to unlock trusted AI intelligence from mission critical MD systems, enabling customers to accelerate modernization, make more informed decisions, and automate business processes with confidence. And most importantly, delivering value without disrupting the applications that your organizations obviously depend on every day. So with this vision, we want you to realize the full value of your multivalue investments while creating a practical path to an AI driven future. Okay. So with that vision in mind, let's walk through the, MV dot AI journey, a journey from uncertainty to innovation. So the road map shows how we'll help customers move from understanding their existing environments to ultimately driving innovation. So as you can see, at the center is the Rocket AI platform layer that provides the trusted foundation for all AI capabilities through governance, security, and licensing. So as you can see, along the bottom, the journey begins with understanding. So first, we have application insights. This helps customers understand, you know, complex applications that have often evolved over decades. So with application insights, you will now be able to expose application structures and dependencies, business rules, technical debt, and obviously transform all of that hidden application knowledge into actionable insights. So alongside that is data insights, and this focuses on making multivariate data more accessible. So instead of requiring knowledge of files, dictionaries, or query syntax, users will be able to interact with their data using natural languages natural language. Sorry. So once customers have a clear understanding of their application and data, they can then use operational insights. Obviously, that's the next part along the journey to manage and optimize their environments more effectively. So operational insights will transform, observability into operational intelligence. So it'll help teams, obviously, proactively detect issues, identify root causes, and, obviously, improve application reliability and performance. And so the next phase of the journey is is modernization, to modernize. So the development and modernization assist is designed to increase developer productivity, obviously, by combining AI driven application understanding with development assistance, obviously, in accelerating enhancement and modernization efforts. And building on that, that foundation, customers can migrate with confidence using the upgrade and migration assist. And, of course, this reduces the risks associated with with platform upgrades and migration products by, projects, sorry, by providing, obviously, greater visibility into dependencies, impacts, and required changes, on which will obviously, therefore, lead to faster predictable outcomes with your migrations and upgrades. So, finally, the journey, allows you to innovate through AI enabled applications. So once customers can understand their data applications, operations, and have modernized their environments, they can, see them, begin embedding intelligent experience directly into their business applications. So the key message, with this slide is that these are not isolated AI products. They form a connected journey to help customers understand, operate, modernize, migrate, and ultimately innovate within their multivalue environments all on the all on one trusted AI platform. Okay. So now you know the planned journey. Let me walk you through our MV AI roadmap. So our strategy is intentionally customer driven. In 2026, we kick things off by listening to our customers. So in June, we run a number of, customer advisory boards to ensure that you are, like, directly influencing our direction and validating our priorities. So during these sessions, customers told us that what delivers the most immediate value to them is understanding their applications, understanding their data, and having greater operational insights. So based on this feedback, as you can see on the road map, we're launching, the application insights beta shortly, and more to come on that in the next slide. And we do also aim to deliver the first application insights release date this year. So the initial release will provide visibility into application structures, dependencies, and relationships with graph graph visualization capabilities. And then moving into 2027, we will expand the portfolio. So we'll continue enhancing application insights. And alongside that, firstly, we'll introduce data insights and giving customers the ability, obviously, to interact with MB data through natural language. And then we will introduce operational insights, which is obviously transforming operational, telemetry into actionable intelligence. And then as we look further ahead, in our directional road map, the focus shifts from, obviously, understanding to action. So once customers have, trusted visibility into their applications, data, and operations, we can then, obviously begin applying AI to accelerate development and modernization. And, obviously, our future beyond that, our long term future vision is AI enabled applications. Next slide, please. Thank you. So as I touched, on as we went across the road map, we are preparing to launch the MVAI application insights beta. So, of course, the goal of the beta is to work closely with all of you and gather real well feedback to help you shape both the, product road map and, obviously, future use cases. So application insights is initially focused on Unidata and Universe environments, but we are gonna have support for JPS that is planned for the future. But for this beta, it is just Unidata and Universe. And, obviously, to ensure a high quality experience and meaningful engagement, we are going to limit base of places, just so we can work with you all directly, understand, you know, individual challenges, and incorporate your feedback directly into the development team, in, you know, in a timely manner. But if we do have, you know, lots of people subscribed, then we will obviously allocate as many sessions as possible to accommodate everyone. As this slide does note, there are a few prereqs for participation. So, you will need to get help Copilot subscription. Obviously, as I touched upon, you will need a Unidata or Universe environment. You'll also need a Linux or Windows containerized environment and Visual Studio code. So for anybody who is interested in joining the beta, please do reach out to me directly. Ebrecen@rocketsoftware.com to register your interest, and we will, look forward to welcoming you to the beta. And with that, I'm gonna hand over to Mike. Thank you. Next slide. So we'd love to have time to go over everything, that that the app insights, does, but, you know, we only have an hour. So just wanted to give a high level overview. As as Emma said, you know, this is this tool is, you know, a discovery tool that would help you understand what your app, your application and and your, your database. We got remembering that multivalue is not just a database. It's also the application platform. So by giving information about the accounts, the schemas, the programs, you know, and and showing that in in how everything interrelates, you actually get better insights into, where you need to make changes. And so when you're looking at that, trying to figure out, you have an issue or a place where you wanna modernize or innovate, this will help you isolate the area that you want to, wanna work in. Next slide. One of the areas that we do that and then which is in the first, you know, the the the beta that's coming out is the ability to graph the the application and the and the, data flow of of the, application. So you would go be able to go in there and say, hey. I'm I'm looking at this module. I'm looking at the the entire application. What what is everything involved? What what files are involved? What what, server teams are involved? In this way, you could get a good feeling for for, what what is available there. And then based off of there, you can make either architectural or or programming, decisions and then go out and figure out, you know, how you do your work, along with that. And to, to that end, that is the, that is the extent of of of my my description of the multivalue, you know, the, multivalue app insights at this time. And I now I'm gonna, you know, pass this over to the, road map, release and highlights. And And I'm gonna before we start with that, I'm just gonna mention that, all all the stuff that you are seeing here, the information about the road maps will be, available, you know, on the forum. So, you know, just, go out to the forum. We have the, the the road maps and and frequently asked questions section. So please go there to find, what you need. And, with that, I'm going to, you know, pass it on to to Gokheng. Alright. Thank you, Mac. Hello, everyone. Here today, I want to, talk about the production versioning and, also, I recently positive development to it. So at Rocket, we have used the VRMF versioning scheme for many years, but one part hasn't worked so well as it should be is the maintenance release. They are meant to carry small enhancement and the lower severity fix, but they have historically not delivered frequently enough. So more and more got pushed into a fixed pack instead. So fixed pack ended up acting like a mini release, carrying a lot of noncritical content, simply because they were the fastest way out of the door. So that is the situation we want to change. And because of years of automation work and the internal restructure, finally, we can make that possible. So starting from this year, you will see maintenance release ship much faster. And the fixed pack can go back to what they always mean to be, which is a small number of critical issues and nothing more. This version of scheme in itself does not change, so there's nothing new for you to learn, but there's a real benefit here for you as a customer. The VR and AM releases all reset the PLC clock. So you got four years of general availability and then limited support and then upgrade support. Fixed packet never reset their clocks. So this more frequent and the smaller maintenance release make it easier to upgrade and stay in full support. So next, I'm going to hand over to, Emma, and then she will talk about Universe, Unidata, Unimap. Thank you, Gerald. Okay. So as we move from, left to right across this road map, it obviously details our investment in the multivalued application servers, for Unidata and Universe. So, beginning with what we've already delivered in 2026, Unidata eight four one, we had the beta, average started off with the beta. And then, obviously, we had the Unidata eight four one GA release, which introduced open telemetry support, new object oriented, development capabilities, updated platform certifications, Python three thirteen, OpenSSL 3.5, and a broad set of, other enhancements and fixes. So with Unidata eight four one, we focused on improving observability and modernization. So moving into our committed releases, we continue that momentum. Universe fourteen three one introduces OpenTelemetry support along with audit enhancements, Python three fourteen, and OpenSSL 3.5. And then alongside that, we have maintenance releases for both the universe and unidata as Joe just covered. The maintenance releases, they, you know, they allow us, as Joe touched upon, to quickly, obviously, address customer feedback and deliver important fixes, enhancements, and along with smaller feature improvements. We can do that within the maintenance release, obviously, without waiting or keeping customers waiting for the next major release. So looking ahead into 2027, Unidata eight five one will focus on modernizing the platform while continuing to deliver the stability, performance, and reliability our customers expect. And, obviously, our directional road map, that provides visibility into where we're heading next, obviously, in the future. And as Mike said, these will all be available on the forum. Okay. So, as you just would have seen on the road map, we are approaching an exciting milestone with the universe fourteen three one beta. So I'm really thrilled to share that we would have a number of customers signed up and ready to pass this participate in the beta. So a big thank you from me to everyone who has already, registered. For those yet to register, I just want to let you know the beta is a great opportunity for you to obviously get early access to the release, try out the upcoming features, and, of course, work directly with the product and development teams. So, you know, your participation is always really appreciated by us, and it allows us to help allows you to help us shape the final product through your feedback. You know, everybody we appreciate everybody taking their time out to join us for the beta. So, if you do want to join the beta, when the deck is supplied to you, you will obviously, have the link to the registration page. But if you do have any questions or you need any help getting registered in the meantime, please don't obviously hesitate to reach out to me, and I can help you with that. Okay. So, our unit data customers, they'll already be aware that, you know, we're going ahead, and we did announce this in the, previous road map webinar, that we're gonna have some, breakout sessions on the basic extensions and hotel for further development. We just want we want to hear from customers. You know, we have IR ideas of where to take this, but we want to ensure it's aligned with with your hopes, for the future development of these these two, features. So, because Unidase sorry. Universe fourteen three one is, about to go into beta and we'll have open cemetery included in that release, And we're gonna push these, sessions out to q four so that we can include both the Universe and UniData customers. So they are gonna be small focused interactive sessions where we bring you in onboard, you know, to obviously help validate and shape what we build next. So if you have ever thought, I wish the product did this, this is your key opportunity to come and tell us. Now we will be keeping, attendance intentionally limited, you know, just so everyone has the space to ask questions, give real actual feedback. And but, of course, depending on the demand and the number of people we have sign up, we will run additional sessions if needed. So if you would like to be part of these, please reach out to me, ebresin@rocketsoftware.com, and register your interest now. Okay. So for the app server tools, obviously, we continue investment investment to ensure customers have modern, you know, supported tooling across the development platforms. So starting with what we've already delivered in 2026, we released due to common clients five four three and d b two, four six two, and they both provide certification for the latest unit data and universe releases along with the range of usability enhancements and quality improvements. And for our committed releases, we are expanding our dot net capabilities with the UT toolkit for dot net three one three, and that will include, full product availability through NuGet and support for dot net 10. And alongside this, UAPi one five o and d v tools four seven one, they continue our focus on enhancements, bug fixes, and certification, of course, with the latest application server releases. So looking ahead into 2027, our road map, will continue to, obviously, to strengthen the ecosystem around Universe and Unidata with the tools delivering additional enhancements, maintenance improvements, and certification support aligned with upcoming platform releases. And then beyond in the future, beyond 2027, we may obviously remain committed to evolving our tooling portfolio, you know, with future releases being focused on enhancements, improvements, etcetera. Okay. So, for the MV tools, starting with what we've already delivered. So in 2026, we, SBX a six six five focused on platform modernization with the dot net framework for 8.1 upgrade, native ARM support for Windows 11, security updates, operating system compatibility enhancements, and ongoing quality improvements. And moving into our committed road map, Accuterm eight one three introduces user requested, usability enhancements while SBXA six six six continues to strengthen platform stability, security, and overall reliability. And then looking ahead to 2027, we continue building on those foundations. So Accuterm eight one four and Winter Grade six four six focus on maintenance and security. And with SBX eight six seven one, because this represents, you know, a big step forward by introducing open symmetry integration, a new scripting engine, enhanced mail capabilities, a new modern Windows theme, licensing enhancement, and the retirement of the browser client. This is why we're moving the version to six seven. And I just want to say about the browser client retirement. If anyone has any questions about that or concerns, please do reach out to me directly about that. And then just to finish off, beyond 2027, our directional roadmap remains focused on continued development for each of the tools. And with that, I will now hand over to Hunter. Okay. Thank you, Emma. Hey, everybody. Good morning. I'll be going over first tier, JBASE OpenQM and D3. Just to start us off, wanted to highlight our upcoming JBASE release six three one, formerly six two three, will be arriving October 20. Real quick, just to keep in line with that maintenance definitions that we heard from Guo Chang earlier, we, decided to rename from six two three to six three one just because of the, we really exceeded the amount of content in a maintenance release. So good things there. Some of the highlights in six three one include MV Basic for Versus Code online compatibility, JAgent performance improvements to support, some of those customer environments with increasing integration demands, Linux 10, open SSL three five, and open JDK 22 support. Right? This in turn, supports some of those modern Java environments and current enterprise standards. Of course, security, stability, and scalability improvements always front and center for our releases. Some examples of things we've done there, increasing index key capacity is one example, along with various JD file improvements. We're also continuing our improvements to transaction journaling, building up that feature set that was, introduced last year and conversion compatibility with a focus a focus on simplifying reality to Jbase migrations. So moving on to the next slide, highlighting our next d three version, ten three five for Linux, is slated for October this year and really acts as an additional path, through the end of twenty thirty for our Linux users. Our decision to include this release was a direct result of customer feedback. Specifically, you know, we understand the challenges upgrading to ten four Linux due to the architectural changes that we've introduced. So, ten three five will include a Linux 10 certification as well as all of, the roll ups, of the patches from ten three four. And once we have ten three five available both on RBC and RCC, ten four one for Linux and Windows will come soon after and before the end of the year. So looking forward to that. Now to move on to the larger road map for Jbase d three and QM, you know, just went over what's coming in 2026. Let's look to what is coming in 2027. Starting with Jbase six three two, our first maintenance release slated for the first half of the year with Jbase six four one coming shortly after. Six four one will focus on a few things. One of which is our ODB C JEDI formalization, making it standard in the Jbase product, as well as spooler improvements, MVIS support, which I'll bring up soon, and, of course, bug fixes. Open QM four one one or our next major release of Open QM is still slated for next year. Main thing to focus on here is security compliance enhancements, some other small enhancements and bug fixes. D three ten four two continues our our Linux and Windows alignment, and also we'll focus on security compliance, of course, smaller enhancements and bug fixes. Alright. Looking to the future for Jbase and d three, always, researching, always building something new. These are some of the things we're looking at on Jbase. The JBC debugger enhancements, Python, NoSQL connectivity, auto horizontal scaling, still things in development and in research. D three, gonna continue our focus on that continued Linux and Windows alignment as well as, d three compiler support for additional MV base statements and certainly more there. If any any questions come up on on this road map, please feel free to reach out. Okay. So before I move on to MVIS and MVVS, just wanted to highlight our, upgrade guide that we've made for Jbase. This was created a couple of months ago. Just wanted to reiterate it here. Again, this can be found on our documentation website. And what we're really pushing for here is, having the ability for folks to, upgrade DIY more seamlessly, without any need for external help. That all said though, we do recognize sometimes help is necessary, which is why we're continuing to enable and build up the services org, to be able to meet those needs. This is also intended to be a living document, so please provide any feedback so we can iterate on this and make sure it's the best that it can be moving forward. Alright. And with that, I'm gonna move over to the MVIS road map. Okay. So two three four is slated to release October 22, and brings further UI alignment mainly, in that new UI, our new user management, for the admin experience that's really built off of what we did in two three three for only one common user. We can now have different usernames, separate roles and permissions that can be audited, again, specifically for the admin experience. We've also included some Docker optimization, so we now have a smaller size of the installer and newer Docker OS version, for better security. Looking at a, 2027, three dot o, we will be bringing, this new and complete UI as default into the admin experience. I'll be explaining this a little bit further in the next slide. We'll also be introducing Java twenty twenty five support, performance improvements, installer optimization, and bug fixes. In the future directionally ended research, we are looking at user management improvements, single sign on, Jbase support, which I mentioned earlier, HTTPS as default, FIPS compliance, and certainly much more. So moving on to the next slide, just wanted to highlight a little bit about that first bullet point of the new I being default in MDIS 3.0. Next slide, please. Thank you. Thank you. So what you're looking at here is just a screenshot of the new UI. You'll notice in the upper right hand corner here that try new experience. This is something that, if you've been on, any recent version of MVIS, you you will have noticed. We have given the, option to try out this new UI the past couple of versions. Starting in three o, this new UI will be default. And similar to how we've done it in the past, it'll be flipped. The the toggle button in the upper right hand corner is gonna say something along the lines of, you know, do you want to revert back to the old UI? And if so, a form will come up, and we'll ask for feedback. Right? Totally fine. Right? Especially in the in the next couple of versions if the new UI, isn't just there, for you. But we'd love to hear why. Right? Did you go into the admin experience looking to do one or two things and didn't want to, figure out that new UI, just wanted to get something done, and so you reverted back? That's fine. That's valid feedback. Right? We'll be asking for that feedback for the next, couple of releases, and it'll be super important for us moving forward. But main point here is that it'll still be optional. Right? We aren't just, turning off that that old UI. K? So with that said, last but not least, before I hand things off, looking at the road map for MVVS. Next slide, please. So coming next week, September twenty third, two eleven, brings diagnostic output collection, configurable right click commands, and some bug fixes for, both data servers. For Universe and Unidata, specifically, we've introduced AI Copilot syntax and plugin instructions, examples for MV Basic to help developers there as well as region collapsing. And for Jbase specifically, we've added, file locking support. You'll notice that we have features for some data servers and not for others. But rest assured, our North Star is feature parity here. We've just recently included Jbase in our support. So, there's some catching up to do. So now or in the future, you do see, separate, features for different, data servers, just know, yeah, feature parity is is, the North Star and will be coming at a later date. Looking in 2027 directionally, 02/12 is our next MVVS release. It'll include syntax highlighting, predictive intelligence support for Jbase, improved partial performance and bug fixes. And in the future, directionally and in research, we're looking at Jbase debugging, DevOps, additional basic development toolkit features, system builder support, and, of course, AI enhancements. Before, moving on, one last thing from me. Starting next year, our release cadence for MVVS will shift slightly to focus on two releases per year from previously four, and with hot fixes sprinkled throughout the year. This really this change happened just to allow our team, to bring more impact in each release while still delivering at the same velocity we have been. So just an update there that I wanted to share, so you are not surprised next year. Okay. With that, I think I am all done. So I will hand things off to Dan l to talk about elearning. Thanks, everybody. Thank you, Hunter. Elearning. Yeah. Learn.rocketsoftware.com. I just wanted to discuss a little about our elearning courses and objectives. The Versus Code training, is out there. So the AI enhancement development that, everybody's been talking about, the Versus Code is where you're gonna start, and we've got lessons out there on using the Rocket MV Basic Extension with online editing. It covers everything from downloading to initializing the folder and adding your default build and and launch tasks. Everything is given step by step. So, it should definitely get you into Versus Code and be able to start using Versus Code for for your coding, and then looking at doing, AI and etcetera in in the near future. The shorts for Versus Code include, limiting accounts and file displays. What we found is that the default, for Versus Code is to just show you everything, and in a, true, development environment, there's way too many files and way too many accounts. So there's a little two minute video on limiting those accounts and files so that you can, set up your development environment. There's also a simple one minute video on code lensing and what it adds, and a little, short on go to definition and explaining what it does and and how to use it. There are also videos coming up this quarter which are going to, be short on setting up ins the instructions to aid in coding in your standards. So we'll have an actual two minute video. So if you can't quite figure it out from the, the instructions that you're given, this will be a, very short, simple, showing you exactly what to do. And then the next, video we're looking at is the schema video, which just helps you to set up the schemas for your, your data so that Versus Code not only understands your code, but understands your data. And as AI comes into play, that becomes more and more important because if you ask AI to add a customer name to a file, it needs to know where that customer name is. And then next next slide. We are doing more and more Docker based tutorials. We currently have Docker images for all the essentials for Universe, Unidata, and Jbase. You can now rather than having to be on a cloud virtual and having a limited time to access it, you'll get unlimited access to your own personal Docker image. So you can always go back to it. With that in mind, we will be publishing Docker images for YouTube basic Python functions. That will teach you the Python functions in YouTube, and it includes how to load modules, how to use those functions, and some, basic programming, not only code, but examples, to show you how you could be using Python in your, YouTube. We will be publishing Docker images for MB Basic one zero one. That will be available for Universe, Unidata, and Jbase. And then we're going to be a whole doing a whole new course that will introduce you to Docker images for YouTube and Jbase, and that's administering your server. So you'll have a Docker image where you can actually learn administration, how to work with the, Linux users, displaying the users within your database, viewing and adding and modifying accounts and files and etcetera. But it's all gonna be on your Docker image. So you've got a local image. You're not gonna be disturbing your development environment when you're learning how to do things as as an administrator. And that's what we're doing with, elearning. So I'll turn it over to James for, ID. Hey, everybody. I'm going to go over three slides today looking at documentation. In our last road map meeting, I talked about some AI productivity gains, that help improve documentation. And I I I wanna say documentation is molding faster today than any point in my career. And we're using that opportunity to expand what we can deliver to customers, such as these highlights here. Adjusting updates and batches using AI means we publish more documentation corrections and improvements faster. Automating updates across the entire doc set results in, greatly improved consistency and reduction of conflicting information. Writing rewriting from scratch an entire guides for an absolute beginner audience, which we think will help you get new employees up to speed. We're updating documentation content so that AI searches and queries provide the most accurate and complete responses. We're updating code examples. We're starting a video enabled tutorials, and I might work with Dan on that actually. And in some cases, we're creating documentation collaboration with customers, and I'll mention that later in this in another slide. Let's go to slide two. And so I bring this slide in every every every one of these road map meetings. The documentation feedback improves the documentation. That's how it works. The more feedback you give, the better the docs are gonna be. So this is one of our most valuable inputs is you. So when you're on the doc portal, add a question mark to your search. You'll get an AI generated answer, and it will link to related topics as well. We monitor this search activity to identify questions that you are asking or getting answers to, and we can that will help us guide documentation improvements. But you always have the option of providing feedback on every page of documentation. There's a contact us at the bottom of every page, and you can also log in and click that feedback button. We review all of the feedback that you provide. If you include your email address, we can follow-up with you on a documentation request as well. And next slide. Yeah. So I mentioned the documentation in collaboration with customers. For the MBIS installation user guide, we recently completed a significant update adding and revising more than 25 topics. They were mostly focused on deployment scenarios. These topics were developed at the request of a customer and with their direct input, review, and their validation throughout the whole process. This allows us to create documentation from the customer's perspective rather than solely from an internal developer focused viewpoint. I believe this collaborative approach represents a new model for documentation. Going forward, it has been one of the most rewarding documentation products I've worked on, and I know that Rocket and myself highly value these types of customer partnerships. So I would ask you to think if there's any topics, workflows, deployment scenarios, integration cases that you would benefit you or your organization, I invite you to reach out. We welcome the opportunity to work directly with you on to develop documentation that helps you with your needs and helps you be successful with our products as well. Thank you very much. Mike. Thank you. Yeah. So, for those of you who happen to attend the MV World event recently, you you may have heard us mention the RocketMV accredited solutioning, partner program. Just wanna give a little bit of an, of an overview of that today. So when when you when you think about, you know, what what you've heard from myself and and Patrick over past, you know, webinars and road maps, we've always talked about the multivalue discovery assessment. That is just the the short duration service that that the evangelist provide to give you a good overview of where you are, what your business and technical needs are, and how you get there. And most of these, type of engagements, we we usually will will bring you over to our solutioning, group if you do not have the the ability to take the steps that we we we recommend. And that that would be in in a, you know, you know, in in areas of, like, the the upgrade assistance, you know, rehosting. So, like, if you need to migrate from, say say, a AIX to Windows or Linux or something like that, we would bring it over there, and they they have packages to help you with that. And they are they're very good at what they do, but there are some areas that that they they may not have the bandwidth or the expertise to help. And here is, here is where, you know, the accredited solutioning partner program helps. You know? So this is where, you know, we deliver what what we can, and we we we try to connect you to the people who could do what we can't. And that that is the Rocket, accredited solutioning partners. So the solutioning partners are are focused on on delivering specific things. We have a a procedure for accreditate accrediting them to make sure that they provide a level of quality and, you know, have a, a set expertise in the areas that they describe. Next slide. Next slide. Thank you. At this point, we have we have three badges that that we we we, we produce for our accredited partners. And that is the general one, which would be the the main things that you saw on that previous slide, which focus around the, areas that our solutioning group, you know, would say, hey. You know, you could either do this yourself or if you need assistance, you know, these are people who could do it for you. As well as we have one for, recruiting partners. So if if a if a customer or or a partner says, hey. You know what? I'm really looking for some multivalue expertise to join my team, But, you know, I'm I don't I don't have the, you know, the bandwidth to go and and fully, you know, flush out the the candidates and make sure that they're they're they're good enough for, to be a multivalue developer. These solutioning partners, you know, have a, you know, have a recruiting platform that would, help identify these resources and and provide a way for you to get, access to these resources to bring on to your teams. And then the other focus that we have is we we realize that AI integration is something big and something, you know, more so than just the tools that we are providing to for you to understand your multivalue application, the innovation, and, integration into a larger enterprise type of a solution where you wanna bring, you know, AI, x you know, AI, to to your customers or to, you know, to your to your solutions. We have, certain partners that we have identified that have those skill sets that work, you know, you know, you know, with multivalue and beyond multivalue to help you, integrate, AI into your into your solutions. So that, you know, this is this is, you know, all new and interesting stuff. If you're interested in knowing more, please reach out to me. And with that, I'm going to pass it over to Christine. Thanks, Mike. Just wanna go over quickly the Rocket Envy Forum and the Innovation Library that is also contained within that forum. Our forum is at community.rocketsoftware.com. There are multiple different sections within the forum on multi value. We have subforums for the MV Roadmaps and FAQs, as well as individual product groups and the Innovation Library. The Innovation Library is something that we launched last year, and this is a place to share your ideas, your prototypes, your code snippets, and any information, that you've developed. So we're inviting all of our Rocket partners and customers to become active contributors in the Multivalue Innovation Library by showcasing your solutions, sharing your expertise, and inspiring others. So downloading and exploring prototypes, demos, and white papers, accessing and adapting sample code, reusable code snippets, and integration examples. So your ideas, experiments, and use cases can help accelerate that innovation across the entire multi value ecosystem. So, next, I wanna cover the MV product life cycle. This changed, last year and goes into effect October 1. The mv product life cycle shifted everything so that we have a longer GA period for our releases or our versions. The MV product life cycle is not based on product, but product versions. So the version is got a general availability of four years now. It was previously three years. Limited support stays at two years, and we've added a new, status of upgrade support where upgrade assistance will be available for one year prior to a version going end of version life. I'm not going to go into detail here. I'm just going to highlight some of the areas on this slide, from security vulnerabilities. Think of this as you know, legacy systems may not support the modern security protocols and that leaves data and infrastructures exposed. Lack of support, you know, this is really about as software ages. The community, Rocket resources tend to start to dwindle, making it making troubleshooting harder. Performance and stability issues on older versions, you know, that legacy software may lack the optimizations found in the newer releases, and that leads to slower performance and higher resource consumption. Combat compatibility problems. You know, updates in hardware may not support may not support, older software and that leads to performance degradation and system failures. And then new tools, APIs, or platforms may not work with that outdated version, limiting innovation and automation. Older versions, you know, you miss those features and innovations. So from a compatibility perspective, you fall behind in the technology and that can hinder business agility and responsiveness. And then lastly, on operational, costs or financial risks, you know, older software may not be may be prone to outages, you know, affecting business continuity. And supporting those outdated systems offer requires custom fixes and legacy expertise. So with that, all of this information is available in the Product Lifecycle Handbook. It's available the handbook itself is available on the Forum. It's available on the PAM and in the future will be available on the Rocket Documentation Portal. We also have additional resources out there on upgrading. There is a best practices brochure. We have all the links to all this information here in the slide, which will be available in the recording. We have mb upgrade miss. There's a blog post out there on that. And then we have for, Universe and Unidata, we have a release matrix that shows all of the features in the various different versions as they progress, in in, enhancements so that you can compare your version that you're on with the current GA version. And with that, I thank everybody for attending today. I do wanna give you our contact list. These are all of our email addresses and the products that that we're responsible for or where we have our expertise. Please feel free to reach out to the appropriate person should you have any questions. And now we're going to move on to the Q and A session. There is a Q and A chat window to your right. And if you have any questions, go ahead and pop them in there. I don't see any questions right now. We'll give you guys a few minutes, and if we have no questions, we'll go ahead and close the webinar. I do also wanna remind everybody that, Lindsay is going to launch a survey. Lindsay, I don't know if you can launch that right now. And, okay. There's a question, but it's in the chat window. Hunter, what is the plan for AI and d three? I think that's probably a better question for Emma on the AI side of things, but, certainly something we're we're looking at right now. I don't know, Emma, if you have anything else, in terms of road map or anything. I don't know if Emma can come to the stage, but I'll go ahead and answer that. So right now, we are looking particularly at Universe and Unidata. Jbase is the next AI integration that we are also researching. And right now, we we're not looking at d three as far as AI integration, but something that we will consider in the future. And, Richard, we'll we'll get back to you on, any additional details that you would like on that. So, Hunter, there's a question. Is there any OAuth optimizations planned for NVIS, tokenization, caching, etcetera? Thanks, Chris. Yeah. Let me go back to the team on that one and see where that is on on some of our research projects. I'll definitely make sure to bring this back to the team and and send you an email directly with whatever we whatever answer I get back. I appreciate the question. Richard, we will have two recordings. We recorded the session again last night. You asked if James Hill could rerecord his con contribution. We can't record over the recording or add, additional recording, so we'll determine which of the two sessions will be the one we post. We might post both, but James was very clear last night. So, if you have any questions on his section, I know a lot of his talking points were in the slides. Please reach out to James, and he can certainly help you with that. We do have two other questions. I think we will, reach out to you directly to answer those, get clarification on those questions and answer those. Chris, I'm seeing one here about upgrade paths. Hey, Richard. Yeah. We have two built out paths for, d three, at present to Universe and to Jbase. There is no right or wrong way. It's it's all dependent on on people's environments and and, you know, contextually what what we're looking at. So, Richard, if you have any questions, please feel free to reach out, and we can, yeah, definitely discuss further. Absolutely. Any other questions? Hey, Chris. I'm just going back. I see a question about MCP connector fitting in the AI road map. Emma, do you wanna answer that, or do you wanna talk to Asha offline? Or might. Or Mike. Yeah. I I I can address that quickly. I mean I mean, we need to really understand what you mean by MCP. I mean, are we gonna provide a a general purpose MCP? That that's not something that we're looking at. We are looking at all of our AI solutions, you know, go you know, driving through MCPs, you know, and, and the architecture, you know, of that is what we will be, flushing out and working with, throughout the data. So, yeah, there will there will there is a MCPs, if anyone who is is into, AI, knows, that is the the, entry portal, the entryway, you know, to get information about the, the the knowledge or the solution that you're you're connecting to. In this case, the multivalue, you know, database and platform. So, yeah, there there there it is it is in the road map, and if you're in the beta that you would you will see how that that is going. And, it is it is it is a a key component throughout our whole AI strategy. I just see a case number in here. Just, just know that we're looking into that, and we'll send you an email. Appreciate that.