Co-work Creator Is Collapsing Into One App

I think it was Michael that was next.

Michael Pye 20:22

Yeah, thanks, Colm. Thank you. So, yeah, the priority for Co-work Creator over the last week and moving forward is the, I guess, the consolidation and getting ready for wider adoption and go live at the Co-work Creator application.

And I wanted to touch on a bit today on a bit of clarity over what the go forward plan is and how we've been approaching the kind of UX refresh of the co-work creator application. So some of you may notice that if you kind of go into the various environments. We've got our kind of agent builder application, which would be one and co-work creator, which are now marked as old.

And then we've kind of got a new application as well. And the go forward plan and as part of the UX refresh, we will be moving forward with this kind of, with the co-worker creator application that you see on the screen at the moment. And we're reporting more and more capability over to this new application over time.

But there's some fundamental kind of differences as we set up for this as well, and it links a little bit to the connector update that was given around ADE as well and the importance of connectors. and how they fit into the wider ecosystem and the platform pillars that we're creating. So I'm just going to kind of go through a few steps. So you can see we don't have like for like every process at the moment, but this is work in progress.

I'm just going to create manually for now. Select an icon, provide a description, all the kind of standard stuff that you've done previously, and click next. So one of the kind of fundamental changes now, if we look at the different processes, is the use of the connector catalogue itself.

So it's really important that we're registered, and I know we've got the hackathon or connectors on coming up soon as well, that we consider registering our connectors with the platform so that they're available to select previously in the old applications. The connections to the data would be made kind of per agent and registering them with the connector catalogue means that they're available for use widely across the PERS. But also we don't need to be registering the same details over and over again through a customer angle.

It also means that they can be accessible to customers. in a streamlined way as well. So that's kind of the fundamental differences as we move forward. And to support this, we have launched a new set of documentation as well that's now available, which I'll post into the chat.

And yeah, it was really just some clarity that we wanted to bring and then a kind of summary. So our view as we move forward is that there's one co-worker creator application that will be used internally and for customers. And we're undertaking A consolidation over the next two weeks.

And the new kind of UX refresh version that you see is the one that we'll be moving forward with. We ask that people use the latest app, but like I said, there's not full like-like functionality at the moment, so the old applications do remain in use and reach out if something's not working using the agent builder general chat. And if you've got existing agents out there at the moment, that are connecting to our access application data, then do register your API as a connector so that they're available for wider use across the platform as well.

And these links will be available in the deck when we share it after and the documentation link that's been provided as well. So hopefully that provides some clarity over why there's different applications and yeah, And our priority now remains on consolidation and simplifying the end-to-end journey.