Video: Rocket® Uniface Roadmap 2027: Modernization, AI & What's Next | Duration: 4096s | Summary: Rocket® Uniface Roadmap 2027: Modernization, AI & What's Next | Chapters: Welcome and Introduction (5.91s), Session Introduction (72.905s), New UX Features (400.7s), UniFace UX Features (947.545s), Version Updates (1401.955s), Learning Resources (1733.51s), AI Strategy Vision (1851.95s), Version Control Integration (2460.435s), Roadmap and Progress (3002.6s), Future Roadmap (3390.93s), Release Strategy (3477.68s), Migration and Modernization (3678.49s), Wrap-Up & Feedback (3832.985s), Linux Certification Request (3898.57s)
Transcript for "Rocket® Uniface Roadmap 2027: Modernization, AI & What's Next": Hi, everyone. Thank you so much for being here. We'll get started in just a few minutes. If you want to test out our chat or q and a while we're waiting, let us know. You can even just tell us where you're from, and we will get going in just a moment. Okay. I like the energy I'm seeing on chat. Thank you so much, everybody. I'm gonna go ahead and kick us off. Thank you again for taking the time out of your day to join us for our Uniface, road map session. Michael Taylor is going to guide us through literally all the things. So very excited. Just a little housekeeping information. We are recording today's session, and we will send you the link afterward. Everyone is muted. So if you need to reach us, chat and QA are open. So just open the QA to ask a question. And then before you leave the webinar today, please, if you can, just fill out our short survey. It helps us... It'll be launched with a few minutes left, so we'll give you all time, but it really helps us just help you better. So just a quick reminder there. And then our agenda for the day, we're going to recap basically what's been done, talk about what's happening currently, and as with, like, any road map session, we're gonna tell you what's to come and reserve room for questions. And with that, I'm gonna kick it off to Michael. Thank you so much again, everyone. So hi, everyone. Yeah. I'm Mike Taylor, product manager here at Uniface. I think pretty much everybody probably knows me by now. I've been doing this now for a little while. So, it's great to be back, and it's great to be able to show what... Share with you what we've done and what we're doing and and what we're going to be doing in the in the near future. With the... Always with, with the road map presentation, I like to start off with, you know, some some history. What have we what have we put into the product? I'm gonna be starting, I'm gonna be starting with, ten four zero two. Normally, I wouldn't go back quite this far. However, there is, there is some great functionality, which I think I still wanna trumpet about and still wanna talk about in in this early release. Right? So, ten four zero two, gave us a lot of new functionality. The things which, which I find really exciting are, exceptions, a way of being able to to put, new ways of being able to, to to be able to do control of flow within an application. It changes the the Uniphase is very permissive, error handling where if you don't do anything with it, it will it will take it as a as a an accepted failure and continue and and just work to be, more stringent in in making sure that errors are core. You know, what I really like about this is that it it it makes your applications more robust. You know, you you have to think about, your error handling, completely, and you you have to be able to... You end up with a with a strong with a strong application. The other thing in in ten four zero two, which I, you know, is really worth sort of, highlighting is the the functions. Functions, a new prop module, which allow you to be able to to encapsulate this, prop code much more easily within our inheritance model. Instead of, a... You know, with entries and being, promoted to the component level and therefore allowing you to have many more clashes. You know, the the functions allow you to be able to encapsulate it at different levels within the component. So, a function, specified on the component level becomes very much similar to, to the, to the entries. If it's not on the entity level, then only that entity and its fields can be able to call it. And if it's on the field level, only the field itself would be able to do And that, really does help with the nailing conflicts if you're trying to put code in the model, which is then inherited into your components..com is obviously another, big thing that was added into, ten four zero two. So moving on, ten four zero three, service pack was released. I think it's worth talking a little bit about what we do in the various different releases of Uniface. So, you know, we release a patch every two weeks. In that patch, we will put functionality. We will put, you know, a new functionality. We will bug fix. We will put security updates, and that kind of stuff. What we don't do is we don't introduce incompatibilities, within the application, which means that, you know, you you have got a a fairly easy path to go from a patch to a patch to a patch to a patch. When it comes to service packs, you know, it goes a little bit... It's a little bit more extensive. We will, we will make sure that all of the previous patches are rolled up into the the release. We will, we will add new currency, as well as remove old currency. So stuff which isn't any longer supported by the vendor, you know, we'll clear up the PAM and make it so that, so that, you know, it's only supported stuff by the vendor. We'll put new functionality in there, but we'll we'll also put minor incompatibilities. You know, incompatibilities, unfortunately, are a bit of a fact of life. You know, we don't have any much choice a lot of the times. So, you know, we will put small incompatibilities into service packs. And the reason why I say this is that, you know, when you get to a service pack, you know, it is worth looking and seeing what those compatibilities are and to be able to plan your route to go forward to the next version. So in ten point ten four zero three, we had a... We produce a a lot of, new functionality. So I would like to sort of highlight some stuff which we put in there. The first thing that is worth talking about is the the Uniface UX and the UX interfaces, which are, a new paradigm of being able to develop web applications within Uniface. So it's built on the DSP technology, and it allows you to be able to create, user experiences or or extends Uniface into the user experience of the DSP application. Historically, you know, you have this great flexibility of being able to, create your own UIs and allow Uniface to do the heavy lifting of being able to, transport information from the browser to the server and then from the server back to the browser. You know, that... That's great functionality. It gives a consistency. It allows you to do scoping and blocking. However, you you are responsible... You are responsible for being able to create that front end. And, you know, we we we got plenty of feedback from customers that, you know, Uniface developers wanna be able to create these these rich web applications, and how do they... You know, without having to go out and learn HTML, JavaScript, and CSS, how do you do it? Well, this is our answer to it. It's it's the ability to be able to create this consistent and rich web front ends within your application. It's split into two parts. So Uniface UX is the out of box experience. These are the widgets which we've been creating. These are the the functionality which we've been creating that allows you to be... Which allows you to create a consistent, rich front end application. Everything works together. It is all based on the same themes. It uses the Microsoft fluent web components in order to be able to create the widgets, allows you to be able to set a widget against the... An, a a item in the the component structure, and then using definitions and properties to be able to, to tailor how it behaves. So for instance, being able to put an icon at the beginning of the field to be able to set a label and and all this kind of stuff. But with that, allows you to sort of step away from having to create that HTML, JavaScript, and CSS because it's wrapped up into the widget itself. So we produce this this front end experience for you, using, using this Microsoft fluent. But what it... How do you how do you extend it? How do you make it your own? How do you, start it in in in a completely different way? How do you use a different front end framework, you know, Bootstrap or or any of the others, Tailwind or any of the others which are which are available. So in order to be able to do that, we also produced an open API. Our API allows you to be able to, you know, if you conform to the API, you can create your own widgets, which can do great things, within within our application. So for instance on the screen we've got a couple of images, we've got one with a table, we've got one with graphs and the only difference between the two is that we've selected a different widget. The widget is the graph instead of a table. And that then renders it as a graph. It enables you to be able to encapsulate all the user experience, interaction, and visualization within the widget. You don't have to do it within the component itself. That simplifies the component. It simplifies your coding. You put the business rules within the model and the component. And that UX side of things is then abstracted into those widgets To enable you to be able to understand the best way... You know, best practices of being able to create these widgets, and also be able to take, you know, what we've done and be able to extend it to it to your to your own usage. You know, we've also opened an open source Uniface UX, which allows you to be able to to, see exactly what we've done and be able to extend it if that's what you want to do. Another really strong thing within 10/04/2003 has been the app, is being able to secure applications with the the application certification. So application certification is, at the, compile at the build sign. You're able to generate a a a public private key partnership, use a private key to be able to sign the... Or certify the components, and then at deployment time, being able to use a public key to be able to encrypt the path section of your assignment file and be able to bind the two together. So only your code that you have released is able to access that path, preventing code injection into applications. What objects are certified? It's anything that's executable. Yeah. So components, menus, panels, you know, all that kind of stuff, is all assignable and will only, you know... If it's going to be able to access, the database, you know, it was checked by the runtime. And if it fails, then the application stops, you know, giving you a lot of security and safety within your within your application. The the next thing that's worth highlighting is, the observability, and telemetry, yeah, with open telemetry. Uniface, traditionally has allowed you to get a lot of logging information out of your application. You go into your assignment file or in your code and you set your your IO printer, your your, your, you set your IO buffer to six... To 64, 63, to a number and then the UniFace outputs it to a file. That has a number of challenges around there, and especially if you have got, distributed deployments, where you could have multiple application servers all running your application and the the network traffic being being directed, to them. This also includes things like Docker as well. How do you effectively debug your application, and find out how it's running and what it's doing. So what we wanna try and be able to do is to be able to get this information and to output it into, the standard observability systems like Grafana, like Elasticsearch, like Splunk and a number of the others. And so Uniface has added this functionality into the runtime itself. So you can turn on the output. So in the assignment file, you create a new section which is observability. You say say tracing is equals on, list, yeah. It's it's, yeah, usage, turn on the tracing, turn on the, on the, the the logging, and then sort of also fine tune it to other details which Uniphase can output as well, things like the the, the status of the the function call, etcetera. It will go down as far as code level. It will not go down as far as data. Data is is something that needs to be protected within your application. So it doesn't go down as far as data, but it goes down as far as, the proc code. As part of that, it will also give you information about how long it is spending in each of those proc modules. Is it spending time in the database? Is it on the network? Is it within the problem module itself? And it will also give you that in the just this local, this this one module or, accumulation of everything that is, that it has been that has been called from it as well. So it gives you lots of output information. And as I say, it's something that, you can just turn on within your assignment file. It's not something you have to go and recode your application. It allows Uniface to sit within the standard DevOps panels and and, and systems which you or your customers are probably already using to to monitor systems and and to make sure that the the, the the systems themselves are working. It goes through open telemetry, which gives a a great, variety of back ends which it can connect to. You know, we just we just output it. And the great thing about this is that it doesn't slow down your application. It's all sort of off onto different threads. So, your application continues to work. You don't have to... The the problem that was the traditional problem of when you turn logging on, your application slows down. That's not something that's a problem. It gives you the ability to understand what's going on and to be able to diagnose an issue before your customer or your end user contacts you to tell you that there's something going on. You can set up those dashboards and alerts to be able to find out. As I say, it's one of my favorite bits of, functionality right now. So UniFace UX. UniFace UX, I'm I'm... I explained what it was. What what does it consist of? We have widgets which have been produced at component level, at entity level, and field level. And these all work together, well in order to be able to create you a rich user interface. Yeah. And because we have them at all those different levels, we no long no longer are required to create, the the the HTML within the component. That HTML tab can now be blank, and Uniface will will create that for you as it goes through. So the layout mode allows you to be able to to, select generated and Uniface using UX widgets will go away and generate that. There's a big rich, collection of widgets which are available. You know, and things like, the layout, for example, gives you the ability to be able to add an appearance onto things. So is it a card or is it an outline? Is it a section panel? That kind of stuff. And that gives you an idea and an impression of what the the the properties are able to do within, within those widgets. Underneath, you know, all the interface UX has been built up using the UX interface, which is the the open interface which, you know, we publish and and talk about. We've also created on top of that, a a widget framework, which allows us to be able to encapsulate, functionality within widgets and be able to share across widgets. That framework is documented within the the the GitHub repository. So Uniface UX GitHub repository allows you to be able to to get lots of documentation about how to work it and how to extend it. Yeah. So, no need to go into the the minified JS which we supply. You know, we supply the the the source and we just, supply the testing frameworks and and and that kind of stuff along with it. Widgets are able to also include code. So if you selected a logical widget, Uniface's compiler will also bring in, included props if that's what you want to do. Dark mode has been also enabled on it, and that is not just on your Uniface UX, that is also on the the DSP themselves, as well, the the traditional DSPs. The the UX is a complete solution. The... Depending on what you've done in your DSP application, there might be some CSS changes to to enable it. Yeah. Lots of work in around the IDE, and that's something that we continue... We plan to continue doing as we go through. Security is is always top of mind. You know, we spend a lot of time dealing, sort of concentrating around security. So we do, a lot around, we've done things like the application, the the application certification. We've introduced a new seed option onto the pass scrambler, which means that the the the scrambling is done uniquely for for your site and your seed, etcetera etcetera. Around security, we have also spent a lot of time internally, making sure that the the Uniface itself, conforms to the... To security standards. So, you know, we do a lot of static, code analysis, using a product called Polaris. And using the output from that, we make sure that the UniFace conforms to the coding standards, the actual run time, the c code that we produce. We also run through, tools like Blackdub to make sure that, CVEs, etcetera, are being, are being addressed. So it's always worth staying up to date with the latest versions of Uniface to be able to get that, the the update in the... Not just in Uniface itself, but the tools which we use, and bring together. You know, observability, I've told... Talked about. Logging, we, we've also moved this traditional logging off onto its own threads as well. So that's now more more formal than it's ever been before. We introduced non Gregorian, calendars with, with 10, ten four zero three and a number of other things along the way as well. Something worth noting, the SQL workbench was moved from the, from the Usys. Uar into the IDE. Uar. You know, we we look at the the SQL Workbench and think, you know, that's possibly, something that could be misused. So we've taken it out of the the standard, application deployment, moved it into the the development side of things, so it's still available. But if you use it or you rely on within your application, you know, you would possibly have to either... You would have to move the the, the component from the IDE. UAR into your... USIS. UAR. Currency is always a big big topic for us. You know, we're keeping up to date with, with the different platforms and databases which are available and are used throughout the customer base. You know, the... These are... We we will introduce constantly new, databases and, and platforms as they as they become available, or or when they are requested. So, you know, please do do feel free to reach out and request, and, you know, we'll we'll try and schedule them in. We we have, a number of a class platforms which we which we we concentrate on and will release as a matter of course, but there are other ones which, you know, please please tell us what is important to you because it helps us to be able to prioritize on what we produce. What we did do as part of releasing 10/04/2003 was to to remove support from things which were no longer supported by the by the vendor. So things in there are, Windows 8.1 and Windows Server 2,002, 12 r two. They're they're probably the big ones. You know, Windows 10... Windows also operating systems tend to be very long lived. So, yeah, removing them is always a difficult difficult choice. However, once they become, non supported by the vendor, it becomes very difficult for us to support it ourselves. And and, you know, we we wanna be be open and clear about that. You know, databases, again, no longer stores by a vendor. 10, 11, 12 of post grade. And Internet Explorer version 11, no longer, should be used with with the Unifax runtime. You know, that that sort of disappeared off with with Windows, 8.1. Nothing, that is available today, supports Internet Explorer 11. So Edge is fine, Chrome, Firefox, Opera, you know, all all of these kind of things are all fine. But the the old Internet Explorers, have finally disappeared. So, as I say, the, incompatibilities can be, introduced as part of the service pack. This is a pretty exhaustive list of, for ten four zero three. These are things which you... Kind of things which you have to look at. So, you know, the top one there is, Tomcat 10.1. They changed the API. It no longer supported the API over which we which we implement, the server API which we implemented. So we brought out a a new version of the WRD version seven, which does support it. Along with that also came, same size cookie support, which is a good security enhancement. Java calling, is using a new package name, finding your compilers no no longer as part... Named as part of our product. It is it is an... Our AllRocket software. Yeah. So just generally, you know, make sure that you you, you keep up to date. You know, you... If you're going between service pack, understand what what their minor income liabilities could be. So, we've just released service pack ten four zero four. I think we released patch number five on it, yesterday. So we are ten weeks ago supporting, we released, service pack 10,404. It's the the latest supported version of Uniface. It is, mainly it is is a roll up of, everything that has come before it. But there are a couple of important things which, which we have, which we've done within the, within this release. Probably the main one to really expose is that the, anything between before TLS 1.2 has has been removed out of the product so you can no longer use the SSL the TLS one point zero and one point one. Also along with that the weak ciphers which are which are which... The ones which have been sort of deprecated from, the underlying technologies which we use, and are unknown to be insecure. So that's something really to be, to be to be, aware of. In 10/04/2002, we we actually, changed it so that you had to enable those things. But now, we just can't support them anymore, so that they have been removed. You know, we've enhanced the Uniface UX so that we are now passing through the the model labels through to the component, through to the to the the widgets themselves. And and therefore, you know, you... You're being able to get that inheritance. We updated the Windows SDK. So if you are, if you compile in your own three g l, it might be something that's that's worth, looking into. We also added the, OpenTelemetry on Solaris, through popular request. And on Windows 32 bit, we've we've had to deprecate the Java call in, and the XSLT. And the reason for that is that there isn't really a supported version of Java runtime 32 bit anymore. You know, they've all sort of now no longer been supported or have have gone out of date. So we on the 32 bit installation we've released we we include the 64 bit version of Java and we do we include that in order to be able to run the the the latest versions of Tomcat. But if you, if you do need to continue to use the XSLT or the w... Or the, the Java call in, it's still possible to do, but you need to supply your own face to beta versions of Java in order to be able to do it. Yeah. We also, we've also released a a new widget, which is a core new widget onto the Uniface UX. Something worth noting is that the components compiled with ten four zero four are no longer compatible with earlier versions. Yeah. So you can take something from ten point four point zero three and you can run it in ten point four point zero four. The the the runtime is clever enough to understand the format of the file. However going the other way, that's not possible. So it is possible to to run them older compiled versions on later version of the Uniphase. So another crib sheet of of things which are, that you know, it... It's worth knowing about, before doing the upgrade. The TLS I've mentioned, yeah. As I say, it's always worth making sure that we, that you understand, the incompatibilities that are are are in the the service packs. Elearning. This has been a, a great journey for us. We've been busy creating content which goes on to elearning. If you haven't been on to elearning then, the website is learn.rocketsoftware.com. It's free to use. We keep on bringing out new modules and and new learning content for the site. So we, you know, we've obviously concentrated a lot on the web especially around the the Uniface UX and UX interface. Recently we have produced learning around the DSP lifecycle which is you know, the the the various different triggers which are fired, and the events which are happened, the path that it takes while it's going through, through a web application. So the DSP lifecycle gives you that that great overview so so you understand how everything fits together within the whole stack. And we've also just released, the first part of a a scope, so understanding about the blocking that happens within the DSP framework and and how to control it, how to use it. But it also describes how data is passed to and from, the front front end and back end. Yeah. We have been, we have been and we will continue to release sort of short form, nuggets of information, bite sized bits of information in the form of of shorts. These are learnings which are specifically targeted at a very narrow, a very narrow bit of information. Yeah. So you can go on there and you can find out that information in one or two minutes about about how to use a particular bit of functionality. As I say, that is, that is something that we have been, growing over, you know, since, for quite some time now. And... Yeah. An example of the shorts are things like LDAP, and that kind of stuff. So now we get to the current activity. What what are we currently working on in in the labs, and and what are we expecting to be coming out, in the in the near future? So first of all, we we look at, you know, where where where is it we wanna concentrate within our product. And, you know, we wanna be able to enable customers to be able to modernize and to be able to integrate with other technologies. You know, we want to make, developers productive. Yeah. More productive than they, you know, than they they currently are. Uniface is a very productive environment, but, you know, there there is more that we can do and there's more that we are we are doing. Not least of that is in and around the integration of AI within the platform. It's not really an integration of AI within the... In in... Within the platform. You know, we we really have, quite a low level trying to understand how AI is able to help within the Uniphase development life cycle. And we got a whole strategy around that. I'm gonna go through it in in a in a coming slide. Security and observability, you know, building trust with with the platform. You know, that that remains to be, something that is, you know, is is constant within the industry today. You know, they're running on outdated software, having vulnerabilities within software is something that, is becoming... More and more focus is happening upon it. And it's only right. You know? There are increasingly clever tools and and and utilities which which can exploit vulnerabilities and and it is our job to make sure that, you know, we do everything we can to to to help protect, yourselves, and the software, from these risks. E learning is is, is continuing to grow. So what are we working on? This is a list of the customer facing, things which we're working on. So version control, we are working on integrating Uniface with some of the databases which are available from, from, you know, from within Rocket, you know, our sister databases. We have, we we wanna be able to to use Uniface in order to be able to help, multivalued customers or or the Rocket customers to modernize their their applications. You know, so... And we also want, we wanna have a, our database available for for anybody that wants to be able to use it as well. We are working on platform currency, so d b two version 12. We're expecting that to be released next, in the next patch into version six and then in patch number six and then we will be sort of picking up the next currency immediately afterwards. We're doing quite a lot of work still on the Uniface UX. A lot of this is around searching and looking up of data. So a combo box suggestion lookup, which is very similar to a combo box, but, you know, as you type in, in your your, into the combo box, it's doing back end searches and and giving suggestions and guests back from the back end to the front end so that the user can can select what they're what they're trying to do. Searching dialogues, as well as localization. Yeah. Again, we're expecting that to be coming out in in the next patch or so. Formatting, sorry. No. Not not... No. No. Localization is, language independence. We're working on that. That is not coming out in the next patch or two. Internationalization is imminent and coming out in the next patch or two. We are extending the Uniface UX with a formatting API. This allows us to be able to, to interpret data to to, to on the browser, to be able to display it in a, in a different way. So for an example of this is, you know, localization or sorry, internationalization with the with the dates. So is it day month year, month day year, etcetera. Yeah. That all goes through a formatting API, but that's built into the the the underlying APIs so that you can, you can plug your converters into it and then be able to get that information from... Directly from the API as it's running. Language independence is is something that we are working on. Saw some great demos, and it's great thinking about that going on earlier today. So, I'm looking forward to that coming out. On AI, we are concentrating on application insights, the ability to to understand, the application from the code, and any learning, learning pathways, certification badges, and translated, captions. I think translated captions are are mainly there now. So our vision across, for AI across Uniface, we think that there are multiple areas where Uniface, that we can enhance the Uniface ecosystem to make really good use of AI and to really help customers to be able to put change through, to be able to update, to be able to modernize, and to be able to maintain their applications and create their applications. We feel that, right at the very start of that journey is the application insights. So the application insights is the ability to be able to, ask natural language questions of your repository and be able to get back sensible answers, to be able to ask it to to look at a component and give suggestions on how it can be improved, to be able to say, you know, I have component a and I wanna get to component b. What path through the code does it take in order to be able to get there? Can you tell me how how it does that? You know, please have a look at, you know, this library and and what what does it do? You know, explain my component, that kind of stuff. You know, we we look at, Uniface applications. They are long lived. They have been, you know, a lot of them have been around for a great many years. Documentation is not always as good as it should be. You know, there... There's a lot of knowledge which sits in, you know, a limited number of heads, and we wanna be able to sort of democratize that information. And we we can't go into the person's head, but we can go into the code. We can go into structures. We can go into the components and be able to output that. So we're putting our knowledge around, you know, the AI to be able to help it, to be able to answer those questions. So we, we also wanna be able to, help customers who are on earlier versions of Uniphase get up to the latest versions of Uniphase. Yes, in order to be able to use the, the, to be able to use the latest functions and features which we've been talking about, but also to be able to, to, make use of the AI and to speed up development and that kind of stuff. The next step is the development and the, and the modernization agent, and this is to be able to go in and ask Uniface to be able to make updates to the application for you. You know, I am... I want you to be able to go... I I want to be able to have this in my application. Can you go away and do it? And, obviously, that needs to have a lot of control and a lot of, a lot of input around it. But, you know, we we, because, you know, we we have the the underlying, access to it all, we are able to to to to be able to, you know, put this into the product. But it relies quite heavily on that application insights to understand how it fits in. You know, you could probably create something quite easily which doesn't understand the rest of the application, but it doesn't really fit in with the standards and guidelines and and that kind of stuff. So we wanna be able to to use that application insights in order to be able to, you know, do the best job that we can on that development and modernization insights. Once an application has been created and it's being put out into the world, understanding how it's running becomes really important. You know, to be able to see what it is doing and how it's doing and the paths it takes through the applications, to be able to feed that back through the mod... Development and modernization and through the application insights to be able to enhance and and improve the application becomes quite a strong, quite a strong requirement with the development life cycle. And then lastly on the end there, is the AI enabled applications. We get a lot of requests about what are we gonna do, what are we doing for about AI within the unified development. Yeah. I'm sure the customers are also getting a lot of questions about, you know, how can, you put AI into their application in order to be able to help them. Yeah. And, you know, with this stuff we can do in order to be able to extend the Uniphase development, in order to be able to expose your application, to AIs and to be able to give that experience to your end users. And all of this has to be wrapped up under a a layer of governance and security. Yeah. So, you need to be able to make, manage costs. You need to be able to manage auditing. You need to be able to manage, and understand what is being done within the application. So there there has to be a a governance layer so that you can keep control of of what's going on. So, you know, it's not... It shouldn't be a wild west. It It needs to be controlled. It needs to be done in a in a proper and correct way, and you need to understand what's happening within your application. And you... That is, yes. You need to be able to do that, but also there are regular regulations which are which are gonna be coming out or or or are out that, that make that a requirement. It won't be, it won't be an acceptable thing to be able to say, like, oh, well, AI did it. You know, that's not gonna be acceptable. You need to understand it. Version control. You know, so Uniface has for for a very long time been repository based. There have been options, over the years that allow you to be able to go to to, either file based. So I'm thinking, you know, the u d six driver from Marchaire. I'm thinking, or to be able to keep a repository and, a a work area synchronized with the WIS listener, etcetera. You know, this is something that we have been asked for, pretty much every conversation we have. You know, version control is something that, you know, people have really wanted in the in the product for a long time, and, and we're working on that. And the idea is that, you know, we we need to be able to have, the information that is used within Uniphase. It needs to be stored. We need a single source of truth, so Uniphase needs to be able to work against that. And also the version control system needs to be able to work about, on that. So files are the way forward, you know, get Uniface to be able to talk files and get, and and then the files can be persisted by the version control system. This is something that we are are building into Uniface itself, to to enable that to happen. You know, our our concentration at the moment is to be able to output those files. We're gonna be expecting to be using the sort of the the native tools and utilities in order to be able to do the branching and the merging and the and the and the and the pushing and the pulling of of the the various different changes. When we look at the files, you know, we... We've had a lot of conversations about how the file should be structured, how they should be, and and how many files should there be. So, you know, there there are, you know, two schools of thought. One, there should be just a single file or there's two, there should be, multiple files. And we're going for that multiple file way of doing things. The reason being is that we feel strongly that the merging is the really important part, the really difficult part of, version control. And if we use different files, and file layouts for the different type of information that is stored within Uniphase, that gives us a a great... Greater ability to be able to to do that merging. So when we look at it, we'll think... We we think of things like properties within within Uniphase, you know, that they work very well as being JSON. Codes doesn't. Code, JSON doesn't allow you to to have, you know, doesn't allow you to have multiline information in it. So we have a sort of a disconnect. You know, we can force it in there. We can do it in a bit... In a different way, but then it becomes difficult to merge and difficult to understand. You know? We could change it to just be sort of like line separators, but then the whole code block becomes a single line. You know, if you've changed one character and then you really wanna see as part of that merge exactly what has changed. Right? So, you know, we would put, ProxScript out into text files, for instance, and the the form structure and the... You know, all this kind of stuff. Yeah, entities would have their own folders and would have their own file structure beneath it. Yeah. So we we think this is the the best way forward to give the the, the richest experience for the users. So what's to come after this? More on the interface UX. So we we... More widgets, especially around, navigation. We think that's an important area which we need to look at. Then we are going to be, adding in the, state handling into the unit... UX interface. We have, we have state handling in Uniface, but it's all server side. When you're starting to talk about the... This this, Uniface UX and the front end side of things, you need a different kind of state. You need something that is is wrapped up into that front end. So, yeah, we're we're looking at how how that best can be done, and whether that's a hybrid solution about, you know, it's front or back end or or whatever. Yeah. So there... There's quite a lot of work we need to do on that, but state is it we we think is a an important part. Code editor improvements, property editor improvements, and the ID, performance. Just generally, you know, we need to to look at what we are gonna be doing in the the long term around the development experience. So, the Uniface, development environment is very good at being able to visualize the inheritance, which is part of Uniface. That that integral part, you know, where where you get a lot of the, the the speed improvements in development is because you have the model and that inherited component. And the the IDE gives a, you know, a great overview on that. But as things like AI, and and other paradigms, sort of weigh in on development, you know, what does that look like in the future? And that's something that we we have to consider, and and we... Something we have to to work on in order to be able to, yeah, deliver the the ID that is needed for, you know, going forward into the future. We have a lot of currency, which we which we have on our backlog and we're gonna be working our way through. The next big thing after version control, that I would like to to be working on is testing. So this is, you know, you have the ability through the MSAA interface to be able to do end to end testing, to be able to drive uniface from, from the, from the the, you know, from tools... Testing tools like the one we use for Anorex, but, there are others on the market as well. But that's, that's a quite a heavy duty way of being able to test an application. Now we want to look at how we can bring these testings down to a lower level and to be able to unit test and integration test the Uniface applications. This is a a way of, you know, helping customers to be able to keep up to date with the Uniphase versions, to be able to, you know, keep the security, updates going. You know, it's, you know, we we hear from customers that the testing cycle of an application, you know, it can be sort of weeks, months, in order to be able to to test a new version of Unifax. And, that's sort of sort of a lot of, a down tools. Let's go and test this now version of, the application, and now we can deploy it. You know, we wanna help customers to be able to to to bring down that testing time. You know, and and with things like the modernization agent, you know, it sits in there a really good time that if it is able to to look at a component, to be able to generate tests for a component, you know, that really does take away, you know, some of the big barriers which people have had of of, you know, retrofitting tests through through within their application. The next thing that we we look at doing under AI is the application and development and modernization agent. So this is the truly agentic parts of the of the, of the AI. So currently, you know, we've been working on that application insights. We went into beta with it last week. We have got some work we need to do before we we bring it to GA, especially around the governance, the governance area of it. But, you know, being... I I found it quite impressive with what what it's been been able to to understand so far of the Uniface application. Going forward, the modern development and modernization would be the thing that we get onto after we go GA with, the, application, application insights. We're gonna be going then through the other parts of the AI journey, so operational, upgrade, and also being able to to put AI into into your applications for your customers. Development reimagined, I... I've I've mentioned. And, you know, as we go through, looking at, you know, is there ways of being able to to integrate the version control more into the IDE? So not just be able to read and write from these files and then use the external utilities and also be able to to persist it and to go through it, but also be able to to drive that from within the UniFace environment. Yes. There is, but at the moment, we find that as a a slightly lower priority than than actually being able to write to those files. And last, the, you know, the e learning. We've, we... We've gone through a bit of a journey of learning about how to produce elearning. And now, what we are moving towards, is a more, persona, oriented, way of being able to create courses to understand who would need which bits of information and be able to create courses which can be plugged together in order to be able to to fill in the information those require. So So there are bits of information that are required by everybody that... But there's other bits of information which are, you know, subject matter experts which might need to need... Might need to know but the salesperson doesn't. So you know, really working it through, the personas. And that's that's something that we have started doing and that is something that we are going to continue to do. So you'll find, if you look at the elearning site at the moment, there will be courses which are like, three zero two something. Yeah. And that's part of this, this taxonomy which we're putting into place. That will be... Become much more clear over the coming over the coming releases. But, yeah, we we we're quite excited about the the new the new course of it which which have been coming out. They've been very interactive, they've been, very yeah giving a lot of information, in a in a very clear and concise way. So, so available now, 10/04/2004. We've released it. We, you know, we we always recommend people stay up to date with the latest versions of Uniface. And, you know, we, you know, as I say, we we do do a lot within that runtime in order to make sure that the the security remains high in in it. Yeah. So, you know, we really do recommend that people, if they can't stay up to date with the latest versions. K. So in in progress, version control is is the thing that we have been asked for, the most, and that is the thing that we have been, you know, we're we're now working on, you know, with with Gusto, at the moment. Increasing of the the Uniface UX, that's an important side, but the the d b two, sorry, the, the AI and the application insights going into beta, and going forward into the AI world, is is something that we are doing. You know, we really want AI to be infused throughout Uniface, but we want it to be in a way that, it helps people to be able to do their jobs. You know, it's not... It shouldn't be... We don't want it to be AI for AI's sake. It's got to be able to add value into the product. Yeah. We have one vision of, AI across Uniface. You know, we want it to be able to help us to understand the application. We want to help to be able to modernize applications. We want you to be able to keep your application, you know, relevant to yourselves and your your end customers. And we need it to be able to do it in a safe and secure way. K. So, generally, that's what we've been doing. I was meant to finish probably ten minutes ago to give questions, but let's see if we can go through some questions now. Do we have any questions? There's loads of questions. File based structure, I'm looking... Okay. The file based structure, of unit based components is brilliant. How will the... Into Tableau in the forms being coded into the new file? Yes. So, the the paint tableau will, I don't exactly know exactly what the paint tableau, in the new files will be, but it will be, I think probably JSON. It will be serialized into JSON, in order to be able to understand it. Yeah. How long does it, how long do you expect those two bit uniface to be available? We know that we have a lot of customers who have got, who are using those two bit, you know, especially when they have got, COM, and, three three g l integrations within their within their environments which they still need to get to. We do not plan on removing it, anytime soon. But as time goes on, it becomes harder and harder to support parts of, of the platform. You know, if if Windows... If if Microsoft got rid of, Windows on Windows '60 four, you you know, we would not be able to any, you know, anymore do, 32 bit applications. But, you know, we will be continuing to do it while we can. But, you know, there are significant risks of, you know, different technologies becoming unavailable. The first one has been Java. Yeah. The rest of it, I think, is very much in the the Microsoft, environment. And I, you know, I think that Microsoft themselves, they're not going to be getting rid of it anytime soon. So, yeah, I I think 32 bit will will continue. Will the interface testing tools, be AI enabled? These are good questions. I... We we do not have a a clear, you know, this is what the... What what it's going to be... Look like, what it's gonna look like. I think that there will be definitely the... Well, there will will definitely be the ability to use the modernization agent to create tests. But there are, third party, testing environments which are out there, which might be, the best way of us going. So, you know, instead of us creating a test harness, yeah, we integrate with test harnesses. Yeah. So, you know, how we how we do that, when we we don't know yet, but this is where we we we plan on going. When did you expect virtual control to be available? I was hoping this year, but, realistically, I reckon it's gonna be q one next year. Yep. Plans are obviously... Yeah. That... That's the plans. They're subject to change based on circumstance and information as they arrive. So we came from distributions and service packs and patches. Later, we only distribution and patches. Now I'm a little confused. Release, we we always... Our service packs, yeah, we we release, all our patches as now both distribution and overlay patches. Yeah. I think that the important thing is that that that first number that appears, so version 10, tends to signify big changes within the development paradigm or development environment. So from, you know, eight to nine, from nine to ten, from ten, to eleven, you know, there there have been big changes in the development, environment. Yeah. So that tends to to do that first number. The second number tends to be, or we will increment that based on, the... Whether we need to do an export import migration. So we've changed the repository in such a way that we need to have it exported, clean repository created, repository created using, the scripts, and then importing and a migration process in order to be able to to, to be able to adopt it. Yeah. Within there, we will probably have larger changes. Yeah. Then we have a service pack, which is again, which is an overlay. So it will... You can just take the service back and use it against the repository. It will have small... Minor incompatibility changes, and it will get rid of the, it will get rid of unsupported operating systems and databases out of the path. Yeah? And the last one is the patches. That is the, when we will we will put new functionality in, but we will not be putting breaking changes into the patch. Yeah. We release everything as, a... We release service packs and patches with both distribution and overlay. Yeah. The distribution has two modes in which it can operate. One mode is an installation and the other mode is an upgrade. Yeah. And if you use the distribution to do the upgrade, it will do, it will update any files and assignment files with new settings and and and processes. So it would be the way we recommend that people update it Uniface. However, we know that people have had many years of having the overlays so... And have got, scripts and procedures around updating Uniface. Yeah. So we continue to support... Supply them as well. Yeah. Ideally, you could just use distributions, to do it rather than the overlays. I hope that helps. Version control being available. What is the expected roadmap for version control? Yep. And I saw, will AI help me migrate a desktop application to web application? That is a question that, that has been coming up for quite a long time. The... We plan on... We we... I think, yes. I think that there is the the... There are going to be sort of routes which you can go through on, AI in order to be able to to do that. So, I think a lot of what we need to first of all do in order to go from desktop to to a web application is to sort of modernize the code base. So be able to, move code from a monolithic application into something that is structured, more appropriately for a web application. So application modernization, the agent... The agentic side of things there, then that is absolutely something that is... That, that it should be able to do. Yeah. The next thing is then be able to take that front end and to be able to, to be able to translate that into a page which can drive those back end business rules once they've been componentized or or brought into a into a better way. So I think that there is a path that we... That you could that you could go through. But I think there's also... You know, it is worth us trying to find out whether it is something that we can do in one go. I'm sort of at the school where perhaps a a big bang isn't a great thing. Perhaps we have to do it on a on a a a more incremental basis and then get, get the, yeah, and be able to... Yeah. And to be able to take a steady pass through for our table as well. We are not for the version control. Would that be usable for the configuration for our tables as well? At the moment, we are looking at the the the ticket tables, and the repository. There are... We keep on having conversations around, around, you know, what can we do for, data tables as well. But, David, I think I would really like to have a conversation with you to understand what you would like to try and get out of it, if that's possible. Does it all, always say ten four slash two? I'm not sure what that means. Okay. We are we are over now. I'm I'm happy to stay on for a little while, but we are over now. I think either we, we continue on for a little while or we, you know, I can take these questions offline and and make them available, as as... You know, with answers. I... I'm so sorry. I was just going to quickly say it would be a great idea to... If we don't want to stay over, we... The survey's been launched, and there should be, like, an open box where we can gather questions and feedback. Okay. I can leave that with you, can I? Perfect. Yeah. Okay. Is there already, sorry, I noticed a quick one. There is already a component certification application for Linux. That's Windows only at the moment. We have had several requests for it on Linux and we have to figure out what we can do there. Oracle 26 AI is already on the 10.4 PAM. And the SAAST tools, there isn't... Yeah. But this is a... I think that the SATA tools... I think we have to understand what it is we're trying to get out of the SATA tool... SAST tools. You know, what what is it the, what output are you trying to achieve there? Yeah. Okay. I'm sorry for going over. Think of all most of the questions. And, okay. In in which case, I think that, we can call it a day. Perfect. I was just trying to unmute. I think it's a great closeout. And if anyone has any further questions, just make sure that you respond to the survey. And thank you so much, everyone. Thank you.