Name: The FSI Advantage: Accelerating Innovation with Workday Extend
Uploaded: 2026-05-20T18:33:55.584Z
Duration: 58 min 4 s
Description: The FSI Advantage: Accelerating Innovation with Workday Extend

Transcript for "The FSI Advantage: Accelerating Innovation with Workday Extend": Alrighty. Good morning, everybody. My name is Ross Leader. I'm with Workday, of course, as an enterprise architect. Thank you for joining today's session on extend. Before we get rolling, quick call out to our product statement. And I don't know who's sharing right now, but maybe I'll take over the sharing here. One second. Oh, I see. It's it's just about okay. Great. So quick call as to our product statement. If we do talk about anything that is forthcoming in our product road map, please bear in mind that this is always subject to change and make your purchase decisions based on the, what's currently available in Workday. If we do talk any roadmap items, I'll certainly make those callouts as we go along. Our next slide here is just about housekeeping items. So this webinar is being recorded. We're going to send you this recording within twenty four hours. If you want to ask questions, we certainly encourage that. So please utilize the Q and A on the right hand side to ask questions. And then if there's any resources we service out there, you'll be able to download those from the resources tab. Just look for that docs on the right hand side to download any of those. And please post webinar, we are very interested in your opinion on how this went, what we could do to improve. So if you could answer a short survey after after this session, that would be greatly appreciated. Alright. Today's panel, we have, we have, myself, Ross Leader. I've been with Workday for five years now. I'm out of the Denver, Colorado area. And my focus is the platform technology that makes Workday tick. So everything from our core object model to our microservices architecture, to how we incorporate new and emerging features like, of course, AI and rapid app development. I'm joined here today with Kevin Wilkins and Pascale Shakarzyan. I hope I got that right, Pascal. But Kevin's with us from Workday. We'll give an opportunity for everybody to introduce themselves when we hand off, the microphone. And then Pascal is joining us from one of our Workday partners, Kainos, and they're absolute experts in the realm of Workday Extend. Today's agenda, we're really just gonna cover what the power of Workday can do for you and your organization. So understanding the value you can unlock by building where your people and finance applications live. We're going to talk a little bit about orchestrate and how you can leverage that embedded integration platform as part of these applications to automate and rapidly incorporate other areas of your technology ecosystem into these applications. Also talk about what's new, what's next in the platform in terms of, you know, what's, what's on the horizon for Workday as we continue to incorporate AI technologies into it. Then we'll hand it off to Kevin Wilkins who's gonna talk about ready, set, deploy. How do you get started? Where do you get that first, you know, inspiration for an extend use case and how do you make it happen? And finally, Q and A, next steps. We're here to help. So certainly welcome your questions throughout but also have some dedicated time here at the end of our sixty minutes to go through some of those items So moving right along, what is extend really about? Extend is about bringing that power to build, to customize, to tailor that works in environment to the specific needs of your organization. So we do many things in the realm of people, finance, spend, but we can't cover every use case for every customer, of course, and that's where extend comes into play. The advantage of extend is it's really the right place to be building applications that have anything to do with your people, with your money, with your spend. The reason for that is we deliver this pristine object model. And that object model, of course, you know, delivers on all sorts of different functionality. But if you have something specific, we wanna introduce your own business processes, your own validation roles, but do it in a way that's familiar for your user base so they don't have to have a new login, have to orient themselves to a new UI or new user experience. Extends a great place to do that. It also means that not only are you getting the benefit of familiarity, but if you want to turn an app into a mobile app, well, just make it a part of that Workday native mobile app experience. It also means you don't have to worry about things like how performant is this going to be? What kind of infrastructure do I have to light up in order to make this new application possible? That is an embedded part of your Workday experience. Along with that, security and trust is built in. If you've invested time and energy into that security model to make sure that, hey, things are really workflow driven when we hire, transfer, terminate, promote, whatever those life cycle events happen to be, or even on the finance side, we've reorganized how we're, signing the cost centers, restructuring our business in a financial way. Those paradigms, that context comes along for the ride, which is a huge benefit because those are the types of things that are really difficult to replicate outside of Workday. Workday has that real time information about who you are, what your role is, what you have access to. You can piggyback right on top of that with Workday Extend. And lastly, connected to the enterprise, Workday really, you know, since our inception, we knew that we weren't going to be the be all end all system in an IT environment and integration is important. We've compounded and enhanced over the years how integrations can be handled in Workday. And one of the core fabrics to that is what we call Orchestrate. And not only does Orchestrate allow you to have real time event based integrations with your extend apps, but it also, we're also bundling in tools to make orchestrations that much easier to incorporate into your apps by using the power of AI development. So what does this all look like? Well, an extend app looks, acts and feels just like, you would expect a decor delivered Workday experience. So you're still logging in with the same account. It knows who you are, and you can surface those applications in a natural way. So do I want to make it available through the search bar? Do I want to have it as a related action off of an object? Let's say I've got something around spot bonuses and I want to be able to allow managers to reward their team members by simply using that related action off one of their team members. Well, the security model says, hey, they're part of your team. You can go in, you can take that action, you can light up that, unique app. And we've also introduced in the extend paradigm, what we call cards. You may see cards on the welcome page and some of our hubs. It's a really great way to surface real time information from any system right where they're already naturally working. That's really the key when it comes to extend is like, let's not add new layers, add new user interfaces. Let's just make things as familiar as, they would expect it to be with with their work experience regardless if that's within, the application or external. I already mentioned so, I already mentioned that object model, but extend also gives you that ability to bring in unique data to your organization. So you so you can, create your own business objects that look, act, and feel just like the native objects Workday delivers out of the box. What does that mean? If you're investing in development resources to create, extend applications, once they publish those and go live on those and you have, say, your reporting analysts or other Workday users that want to be able to report off of this data, the paradigm is really no different. Security and auditability, of course, is built in. You can see what everybody does, views or does in the application just as you would a core delivered Workday process. In the top right there, business processes. You already know that Workday delivers thousands, over 500 business processes out of the box, for the various workflows within your environment. S then gives you that ability to create and publish your very own Workday business processes. Already mentioned connecting with third party systems. We'll do a very short demo on what that looks like. But I'm also happy to, share that Workday comes with pre built Prism connectors as well. So you can leverage that investment, taking action to update your Prism data sources or leveraging that data as part of an extend application as well. We can also do that with what we call Workday journeys. So if you have journeys as part of your user experience, you can take care of that as well. So just to go and do a short demo before I hand off to Kevin, Just gonna do a quick change on my screen share here so I can share out one of our browsers. And any questions pop up in the chat while I'm making this transition here? Alright. So let me go ahead and share. And Go. Let me do my entire screen. Sorry for the delay there. Here we are. Alright. So, can somebody confirm you can see my screen okay? We're seeing the Workday developer site? Alright. Super. Thank you, Christine. Alrighty. What we're looking at here is the Workday developer site. As part of Extend, you get access to this. This is the central hub for creating applications, for learning more about Extend, for monitoring those applications, and also promoting them through, the various environments you might create an application with. As you can see, I'm in, my particular, we call it company. A company is really just where you're organizing those, basically the promotion path for your application. As you can see, I can take action. I can build an extend app from scratch, build an integration app, manage the applications I have in place. I also have useful resources for learning more and also discovering how to interact with the environment. One great example of that, developer copilot for APIs. If you have an idea and let's say that idea has something to do with aligning an employee rewards platform with feedback. I can just ask, hey, how do I get real time information on where, on employees giving their peers feedback so I can leverage this for spot bonuses. We're giving you the power to cruise through all of the various APIs Workday recommends so you can start to craft that business case, come up with new ideas and be able to design that application. We didn't just stop there. You can continue this conversation and say, you know what? I wanna include this in something headless like an integration app, wanna have it in home card, or I wanna include it as part of an extend app. Workday is really investing with what we call with extend to give you the tools to discover and really frame up what kind of things you wish to execute with Workday. We're also embedding AI at the build experience. What you're seeing here is a quick demo on how to create pages using the power of AI. I can narratively say, Hey, I want to expand on this idea and I want to make sure that there's a user interface for granting recognition rewards based on performance within this application. What we'll see here is, again, we're naturally prompting Workday Extend using our developer copilot to generate these components. The platform is powerful enough to say, Okay, I understand the data sources you're looking for. I get the gist of the user interface you want created here. I'm going to produce this both in a visual and a code fashion so you can simply add this to your app. It's adding the user interface components. It's also adding the, the API calls that are pertinent to that application. Now, obviously, that was a video, but I can show you this is live, available, and being used by our customers today. This is available to the Xtend Pro level subscription. And, as you can see, I have the ability to do that with my own application. Here's a similar application, the employee nomination app. I can go into what we call app builder, and this is my palette. This is where I can influence what this build looks like, and you can also take advantage of live preview. Actually, this nomination create page that I created is something I generated using AI. But if I want to make changes, I also have this visual palette to go through, make those changes, and then preview them in real time. Every Workday subscription comes with what we call a development tenant. This is a powerful tool and a really helpful paradigm because it's an additional Workday environment that's been preceded with stage data. What does that mean? You've got mock data available for your developers to tinker with, so you're really cutting down on the amount of exposure of production data that folks, would see during that development process. Really can open up the field for when you're bringing in external resources as well. Hey. We don't have to expose additional folks, to to things they don't need to see. With AI, we're not just stopping in the development side of prompting to create queries, to create pages, to create graph mutations, those types of things. We're also making AI tools available within the context of an extend app. So you can see here, I've got generate feedback as a button. And the way this works is you could bring in, say, to a rich text box like this, the help of generative AI. What you're seeing here is the visual builder for this particular box. I've put in a generate feedback prompt. What this does is it, hey, give me a 10 word feedback statement from this particular, what they've entered, and then creating a new feedback statement around that. We're actually tapping into the Gemini model and embedding AI directly into that application experience. What I'm not able to speak to or really show, but I would say, if you have the opportunity to come up to DevCon or attend virtually, there's gonna be a big, big announcement on, how we're enhancing Workday Extend and how that ties into the creation of agents and having agentic experiences be a part of that extend development as well. Last thing I'll show here before handing off to Kevin, beyond the generation of components is developer Copilot. Another thing we're going to be introducing, this is still safe harbor applies, is the ability to create what we call orchestrations based off of generative AI. So this is still going on that narrative of a recognition award. And but we're saying, hey. We want this award to come from an external platform. In this case, it's a it's a company called Tango. And What we're gonna do is we're gonna create that integration using a narrative declaration. Hey, I wanna create this. I want it to look up the worker information. I want this information to get over to Tango, and I want Tango to be able to return the result that a gift card's been issued, include this as as payroll input and make it a taxable event. It is possible. It is coming with what we're calling this, this orchestration copilot. We're actually having it create the step by step integration events that can be a part of your extend deployment. The other wasn't totally evident here, we can also include resources from those external systems like a YAML file or a OpenAPI specification. And the system will read that in and create all of the components that would go into that. So we're saying, hey, let's start this based on some kind of trigger. We're gonna get the worker information. We're gonna format that. We're gonna create a text template to send that, as feedback. And then continuing on through this, calling that external system to issue that gift card and finally closing the loop, to to have that logged and detailed. So all these tools are available right here visually in Workday. A lot more is coming into the agentic side of things. But if you're not taking advantage of extend today, highly recommend going in, exploring that developer portal, going through the documentation, and then seeing some of the applications you can get started with today, where you can actually download, view applications that we've built, modify these to your liking, and really learn the platform and start building, building value for your organization. So with that, I'm a bit over my time. I wanna hand it over to Kevin, and I'll release the screen share here. Awesome. Thank you, Ross. So now that you've seen, you know, what are all of these features that are included as part of extend and extend professional? The next question is, well, how do you actually get started using the platform and building out applications for your enterprise? And here's what we typically see. It's it's a bit of a journey going from, hey. I have no experience in building applications to building full fledged applications within your enterprise. Usually starting by having ourselves or a partner come in for that very first application, being able to showcase, hey. This is what you can do, and get you successful with that very first use case. That gives your team the opportunity to go through things like training, use some of those app catalog apps that Ross was showing you just a moment ago, and really be able to get your team up to speed on the back end while doing some knowledge transfer around that first use case. After that, both us as well as our partners have a multitude of services around things like advisory. They're a little bit lighter touch where your team's gonna be building the majority of the application, but you have that second set of eyes over your shoulder helping guide you throughout that process. From there, we have a number of low touch, options that are available through our our developer portal. So Ross was just showing, hey. We have these, tons of applications that are available. I think there's 40 some odd within our app catalog that you can get started with today. It's as simple as going out there, clicking copy, and that's going to automatically pull that into your development environment so that you can deploy that wherever necessary. We also have our developer site and our developer forum, which are a phenomenal resource so that you can more understand how to leverage Xtend and what are some of the gotchas that other people in the community have run into as they've been developing application? Now when we look at what skills transfer over well into Workday Extend development, we really seek two different personas. One is more of that business analyst. So somebody that has a really good understanding of Workday's core technologies. They know how to configure business processes. They understand how security interacts throughout the tenant, your new reporting. Those are gonna be the individuals within your organization that help take those business requirements and translate them into the more technical requirements for your developers. On the developer side of the house, typically, a background in something like web design is gonna be helpful. So if you know HTML or JavaScript, learning PMD scripting and JSON for the PMD files is going to be extremely easy, especially with some of these enhancements that Ross was just showing off when it comes to Workday Extend Professional. We've got a drag and drop interface for being able to create the pages. You can then leverage AI to help you generate the queries that you need as well as the pages themselves. But it is still good to have that developer persona engaged in case there's any more advanced scripting that you want to pull into your application. Additionally, if you have somebody with a background in maybe database management or data modeling, that can be incredibly helpful as you're creating new objects and making sure that that fits in with the reporting requirements that your organization has. Once they kinda get their feet wet, they've taken a look at some of the documentation, I highly suggest that you check out our developer tutorials. Much like those sample applications, this serves as a really great place to walk through at a granular level the different pieces of functionality included in Extent. Everything from creating orchestrations to pages. This is gonna walk you through all of the steps needed to start creating the applications that you need within your enterprise. From there, go over and check out those app catalog apps. Yet again, it's a great way to kind of see an example of how these different pieces and parts and building blocks that we talked through in the tutorials can be applied to a real life use case. Now we understand that self paced tutorials and and looking at sample apps might only get you so far. We do have more formalized learning that's available to you through Workday Learning aimed at those two different personas. So for that business analyst persona, we have our Workday Extend for Non developers course. This just walks them through what all is involved in creating a Workday Extend application. What are those touch points with core Workday? And how can you take those business requirements and translate them into something more technical? Now on the developer side of the house, we have two different courses. The first one is more like an intro. It's building your very first app. Think of it as the hello world application of Workday Extend. It's gonna showcase how it interacts with core Workday, how orchestrations come into play, but it's gonna be pretty high level. Then we have our deep dive where we really go into model components, how you can create new objects, how those relate to Workday core objects, what that means on the reporting side of the house. And most importantly, we're gonna do a deep dive on, orchestrations because this is gonna be how Workday Extend talks not only to core Workday, but to your external systems as well. Now another great place to kind of get the gears turning and figure out, alright, how do we want to start leveraging this, within our organization is this Workday solution marketplace. So if you go to marketplace.workday.com, and don't worry, we'll share this out in the chat as well, You can take a look at some of the solutions that our partners are building. You're also gonna see our built on Workday applications that are available. So it's a really good idea to go and look to see if there's something that matches with your organization's needs because you may be able to just reach out to a partner and start leveraging those solutions, or at least get an idea of, hey. I I like how they did it. Let's see how we can do something similar within our within our organization and really start to build out things that are gonna advance you advance your enterprise. Now, as I mentioned earlier, at first you're probably gonna be engaged with a partner or with our professional services to help you get started. But once you've trained that team up internally, we have a number of support mechanisms for you here. Through learning, we've got our on demand tutorials that we talked through, those catalog apps. We also have our app building tools like the AI enabled, app builder that Ross was showing earlier. We have our community both through our our normal developer site as well as our developer forum. This is a great place to be able to get up to speed on the latest releases. You'll see our developer relations team out there quite a bit posting and showcasing some of the new functionality and letting you know how to use it. And then, of course, we have more formalized support if you need things like app guidance. If you're a WSP customer, that's something that you can you can leverage. But we also have DevCon that's coming up or developer conferences, as well as, of course, if anything goes wrong, the typical support mechanisms by creating a support case. Now hopefully this gives you an idea of what all is involved. I mentioned earlier, you know, we have some additional options if you do have WSP where we can get in there, help you design an application, help you build an application, or just take a look at what you've built and serve as that second set of eyes to make sure there aren't any anti patterns that have been implemented. But probably the best place to get started is with one of our partners here. And in fact, I'm gonna be joined by Pascal here momentarily so he can walk you through what KANOS is doing out there in the ecosystem and showcase some of the amazing work they've been doing. Thank you, Kevin, for introducing me, and thank you for us for pronouncing my surname correctly. So I really appreciate that. So I'm Pascal from kNOS. I'm a senior engagement manager, and we'll be taking you through some, slides that we have prepared. We'll walk you through how kenos helps organizations bring what they extend and AI into practice. What we've seen so far shows what's possible, And what we're going to focus is how to turn this into real tangible outcomes for your organization. Okay. That worked. That's great. So what we're going to do over here is at Canos, we bring to you an end to end extend capability. So this spans across customer, sorry, custom and repeatable application developments, deep expertise across extend integration, security, and the marketplace, and the proven delivery at enterprise scale across both HCM and finance. We're also seeing a strong shift toward AI enabled extend solution, which is where a lot of innovation is happening today. Across our experience, we've supported, as you can see from this slide, over 100 customers, built more than 160 applications, and that number is growing, and have a dedicated extend team focused purely on this space. From a services perspective, we typically support customers across four areas. In these slides, we're going to focus only on three of them. We're going to focus on bespoke solutions, template applications, and extend strategy and center of excellence setup. So starting with bespoke, extend and AI solutions, this is where you as an organization have a specific idea, something unique to you, and we will help you bring that to life. These solutions are, since they're built in Extend, they will be secure and scalable. That's by design of Forti, designed to simplify user experience and increase the leverage AI and agent based patterns. Because they are built directly within Workday, the experience is fully embedded, there are fewer integrations, and reduces reliance on third party systems. Some examples of these solutions we have done so far are credit card management, travel management, license tracking, promotion, and nomination processes. Ultimately, this is about you as an organization taking your workday wish list and turning it into real applications that improve how your business operates. Next item is template extend or AI. If speed and time to value are important, we also offer a template based solution. What are these solutions? These are pre built, repeatable applications. They're designed to reduce both build time and risk and also allow you to run these applications quickly and set them up and achieve value at a lower cost of entry. Some of the examples of these solutions we have, there are four of them highlighted, which we have conflict of interest, rewards and recognition, AI three sixty feedback, and words counsel solutions. You can see on the slide we have a QR code over there, which is aimed at, if you want to see the full catalog, you can just scan the code or when the slides are with you, you can access the full catalog from our side. Our follow-up offering is associated with, what they extend strategy and center of excellence. For organizations, earlier they are early in their extended journey, strategy becomes a critical piece for them. At Canos, we help customers define where extend fits within their broader architecture, identify high value use cases, and align with Workday's roadmap and platform evolution. Beyond that, we support building a structured approach, establishing delivery standards and patterns, setting up governance and release processes, and enabling teams through training and capability uplift. From there, we move towards center of excellence model, which is organizations might want, like yourselves want, to continue the journey. What this does is we build internal expertise, we scale adoption, and reduce long term, running costs. How we deliver these, solutions comes in a four step approach over here. So we engage over a few weeks and leave you with tangible outputs. These include extend reference materials, a clear adoption strategy, a prioritized application roadmap, and in some cases, your first proof of concept of an extend app. The goal over here is to give you both direction and practical starting point on your extend journey. In our next slide, we're going to go through a demo over here for one of our templated apps, which is an AI enabled three sixty feedback solution. This is fully built within Workday. The aim of this demo is to showcase how this experience works end to end. Yeah, the I I need to share the video, so bear with me a few seconds while I stop sharing and resharing the video. Okay. Success. So let me start the video now and walk you through what is, the apps are doing. So So the user over here can provide ad hoc feedback at any time by selecting give feedback to and searching for a worker. This experience is open across the organization and allows feedback to be shared outside of the formal review or nomination cycles. Once selected, the user can go through a formal feedback and nominate and provide values or dimensions using simple slider controls. Each submission is stored as an individual feedback entry for that particular worker. Over time, the workers will receive all these feedback, and they will be provided using AI to provide a clear balance view. So next step is the end of the nomination cycle. At the end of the nomination period, administrators can use the managed feedback hub to formally close and end the cycle. Closing the cycle prevents additional feedback from being submitted while ending the cycle signals that the feedback is ready for analysis. This step enables Workday to start beginning generating AI powered feedback summaries. The next one is launching my team's AI feedback. From this page, from a managed perspective, the feedback hub provides access to AI powered feedback for their direct reports. Managers can launch the AI feedback summarizations directly from within the hub with a single action. Viewing team members' AI feedback. So in this, in these pages, when viewing a team member's feedback, managers see an AI generated summary that consolidates key themes, strengths, and development signals across multiple feedback entries. This allows managers to quickly understand the overall sentiment, the patterns without reviewing each single individual submission, and supporting more meaningful coaching and performance conversations. As you can see, it's exhaustive in the way it's done. It's all configured how, in your organizations, you want to capture these pieces of feedback. Next section is displaying AI feedback to worker. Managers are always in control whether AI generated feedback summaries are shared with employees. This enables the manager to review the content first and determine the right timing and contest for sharing. Then we have the employee feedback received. Managers can choose to share the summary. The employee can view their AI generated feedback directly in Workday, and this provides a clear consolidated view of feedback received, helping employees reflect on strength and development areas without overwhelming detail. So together, this experience supports continuous feedback, thoughtful reviews, and AI assisted insights while maintaining managers' oversight and transparency for employees. So I think you need to go back to the slides now. So I'm gonna stop sharing. And maybe, Christine, can you share the slide deck? That's great. Thank you. So finally, if you're thinking about how extend could help your organization, at Canos, we offer discovery workshops to help you identify use cases, balance custom innovation with reusable solutions, and define a clear path forward. There's a QR code on your screen. You can scan it to schedule a time with our sales team. And also, if you are attending DevCon, we are there. We are at DevCon. So please feel free to connect with us in person while you're attending, DevCon. Thank you all for your time, listening to us. Alrighty. Thank you so much, Pascal. We've now reached the Q and A part of this webinar. We're welcoming questions by using the Q and A, feature on the left hand side of your webinar screen. We also welcome you to raise your hand if you wanna ask something live, you don't feel like typing it out. We are more than welcome to take those in as well. If you do submit a question through the Q and A, it is anonymous, your name won't go out there, so feel free to ask any question you might have. We did have a couple come in so far. Why don't we kick off with one of the more basic questions we got is, what skills are required to build extend applications? I'll introduce this one and I'll start with my perspective is that the types of skills that are helpful in building extend apps and understanding of web applications, HTML, JSON, as well as some kind of grasp on syntax. That could be JavaScript syntax, could be from Python, just some sort of understanding of how logic is created with an application. Now, with that said, in today's state and where we're heading as a platform, by having developer Copilot and the API explorers and the generate component AI features of Extend Pro, we dramatically reduced that barrier to entry. And while I still think it's important to have some of those more technical skills, you can look to your broader organization to to be a part of the process. So rapidly prototyping extend applications, why not have business analysts or other folks in your business that really understand the requirements instead of documenting those in Excel spreadsheets? Get in there, get their hands, dirty and actually create, mocks or, you know, minimal viable, functional applications that you can then hand off for further development. So really getting closer and closer to a zero code paradigm, Extend is truly heading there. So it really opens up the the population for who can contribute to build and actually have a safe, lawful citizen developer kind of program within your within your environment. Yeah. And I'll kinda double click on that as well, ahead. Ross. It's something else that we've seen beyond just shifting a lot more of that work over, into that more of that, you know, business analyst persona. A question I then get is, alright. Well, there's still the need for developers. Do I need to hire, like, a full, you know, full stack developer to be able to create extend applications? And what I like to say is, if you've got an integration developer, you've got an extend developer. We're calling the same APIs on the back end. We're leveraging orchestrations. Being able to learn the the tooling for the UI is fairly straightforward and easy as you were showing earlier. You know, it's a drag and drop interface for the most part unless you really need to go into the code view. So, again, if you've got an integration developer, I think extend is gonna be kind of the natural progression there as well. Definitely. Definitely agree with that. Next question, Kevin, is actually for you here. How long do these deployments typically take? Yeah. I'll say it's kinda like building a house. Right? It depends on how big of a house you're building. You know, with these extend applications, we see customers be able to build things incredibly quickly. In fact, in my prior life, as a developer, we had a customer that had a very urgent need. We were able to get something live in less than four weeks. That was from the time the issue was identified, went through planning, created the application, had it live in production. Now is that typical? No. I'd say typically we're seeing around the twelve week timeline to get something put into place. We also have applications that have been incredibly large, that have taken much longer. So it's gonna depend on on how big of an application, and we highly suggest using a more agile development process so that you can get application features in place very quickly, get it back in front of your users, and start to iterate on those apps moving forward. Nice. Thank you. Alright. Our next question is around, hey. I've created an application and I wanna share it with another customer, with another Workday user. Can I do that safely, securely? The answer is absolutely yes. When you create and build within Workday, of course, your code is saved to the developer portal. You can certainly syndicate that out to a repository of your choosing, as well. But if you want to share that application with others in the community, simply export it out, and you can also collaborate with other extend developers on the Workday developer forum, which is a great way to make those connections, find out what other people are doing with extend. And remember, you're starting this development journey using a mock tenant, which which is not your data. You get to promote it up through your implementation environment, your sandbox environment, and eventually your production, which of course has your data. But the starting point is, is is a common foundation that all developers are working off of. So it makes sharing and and collaborating with the Orkta community, quite easy. Alright. What other questions do we have? Let's see here. Alright. Complexity. Is it hard to maintain these applications? We get this question a lot, and the truth is Workday Extend applications are update proof. Now, of course, we make changes from time to time with our APIs. And if you have an underlying API, and the version happens to be on a deprecation schedule or retirement schedule, you're going to get those notifications through the Workday community as an aims for contact to take action at least eighteen months ahead of time before that API changes. But bottom line is there's not a whole lot of maintenance required when it comes to extend applications because of that core Workday architecture. Everybody's on the same version of Workday. We do version resources you may be dependent on, and we're only taking those hard making those hard decisions to retire a version of an API or to retire a feature that you may be dependent on, if we absolutely have to. Kevin, I don't know, or Pascal, if you wanted to add anything to that question. Yeah. I mean, what we've seen as as you you've highlighted over here, it's it helps the organization to maintain less one extra tool outside of Workday and comes with all the technical debt that comes with it. So within with having an extent app built within within Workday is a lighter way to manage these, the app itself, and you can self manage it internally if you follow-up the training with the extend. Something that we help our customers with KT sessions after delivering the the app itself depending on the complexity of it. The KT sessions are aimed to make sure the organization itself and their, IT people are able to manage the app and support it internally. Eight. Perfect. And the one thing I'll add is we have customers that have been live with applications for years now that have not touched them at all. Still running even though we've gone through multiple upgrades, within the core product. And that goes back to what Ross was saying earlier. Right? All of our APIs are versioned. So unless we're deprecating an API, which you get a ton of heads up on, there's no need to to go in and change the application as long as you're not running into some, you know, data error or something along those lines, you know, further down the road. But tons of customers that have had applications live for years now that have not touched them since go live. And this next one I'm gonna I'm gonna give Pascal an opportunity to respond to first. How do you decide between a custom app and a template, when when you're when you're deciding whether to build or or buy or to adopt something that maybe Workday offers or is offered externally? Yeah. I mean, usually comes down to speed versus how specific the app itself for the organization that are asking for it. The way it is, for example, we have apps that are templated like conflict of interest or feedback. Usually these apps come with some element of customization to meet the organization need. But these are faster to deploy and it's a quick starting point to have value quickly from these apps, not waiting until we have extensive requirement gatherings or design sessions. These app have been designed before, they're proven to operate, and with minor customizations, you get value quickly out of these apps. When it is a custom app, it's usually, it's more unique to your organization or specific to a process. We have clients within the FSI that are looking for example, greater assessment. This is specific for their organization, and we're building an extend app that does a lot of things that are not required by other organizations. So that's where it comes as a bespoke app, follows particular processes and practices within the organization to ensure they have a functioning app. We discussed that as part of our engagement to understand what are you looking for. If we have an offering that is template, we would push that forward because that's where you can get your, market you get quicker go to market, outcome within your internal organization, and you get your value much faster. Awesome. I see we've. We had around the reporting data as well. Ross, if you want to address that real quick. yeah. Yeah. So the question came through is, does, does Workday help kinda solve for some of the pain points you might be experienced on on getting data out of Workday. Does extend get around the same data model constraints, or is it mostly working within the same underlying object structure? The answer to that is with Workday Extend applications, you are you can create your own first party business objects. In other words, you can define new things that live as part of that object graph. All the conventional ways that you may be accessing the delivered graph still apply. It sounds like the constraints are still there, but I'm going to add a little bit of context to that if I can get back to my my screen share here. Where did it go? Shoot. Oh, there it is. Sorry. Still getting used to the, the interface here. But with Orchestrates, not only in your application can you define your own object model, but another, approach that we're starting to see more and more of is instead of having to extract data, why not leverage Orchestrate to design it so that it's event based and actually publishing data out as it happens. What you're seeing here is you can actually create an integration that triggers off of, say, a business process or on a schedule, and you define what elements go out at which time and in what format. You can reverse that model and have this perform in a way that, hey, if this condition happens, why don't we just publish this information out to whoever needs to read it? But again, you get with the app builder the ability to define your object models, and those object models can tie into natively, delivered items as well in a secure fashion. So it does make, reporting and extraction. I don't wanna say it gets around some of the constraints you might be experiencing today, but you can design for the purposes that you're interested in. So here's an example of what defining those looks like, but you can see that, hey, we can derive information from existing fields as well and apply any sort of data transformations upfront that you might need before extracting that data. Great question. And I hope that answered the question too. If not, feel free to type back into the Q and A there. All right. So I think we are getting to the end of our session. We have one more question and I'll I'll, I can address this real quick. How do you ensure data security and governance? I think that's a real great advantage around, extend is that all of the SOC two controls, the ISO controls that are part of your Workday core service come along for the ride with extend. All the auditability is there. So if you're already trusting sensitive data with with Workday, through the core application, doing so with an extend is really, no different. Alright Alright, and last question here, Pascal, you want to take it is where do you typically see the most value from extend? That that's a really good question, and this this is usually one of the key aspects why customers go for extend. It's The aim of having an extend application built within Workday is to reduce friction. You have a single platform where you can process all the work you need to do, all the processes you have externally. Most of our customers are coming in from trying to have a they have currently a fragmented process like approvals, tracking them, workflows that sit outside of Workday. What they're looking for is a streamlined frictionless process where everything is handled within Workday. It follows the security pattern of Workday, and the users, most importantly, are used to the interface. By the time we design the app and get it up working, the users are already familiar with the interface. They understand what needs to be done. It's secure, as we've said, by design, and it delivers on the outcomes they need by removing friction across business processes. This is the key element of why we're building these extend apps and helping businesses to accelerate their, what whatever they're doing, whether there's internal processes or processes or workflows. Thank you, Pascal. So just to kinda give key takeaways, please take a look at those resources we service on the document page. Highly encourage you to join DevCon digitally. There's gonna be some really exciting, cool announcements around the developer experience when it comes to extend. So if you can join in, that would be great. Certainly connect with KNOs. They are one of our best extend partners. They do a lot of really awesome work. They have their own, they they have quite a healthy, list of of of, applications in our in our own marketplace, but they're also just innovative as as it comes. So if you have ideas, you don't know exactly how to execute on it, definitely recommend work connecting with KNFs or any of our Workday certified partners. Think about use cases, you know, build apps that live in close proximity to your people and your money, that makes sense for for extend applications. You're gonna have a really good experience designing, when those elements are involved. Training and, and resources, again, if you've got folks that are already familiar with reporting, with the integration layer of Workday or just web design application development in general, or you got that new, or you got people that are really into vibe coding and taking advantage of AI, this can be a great, great platform for them because you can take advantage of all of those new resources, but still have lawful, guarded, you know, kind of on rails development, when it comes to developing against Workday. And lastly, staying connected with the developer community. This doesn't stop at DevCon. You know, attend, make connections there, but also really, get involved with that developer forum, the early adopter programs and workday community, as well as just, you know, there's a lot of YouTubers out there that are doing really, really cool things with extend. I don't think you see that in a lot of the ERP development platforms, the culture around it. So I certainly encourage that as well. So with that, thank you so much for joining today. The last slide here, again, there's the QR code to register for DevCon. We're sold out. That's how, exciting this really is for our community base. But if you wanna join that virtually, as I will be doing myself, we're gonna be surfacing a lot of really cool content on there as well. So with that, have a wonderful rest of your work day. And, Christine, anything else you want to go before we set out? Alright. Awesome. I think we're all good. Take care. Thanks, Thank you. everyone.