Transcript for "Building on Workday's Open Platform with Cushman & Wakefield": Hello, everyone, and welcome to today's looking forward webinar, building on Workday's open platform with Cushman & Wakefield. So today's event is part of our looking forward with Workday webinar series, and it's really designed to give you insight into how you can do more with the Workday platform. My name is Suzy McKee, and I'm on the Workday build product marketing team, and I will be your host for today's session. So just want to, briefly acknowledge that we may be discussing future road map items future road map items, so, please keep that in mind as we are going through the session. And then a few housekeeping items. First, we are recording this session, and you will be, receiving it in your email about twenty four to forty eight hours after the session ends today. So be on the lookout for that. Workday uses the Goldcast platform for our series, and that allows you to submit questions, get access to resources, and provide feedback. So please note the q and a button and submit all of your questions there. GoldCast actually does better when you are using Chrome. So if you are having any technical issues during the event, go ahead and put a note in q and a, and you we will give you some assistance there. Alright. So here's our agenda today. Workday's open platform strategy and how Workday build empowers customers to build right on Workday. We're gonna start out right with that and then quickly get into Cushman and Wakefield who is here to share their experience with Workday build, taking us through a use case and what is next for their team. And we also have a great demo ready for you. We will get deep into the developer toolset. And then as a reminder, as you're hearing things, learning things, you want more information, again, please just put your questions in the q and a. We will be answering them as we go, and then we have time for a live q and a at the end. So these are our guests today. We are very grateful to have Jennifer Serrato, chief technology officer of the Workday platform. And Duda is the global director of finance systems technology and data solutions at Cushman & Wakefield. And Don Stacy is a senior principal enterprise architect here at Workday. Jennifer, I'll turn it over to you to kick us off. Thank you so much, Suzy. Hi, everyone. It's great to be with you all today to talk about the Workday platform. My name is Jennifer Serrato, and I am the CTO of platform at Workday. And before we get into all the fun platform details, I wanted to start with our Workday journey. So this past year, Workday celebrated our twentieth anniversary, which was a big deal for us. And I joined back in 2014, so you can see me there on that timeline. So I've had a front row seat into how we've evolved from an applications company into truly both an applications company and a platform company that we are today. So today, Workday serves over 11,000 customers, and they trust us with their most sensitive data, which is their people and their money. And we service over 65% of the Fortune 500. Today, I'm actually excited to share that we hit a major massive milestone where we transacted over 2,000,000,000,000 transactions on our platform this past fiscal year. Now I started my career over twenty years ago, and it's really fascinating to me to see how far technology has come. So a fun fact twenty years ago, did you know that the very first YouTube video was uploaded? It was right around when Workday was born, and only 30% of US households had high speed broadband Internet. Truly fascinating to see where we've come in the past twenty years. And the reason I mentioned this is because just like the cloud or the SaaS era has redefined the way that we've lived these past two decades, we're entering another massive technological revolution right now. This AI era will define the way that we work and the way that we live for decades to come, and it's really changing what our customers need from us right now at Workday. So in my role as CTO of platform here at Workday, I talk to many CIOs. And for the many CIOs that I talk to, the the change in the AI era and the AI revolution is translating into a very specific set of new pressures that I'm hearing from them. They've got a mandate, and their mandate is shifting. Their role is shifting and evolving from managing a lot of rigid technology and disparate systems and architecture stacks to needing to simplify those stacks, to quickly respond to these business needs. They're looking for ways to safely adopt AI. They're looking to see where they can get proven value out of AI, and they really are looking to bring their data together with context because context is usually important when it comes to AI to gather better insights and intelligence. So in response to a lot of these challenges that these CIOs are facing, Workday has an an AI strategy, and we're uniquely positioned to be the enterprise AI platform for managing people, money, and agents. So our strategy is to build the best agents for people and for money, and and our strategy is to build these agents that are truly outcome based. There's a lot of AI tools out there and a lot of a lot of buzz out there, and a lot of these tools are focusing purely on measuring productivity. And that's great for all of us. Right? We're taking, we're getting a lot more productive at work. We're we're, you know, using ChatGPT probably on a daily basis at home. But at Workday, in the enterprise, we're taking a very thoughtful approach, on how we're building, our agents and our agentic AI strategy. And what we're doing is we're focusing on true business outcomes. We're not just focusing on, productivity. And because of the data and context that we already hold, we're uniquely positioned to do this. We're not doing this alone, though. We're we're building the best agents for people and money, but we're also opening up the platform to allow our customers and our partners to build alongside alongside us. Us. So it's something that we called Workday Build, which we announced, at our annual customer conference this past year, at Workday Rising. So you might ask, what exactly is Workday Build? Like I said, we announced it at our customer conference, which was held in San Francisco and in Barcelona this past, in in the fall. And you can think of Workday build as three pillars. So the first pillar is a unified developer toolset. So whether you're building applications, custom applications, integrations, or the next generation of AI agents, these tools are allowing you, to build on top of the Workday platform. And you can leverage your enterprise's most critical asset, your data and your context. And because you're building on Workday, your applications automatically inherit our security model, which allows you to scale AI solutions that actually understand your business. The second pillar is our partner ecosystem, and we know that you don't have to build everything yourself. You might wanna partner with one of our trusted partners to see what they've built and what they've serviced, on the marketplace. So there are over 500 partners now who have used these same tools that are on the left hand side to create a marketplace of vetted purpose built solutions that are out there for you to take a look at. Now if you have a niche regional requirement, you can often solve it instantly with one of these partner solutions rather than coding it all from scratch and having to maintain that yourself. And finally, last but not least, a thriving developer community. So tools are nothing without our amazing developer community. And I'm super proud, to see how this developer community has grown over the last several years. We're investing heavily, to ensure all of our developers and the teams can upscale. They can earn credentials. They can connect with their peers globally because they're leveraging all the same tooling. They're leveraging all the same platform, and they're building, unique solutions, and they're able to innovate together, which is really awesome to see. In fact, our developer community has grown two times year over year for the last two years, and we're now at 17,000 developers in this external developer community, and it it's rapidly growing. Now it's great to see all the tools in the partner community, the marketplace, and the developer ecosystem, but the super exciting part for me is actually seeing how our customers are innovating and building with us on the platform, and they're really solving unique business challenges. Now these are just a few of my favorite examples. There's many, many more examples out there. In fact, there's over 3,000 applications in production today that have been built on our platform. The first fun one is the PGA Tour. They built an application that connects their third party tournament software directly with Workday Financials. And through this, they're able to seamlessly manage $12,000,000 in prize money. It's a perfect example of bridging that really niche operational third party tool with our core financial Workday system. Target has over 400,000 workers, and they've built over 18 applications on our platform. They're in production today that specifically support their team members' health, the compensation processes, and their work life balance. And finally, St. Luke's. St. Luke's University Health Network launched a MyOptIn business bonuses app app, where 74% of their nurses used it to enroll in bonus plans. And this resulted in a 50% improvement in nurse retention. And with nurses being in really short supply and in high demand, this was a big, big win for them. These are just a few examples of how our customers are innovating on the platform to build the future of work. But I don't want you to hear it all just from me of how great this platform is. There's one leader who is truly pushing boundaries of what's possible, and that is Edward Duda. He's the global director of finance systems technology and data solutions at Cushman & Wakefield. He's gonna walk us through an application his team built, the outcomes they're driving, and how they're planning for the future. Ed, over to you. Thank you, Jennifer. Hello, everyone, and thank you for joining us today. As Jennifer mentioned, my name is Edward Duda, and I'm the global director of finance systems here at Cushman & Wakefield. To start, a quick overview of who we are. We're a global commercial real estate and services firm with approximately $9,400,000,000 in annual revenue, operating in 60 countries, 400 offices with more than 52,000 professionals worldwide. Operating at this scale brings significant complexity, not just operationally, but financially and from a controls perspective. As a result, we are constantly looking for ways to modernize our processes while maintaining strong governance. That mindset is what set the foundation for our Workday journey and, more recently, our use of Workday Extend. As our business continues to grow, it became clear that manual and semimanual processes were no longer sustainable. Transaction volumes increased, regulatory expectations increased, and the risk associated with human intervention increased as well. Incremental improvements just weren't enough anymore. We needed a way to fundamentally rethink how the work was getting done. Workday Extend gave us the opportunity to move beyond the status quo and build solutions in which are scalable, controlled, and embedded directly within Workday. So our Workday journey. We're well along in our Workday journey and focusing on extracting as much value from the platform as possible. We live as a full platform customer by 2016 as customer 736. As you can see from the illustration, we've adopted most of the Workday products since our initial go live in 2015. It started in 2015 with human capital management, quickly grew legs and managed to move into financials and PSA. In 2021, we started US and Canada payroll, also dabbling in adaptive planning. In 2022, we purchased Xtend and Prism. And then most recently, we signed up for Workday Success Plans in the AMPCON. So one of our guiding principles has been to stay within the Workday ecosystem rather than building external tools that introduce reconciliation challenges and data risk. As you can see, we've subscribed to the full plethora of Workday products. Xtend allows us to create purpose built applications that leverage Workday data while remaining fully governed and aligned around our foundational data model, something that we keep close to the core. So you might be thinking, why Extend? Extend has given us the ability to present Workday data to end users in a way that feels customized and intuitive without sacrificing controls, auditability, or data integrity. It fills the gap between the standard Workday configuration and the realities of a complex global business of ours. We're in several regions, several we've got several service lines, so not everyone is doing the exact same thing. We need a way to get everyone moving in the same direction. Most importantly, extend allows us to solve real business problems while keeping everything inside of Workday. And we see this as a long term capability, not just a one off or one time solution. So we get into our our first major extend solution, which was we needed to improve the accuracy of our labor billing. Cushman & Wakefield bills clients for a wide range of building services, resulting in more than 7,000,000 labor related transactions each year, representing over $1,500,000,000 in revenue. At that scale, even small inefficiencies or errors can quickly compound into material risk, making labor billing an ideal candidate for automation through Workday Extend. So what were our goals? Our goals of this prob project were extremely straightforward, but they were significantly impactful. We wanted to eliminate the manual offer in spreadsheet driven adjustments, reduce billing errors and invoice corrections, and improve auditability. We were spending a disproportionate amount of time on these corrections, up to forty five minutes per instance. Forty five minutes. Just just think of that for a minute. At the same time, it was critical that we maintain financial statement accuracy while improving efficiency for the teams doing the work. So what was our solution? Using Workday Workday Extend, we built an application that pulls labor expense directly into Workday Extend, where we could massage the data as necessary. This app allows users to edit, transfer, allocate labor expenses using percentage based or hour based logic tied directly to our FDM or foundational data model. No EIBs. No manual editing the entry. There was an app that was built that could do it all. We also integrated our ticket numbers from our external systems, ServiceNow. This provided a clear audit reference and audit trail for every single adjustment that was being done. This was both peace of mind for the end user and the person working on that particular task, but also it cleared a big hurdle from a SOX compliance perspective. Once the changes are approved, the solution automatically generates the appropriate transactions to replace expenses to the correct, not only ledger accounts, but work tags as well. It's a one stop shop. All of this happens within Workday, maintaining full auditability and eliminating the need for offline tracking or cumbersome data reconciliations. So what were the results? We had significant results from this. We were able to reduce the team supporting this process from 12 FTEs down to five in the first year alone, saving approximately $1,000,000. We've seen significant efficiencies in years two and three as well. We were able to cross train our team to work on more analytical type of work rather than these simple, time consuming corrections. Error resolution times dropped from over forty five minutes per correction to roughly four minutes per issue. And error related tickets were reduced by 75%. This is year one stats. We were in the realm of about two to three minutes per issue that we received. Most importantly, billing accuracy improved, reducing both operational friction and financial reporting risk. So what's next on our agenda with Workday Extend? So the next thing that we are going to be introducing at Cushman & Wakefield is our SOX and Security app. After seeing the success within the finance space, we thought that this was a perfect opportunity and use case to make sure that our SOX teams and our security was in alignment. These processes were historically manual, fragmented, and supported by legacy tools that were difficult to scale. Xtend gives us a way to centralize and modernize these controls within Workday. So what are the goals? The goals of this initiative are to automate the role inheritance during the hire and change job process, automate privilege and finance and HR access controls, and proactively identify when security changes are required. We also aim to replace our outdated antiquated access request system to establish a clear, consistent structure for Workday, security groups, SOC scoping, and enterprise security. So what is our solution? We're building a single extend solution that administers SOCs and security not only for Workday, but for multiple enterprise applications. We have seven, seven unique enterprise applications which are in scope for this project. So we're just not taking the Workday data and massaging that and coming up with a solution for Workday data. We're coming up with a a solution across our enterprise applications. Security decisions are driven in real time by job data, allowing us to respond almost immediately to changes rather than relying on periodic reviews how we do it today. In today's world, we have a feed of data usually once, sometimes twice, at various times for those seven different systems, and we have a legacy SharePoint site to manage all of that security. We see discrepancies in latency almost every time one of the chain one one of the changes is made to any particular system. This approach will help to reduce manual effort, improve consistency, and enhance the user and manure manager experience and create a scalable model we could reuse across our enterprise applications portfolio. So what do we plan to get out of this? From a value realization perspective, we're hoping to see significantly reduced time and effort required to support our SOX audits. Not with our SOX audits usually being off the side of our desk and an additional task that we have to do, systemizing them and putting them into Workday so that everyone has full visibility to them. Access changes are faster and more accurate. Security infrastructure is modernized, and the risk of deficiencies in audit findings is significantly reduced. Most importantly, Extend will provide the strong foundation for extending our governance and controls across our broader enterprise landscape. So now I'm gonna walk you through a very quick and very easy data flow of what we plan for the SOX and security app, specifically related to the change the higher change job in SOX processes. As you can see, we're pulling data from multiple non Workday applications and ingesting that data directly into Prism for use. We also have all of our financial and HCM data available within the Excede application. First, these changes will go to the manager for review or approval or denial. Next, if it is going to be a role being removed, it's going to be reviewed by the finance or HCM reviewer to ensure that this is correct, to make sure that there's no additional intersections that will break as a result of removing this, and to make sure that this is alignment across our security policy. Or if the manager approves, it's going to go to our finance or HCM administrator to close out the process. I know that this data flow seems super simple, but in actuality, it's very complex based on the routings, the different applications that we have in scope, as well as the different functions that we want to be included. It's been a journey to get to this point, and we need to think through the impacts, assess the change management, and think of the right solution for our firm. The nice thing about Extend is it's not cookie cutter. You can make it fit for purpose for your organization. To wrap up, Workday Extend has allowed us to solve complex, high risk business problems while staying fully within the Workday ecosystem. It has delivered real financial savings, improved accuracy, and created scalable solutions we continue to build upon. Thank you for your time today, and we look forward to continuing the conversation around how Extend can drive value across the enterprise. Now I'm gonna be turning it over to Don Stacy, senior principal enterprise architect from Workday, to give us a demo of the unified developer platform. Over you to that over to you, Don. so much, Ed. It's always a pleasure to hear what our customers are doing with Workday build, extend, and other components of build. Give me just a moment here. I'll go ahead and get started on the sharing side. Gonna show you some demos here today as we move through the process. There we go. That should be coming up. Alright. So by way of introduction, my name is Don Stacy. I'm enterprise architect. That means I help educate our customers and prospects on all things technology related at Workday. Certainly, Workday build AI is within that umbrella. So we're gonna talk through. We're gonna see a number of different demos covering components of build today. We've been looking at the questions. You know, build is not a SKU. Build is a collection of components that really support Workday efforts to be open, in terms of a platform, making it easier for you to build on top of that platform, get data in, get data out, build agents, etcetera. We're gonna talk through a lot of that today. We're gonna talk about custom agents. We're gonna start our session today looking at a custom app, components of a custom application and orchestration. Where to culminate with data cloud. All of these capabilities, are sitting on top of one developer experience. So you'll go to a singular place to deliver these capabilities within your organization. You don't need to swivel cherry. You don't need to change applications. And all of that is driven by a set of open growing open standards. So we've had things like SOAP and REST and Graph for a long time, but we're adding in MCP and a to a to support our argentic efforts. We are adding in Apache Iceberg to support data cloud. And as new standards evolve, we will keep rolling those out as well. And then, of course, everything we're doing is sitting on that trusted Workday platform, the very best place for your people and pennies. What I thought we would do is start today going through a little bit of a app build experience. So we're going to discover an API. We're gonna build some user experience on top of that using developer Copilot, add some AI widgets, which were the absolute star of DevCon. We'll look at how Copilot can help us build Orchestrate in the near future and then how we can surface our application through a card on the homepage of our solution. So with that, I'm gonna go ahead and jump in to the application itself into the developer experience. So I am in that developer site and imagine I'm going to build an application that is related to the delivery of feedback and giving a gift card. But I don't know where to start. I don't understand the APIs. It's an area I just haven't been in yet. I can now use developer Copilot for APIs that will help me figure out the right APIs or the potential APIs to use in my scenario. Alright. So we popped in there. Just give me some suggestions of what I might ask for, you know, give me a certain kind of API. I already have one in here. It said I need an API to give feedback. I'll go ahead and send that request. So the large language model is thinking about that request, figuring out across all of the APIs that are out there, what are the ones that might meet this particular need. It's gonna surface the top three for me, allow me to drill in and see more of them. It's also gonna explain why it surfaced those particular three. So it looks like in this case, I got one SOAP and a couple of rest and some explanation as to why. I can dig into any one of these. I could certainly pop out and test it right within the developer experience. I can also see information about that call. Maybe I wanna compare it to another API and just understand what the differences are. So I'll just pick one down here. It doesn't really matter which one. We'll do this one for now. So that too is a SOAP API. I can see the response. I can see the request. I can start to understand those and test those. I can also tell Copilot here what I'm trying to build. Is it an integration app, an extend app, or maybe a card? Because it might recommend different APIs in that scenario. What we're gonna see in this case is we are going to get a set of graph APIs because that is the preferred API type that we're gonna use for our extend applications. So this is GA now for extend pro customers, the ability to use Copilot for APIs, but it doesn't end there. Let's jump into an application and understand what we can do with Copilot through that lens. So I'm going right into the build experience. This is that one place where I'm going to do all of my building around orchestrations, agents, and applications. We've already started this application, but we're gonna add some capabilities to it. We're going to add a brand new page. I can certainly create that page from scratch or I can just prompt the system. Now you're gonna see me go through a couple of times today and paste some things in because watching me type is not fun for anybody. I'm giving this a really robust prompt asking it to create a new page where we are going to hard code some values. I want a number of, rich text fields to show up. I want a list of values for the gift card amount, $25.50 or a €100. And just like that, I now have a page that I can leverage. And I'm gonna see that my tech my connection died to my tenant while while I was waiting there, so give me just a moment. Just need to connect to my tenant so that it has the right context to go ahead and execute the the commands that I'm asking you to. Alright. So now we are connected to my developer tenant, my extend developer tenant. It's gonna go ahead and render that page for me. So what is the recognition category? Those are those hard coded values. I have a couple of fields here, and we're gonna start to mess around with that. Before we do that, I'm gonna go ahead and add that to my application. Oops. Do the add to app. It's gonna put those components right into my application, and I can start to work with that page. So let's call this employee recognition underscore one. I'm now in this declarative environment with an extend where I can move things around, configure fields to maybe this gift card email message. I don't want that to be a required field, so I can simply uncheck and just that easily, I have fixed that up. What I wanna do in the next step is I want to make those text fields a little more interesting. I wanna use a large language model to go ahead and refine text, generate text for me. That's called an AI prompt or an AI widget. It was the star of the show at DevCon, very exciting capability. So we are going to just go ahead and add a button here to our rich text field. We're gonna call it revise, Gonna paste in some stuff I already worked out for that particular AI prompt, and I'll show you what's inside of this. So this is just saying, take some static text together with a feedback dot value. So that is the name of my field here, feedback. You know, make sure the tone is professional and sincere, make it more specific. So that's the guidance I'm giving. Then when we come down to this email, I'm gonna give it slightly different guidance because that's gonna be just a short piece of text. So we'll say create message. And same kind of thing, we're going to drop some prompt text in there. And I'll show you what that one looks like as well. So this is taking that feedback value together with the name value. That's another field on my page, and I can have hidden fields that are driving behavior here. And I want this one to be professional yet fun and stay under 300 characters. With that, I'm ready to go ahead and test my application page here, see how things are working. So we'll let that come up inside of feedback that you see those buttons popping up. I'm gonna say, you know, thank you for all your support with the build webinar. And then we'll say revise. So at that point, we are calling the large language model that we already are delivering for Workday. So you don't have to do anything other than the prompt setup you saw me do. This particular call came back with four or five different options of the text I might use instead of the very simple sentence I wrote. I would then this is where human in the loop comes in. This is where I would go in and figure out, which of these suggestions do I wanna use as a starting point. Go ahead and delete the rest. It's even explained to me why it picked those particular suggestions. And then the last thing I'll do here, last two things, select a gift card amount, maybe €50 in this case, and then generate that shorter text that I wanna put into the email itself. And so you'll see there's a little icon there, celebratory icon, you know, congratulations, way to go, Logan, that kind of thing. So very quickly, we've made a call to a large language model without any setup on your side other than defining these prompts on a rich text field. This capability will be coming in twenty six r one, and, this is an extend professional capability. While I'm inside of the developer experience, I also wanna highlight one more thing for you today, and that is cards. So we have the ability this is a generally available capability. We can take build cards and then expose those into the application. So this card is very simple, has a badge and some text and then a link into the application itself. This is all about taking those great extend apps and surfacing surfacing them through the Workday experience. But where am I allowed to surface it? Well, I didn't actually know the answer to this as I prepared. So I reached out to Copilot. This is a different element of Copilot. We have indexed all of the documentation of extend, and I simply asked it, where can I place cards in the UI? The answer was the homepage, delivered hubs, Workday search, and Workday journeys. So it was very easy, and then I just researched how to add this to the homepage. So what does this look like at runtime? If we go back to the to the homepage of our application, you're gonna see down the right side here three different cards that we've set up, create a work events, some AI prompts, and there is my employee recognition. So that is that custom card deployed to the homepage through standard Workday configuration, UpdateSafe configuration. When I click into it, it just takes me into that application. Different page than what we looked at together today, but very easy for me to get from the homepage or from a journey into my custom extend application. Alright. Let's pop back into slides here and move forward here. So we saw the first couple of components there. Wanna talk about developer Copilot just a little bit more. So we saw extend the ability to create a page. What I didn't talk about yet was you can create code snippets. You know, how do I get the difference between two dates? Can you generate a validation function for me? We do all of that with Copilot. That is available now for our pro customers. You saw the API example. Coming in '26 r one is using Copilot for Orchestrate. Very excited about this one. Orchestrations are incredibly powerful. They really are the future of integration at Workday. But even with robust modern drag and drop, there's still a lot of things that drag and drop. So what we're gonna do is we're gonna make this even easier with Copilot. This is me starting at a, just the starting point of an orchestration. It has a start and end step, nothing else. We're gonna feed it some text and ask it to do something. I know that's really tiny. Bear with me. I am gonna go ahead and pause and make that bigger for you here in just a second. Alright. So let's take a look at this guy together. I need an orchestration that receives recognition award details, looking up worker info, sending feedback into Workday, issuing a gift card through the Tango through Tango, a third party system, and create a onetime payment at Workday. So that's four different API calls. I need to return some information. And by the way, here's the open API spec for Tango and a sample request body. So we have given it all of this rich prompt information, and then we're asking it, go generate an orchestration for me. Give me that starting point. It's gonna give me 80 plus of the way home. And just that easily, it's explained all the steps that it's added. You'll see it's building the request itself then executing the API again and again and again. That's awesome. If I'm happy with that, I can save it off. Go ahead and add some logging steps. So instead of me dragging several of those out and configuring them, it did it for me. At that point, I can validate, configure, tune, test, etcetera, and then I'm left with the job none of us really wants to do, and that is documentation. I really don't need to. I just ask Copilot to summarize this orchestration for me, and check this out. The purpose, the inputs, the workflow steps, what are the outputs, the security, the integrations. It's all there for me. I didn't have to write any of that. I just need to review it, validate it, and ultimately, I now have my orchestration delivered. So that is Orchestrate through the lens of Copilot coming '26 r one. Alright. So let's pivot away from extend now. There were, you know, extend is a big piece of build, but it's not all of build. There's a lot more involved as well. So let's go ahead and take a look at the agentic footprint here. So let me go ahead and highlight a couple of things for you. Jennifer touched on this earlier. We are busy building the best AI agents for HR and finance. No one lives in these domains more than Workday HR and finance. And so we are working hard on delivering those agents. We have several in production now, or in in general availability now, and we will have more coming soon, February and then beyond. So we're building all those agents, and that really reflects these the Workday built agents. We're gonna keep doing those. The pace is accelerating, but our partners are also building agents, whether it's for a specific industry, a certain niche where they have expertise, or maybe just customer specific demand. But additionally, you, the customer, will be able to build your own agents inside of Workday to specific agent builder types. Sana is really for personal agents, something I might do myself. One of my peers shared yesterday one that he built that goes out and evaluates HCA contribution amounts and the effects to payroll. And it's all done conversationally. He created that with three steps in a conversational tone. Sana agent builder pro is the second component, and that is where more of an IT led build, and that's where we're gonna build, agents that you might deploy across the enterprise. I'm gonna show you what one of those looks like here in just a moment. Before I go there, I wanna spend just a moment talking about this tech stack, the agent tech stack. We're not gonna go deep into these today. But starting right to left, connectors. We've had connectors at Workday for a long time. But not so long ago, we bought a company called Pipedream, north of 2,000 connections to virtually anything you can imagine out there. We are working out to roll those connections into various parts of Workday, Orchestrate being an example, Asana being an example. We're delivering our MCP and a to a, capabilities in 2026. We will be delivering the agent system of record in February. We're just a couple of short weeks away from that, and that will allow you to register all of your agents inside of Workday, whether those are agents that work on Workday or they're they're outside. We'll allow you to see your total workforce because your workforce is no longer just the people. It's also the agents that together are driving business. All of that delivered in the agent system of record for registration and management and governance. And then lastly is data cloud, and I'm gonna put a pin in that one because we are going to discuss data cloud here in a little bit, as we move forward. So let me jump out of that kind of screen mode there and take you over to have a look at Sona Agent Builder Pro. And so I'm in this environment. This is definitely something for something with a someone with a technical skill set. And if I wanted to create a new agent flow, I would simply click add new, and I can start dragging components out. Check out this list. I can have an agent, conditional steps, direct replies, LLM calls, loops, feedbacks, etcetera. But honestly, the way most of us are creating these is we just go in here and we use a prompt to tell the system what kind of agent we want. We give it tools and then we give it a prompt and it will go produce that for us. Probably won't go there today in the interest of time. I'll just show you one that I created previously. This is really just a little tiny agent that's designed to do time off requests. And the first thing it does is it calls a tool in Workday to get time off balance. I told it to call this Gemini, LLM to orchestrate the conversational component. And then ultimately, when the person says, you know, what they want, what time off they want, we will say, is this what you intended through that large language model? When they say yes, we'll call Workday again with another tool to submit that, and we will give them a success or a cancellation response. So real easy to set these things up. It is a technical job because you're building enterprise class agents in this case, but quite easy to set those up. Go back to slide. I wanna show you what that can look like through the lens of extend. So these agents don't have to have anything to do with extend, but they can. So you get a URL when you create agent, you can drop it into your portal wherever you need to access from. In this case, we've said, hey. I've got this great extend app to manage charities. This is one of the apps you can download as an extend customer. I would like to have a conversational component that sits in front of this. So right there within that same developer experience where I just was, I can go in and create new agents, or I can edit ones that are already there. And we're gonna show you one that's already been created for that charitable donation. It only has one step. It just adds an agentic step in it, and here's the test harness. So this is me talking to my extend app. Hey. What can you do? These are the three skills, the three capabilities of that application. What do you wanna do? Give me a list of charities. Great. Reaches into the extend app, grabs that data, surfaces those three charities, and then says, you know, do you wanna make a donation? So a little presumptive close here. Yes. I do. Well, which charity and how much would you like to donate to? Now I can do all of these same tasks through the pages of my extend application. But as we move into this conversational world, this is how people wanna interact, and I'll be able to have this conversational experience sitting on top of my custom application that is used for charitable donations. Then lastly, it's gonna push that information back into Workday, which will show up in this case on my charitable donations page within my extend app. But it might also be reaching out to payroll, setting up a onetime payment so that payroll can recognize that. It's really powerful use of agents sitting on top of extend applications. Alright. As we round out today, I wanna talk to you about data cloud. So data cloud is something that's being built now targeting, r two of this year for availability of that. And this is really recognizing the fact that Workday is a piece of a much larger ecosystem. It's important for us to leverage data that you have in your own data strategy as well as make it easier for you to get data out of Workday. People don't wanna do any more ETL than they have to do. They do not want to make copies of data because every time we make copies of data, we have challenges with things like the right to be forgotten, security constraints, etcetera. So how do we help that? We do this with Workday Data Cloud built on open standards. It starts with key partners. So I'm gonna move to kinda think about the left side of my diagram here first. Those partners are Databricks, Salesforce, Snowflake, and Google. And we have the ability reference data from those platforms with zero copy using Apache Iceberg. We do not have to pull that data in. We can instead just point to it and report upon it, having a conversation with that data. And that's awesome. And that's coming in through our infrastructure, tying together core Workday data with that external data. So people are very excited about that. But the thing they're probably most excited about right now is getting at Workday data from the outside without moving the data. Don't wanna take it out of the safe and secure confines of Workday where all of our security is set up. Data cloud supports that as well. So sitting in those same four trusted platforms, and that platform list may grow over time. This is where we are in our initial rollout. I can ask for data from Workday, ask to see data from Workday. I can use JDBC if I want real time data access to the object model. So instead of RAS calls, I can do this, or I can call into the Workday data lake. And the Workday data lake will be materialized tables that reflect the key business objects of Workday. They won't be real time. There'll be a little bit of latency there, but you'll be able to make these high volume, high performing calls across that data when you don't need real time data access. What I'll do is I round out my last minute, minute and a half here is just show you a quick demonstration of what that will look like. We will look at this one through the lens of prism. And so I'm saying, hey, want some data from Databricks, creating a new pipeline here. It's a live connection. These are the three tables that I want. It's gonna create that pipeline for me. So I'm pulling three things from Databricks, pulling in some workers from Workday, doing a join on those, ultimately producing a data source that leads to, in my case, a discovery board. That discovery board has some data that all lives outside of Workday, attainment rates, service tickets. But then when I want to start to marry that data together with Workday data, thinking about satisfaction by tenure or seniority, or I wanna see details of my team, I can do all of that within here. So you see on this report commission data. What else is here? Satisfaction scores. None of that data has been moved. It's still sitting in Databricks in this case. And then I can start to have a conversation with that data. So I might ask the system, you know, which employees have the lowest commission and when did they join? Or I might ask it, what skills do my best people have that others don't? It comes back and says, hey, they're missing the product knowledge skill. Would you like to assign a learning course? Because I've never left Workday, I can simply say yes, attach learning to that, even drill all the way down to Pedro's profile and see those details. So that is a very, very quick glimpse of Workday Data Cloud. This will be a big topic at DevCon coming up, Definitely something to keep your eyes open for. And then here's just a screenshot of Salesforce talking to Workday data without actually moving that data. I'm a little behind, so I'm not gonna dwell on that one, but it's pretty straightforward just using the tools of that platform to access that Workday data in a zero copy mode. So we saw a lot. We saw a custom app builds. We saw orchestrations, developer Copilot doing more than ever for us, data cloud making life easier, getting data in and out reference points, and billing custom agents, again, all sitting on that Workday platform that you know and trust. So with that, Suzy, I will turn back to you so we can kick off the Q and A. Right. Sorry for the lag there. Thank you so much, Don. That was absolutely amazing. You covered an incredible amount of ground in a short period of time. We have had a number of questions coming in. Hopefully, Hopefully, all are able to see, some of your answers one on one, but we wanted to pull some out to do live. So, the first one, Don, is, and we hear this one frequently. When do I build an app versus an agent? Yeah. Yeah. It apps are gonna be gonna sorry. I'm getting some echo. Apps are gonna be when you have more of a, you know, be be a declarative problem that you're trying to solve, something that's very rigid and strict, or maybe you need to collect a lot of data through user experience that conversational might get overwhelmed. That's typically where we're gonna going to see app build happening, page collections of data, etcetera. Whereas agencies, I want that conversational experience. I want a nondeclarative mode. I'm gonna give it a goal and have it find a way to the answer. It'll figure out what API calls it needs to make, what tools it needs to make. And the two can work together absolutely as you saw in that one video. Thank you. Okay, Ed. I've got a couple questions for you. The first one, can you explain how the Journal Line Reclass app improves control, efficiency, and auditability compared to traditional journal correction processes, especially in a SOX controlled environment. Wow. That's a that's a great question. So thinking back around the Journalline Reclass Extend app, it significantly improves control efficiency and auditability by enabling precise line level corrections without the need to reverse and repost the entire journal entry. From a control perspective, it enforces the standardized workflows, approval, segregation of duties, which is critical in our SOX environment day to day. From an operational perspective, it reduces manual effort and the risk of error by eliminating off system workarounds, such as spreadsheets. Every re reclassification is essentially fully traceable with a clear audit trail showing who made the change, why it was made, and who even approved the change. That transparency not only supports audit requirements, but it also increases confidence and integrity of the financial data, allowing the teams to move faster and with more discipline. Alright. One more for you, Edward. As processes and org structures evolve, how will the SOX and security optimization app help you proactively manage risk, strengthen security controls, and support ongoing compliance? Yeah. With that one, it centralizes the SOX related activities and security optimization into a single governed framework rather than relying on all of these reactive reviews that we have and the the manual tracking. I talked a lot about all the folks at Cushman & Wakefield and the the business users, the IT folks. They've got the napkin on the side of their desk with SOX activities that they have to do in addition to what they have to do as part of their daily responsibilities. So that's really the key to it. And from as the business processes, roles, and organizational structures evolve, the app helps to ensure that the controls remain aligned by continuously monitoring changes and highlighting potential impacts to not only SOX, but also more broadly to security. This can allow the teams to address issues early and often, and and, ultimately, it shifts the organization from a reactive point in time compliance model to a more sustainable, continuous control environment. Thank you. Alright. I'll take the next question. So how do I purchase Workday Build? And there's really a bit of nuance to it. So you don't actually purchase Workday Build as a second item. It's a full developer platform that has everything you need. So as Don kinda took you through how to build agents, apps, and integrations, there are definitely the products like agent builder and Workday Data Cloud, which you would purchase. And then the partner ecosystem and marketplace has ready made solutions, and then there is the developer talent community. So it it it really is nuanced as to which parts of build serve your needs. And, of course, it it truly is an entire ecosystem. So you would probably participate across all three of those pillars, but you aren't purchasing the developer platform itself. And the next question real quick, how do I get access to AgentBuilder Pro? That capability will be made available to all Workday customers who have purchased Workday Extend Professional. And then I see a couple questions too about agents and flex credits, and agents will consume flex credits. So I know that's an entirely other topic probably, but, I'll just answer that one pretty quickly. And, let's move on to Don, we have another question for you. So how does authentication work? Very easily. The great thing about authentication through everything we've talked about is you're using what you already have configured inside of Workday. The security groups that are defined, you've already controlled through the application what privileges individuals have. So as we build agents, we will automatically honor that security. As we build extend applications, we will honor that security. For example, if I had a drop down in my extend app that said my team, all I have to do is literally at development time check a box that says to control that security by context, and I will only see my team. I don't have to go through a bunch of work. If you build anywhere else, you're gonna have to think about all that security. You're gonna be replicating security and trying to keep it in sync. It all becomes very easy within Workday build components. Alright. Okay. And if I build an agent outside of Workday, can I integrate it into Workday? Depends on what integration means. You definitely can make calls into Workday for various things when you might hit our self-service agent, and surface capabilities there. There's a bunch of different ways. There's not a place inside of Workday to, you know, house it like you might think of it a legendary iframe or something like that. But definitely what we're seeing the primary pattern is people are building custom agents that are talking to Workday through the open APIs and then eventually into some of things like MCP and A Day that we're working on. Okay. Next question for you, Don. How current is the data within the apps or agents? If I make a change I think you may have addressed this. If I make a change in the core system, how long do I have to wait for the agent to see it? Yeah. So the apps are they're pulling data as they need it. So you're gonna see that data immediately is the short answer. And then if you think about data cloud, if you're hitting, those JDBC calls that we talked about, that's all real time as well. So you make a transaction, and you're gonna get it that immediately. The days or the alternatives used by maybe some other solutions where they have to pump data into a data warehouse and you have to wait hours or days, those that just does not apply in Workday, thanks to our in memory object model. Alright. Next question for you. How are trust and governance handled for custom agents and apps? Do we need to configure security from scratch? Definitely not from scratch. So it's a bit of a bigger conversation. We've actually invented a a new kind of security control called an agent system user or an ASU, and it has to do with putting together the capabilities to call APIs and tools with who's in front of the glass. And so it will honor who you are as an individual, but the agent has the ability to execute those different skills. Definitely a conversation we'd wanna spend a little more time on, but it is a problem we had to solve when we think about agents working autonomously or working behind the scenes, but yet retaining the security privileges of the individual. So rather rebuilding that from scratch, we're just using the security privileges that you already have in your tenant today. Alright. We've got time for two more questions. I think I can grab these. So, one is whether Workday will be, announcing additional data cloud partners. So the answer is yes. So besides Salesforce, Snowflake and Databricks were announced as technology partners at Rising in the fall. We also announced a partnership to support data cloud for Google BigQuery at Rising in EMEA later in the year. And then additional partnerships are definitely part of our future plans for Workday Data Cloud. Hey, Yeah. Suzy. Can I grab a question that we saw come through? We. thought it be good to talk about. Someone asked you what where's the line drawn between Orchestrate and something you would build in Studio? It's a very good question. So we are focusing most of our energy around Orchestrate. And the very early line you might draw is if it's high event based, high set of transactions, Orchestrate is absolutely the answer. But we've evolved Orchestrate so far now that most things you can do inside of Studio, you can do in Orchestrate. If you were starting a new project today, you should absolutely be looking to Orchestrate unless there's some really edge case where Studio does something it doesn't. But think Orchestrate first whenever you're building integrations at this point. Thank you. Thanks for highlighting that one, Don. Okay. So that, kinda takes us through our q and a. We're at the end of our session here, and I just have a few more things I wanted to share with you. Let's go to the next slide. So, a few things I wanted to point out if you would like to learn more. If you are Workday customer, you have access to the developer forum today, and we've got a link there. So, all kinds of support, conversations, code being shared. It really is a, very, very robust community. As Jennifer mentioned, 17,000 members strong. So check that out. Also, starting in February are what we call Workday lives focused on build. So Don covered an amazing amount of ground in about twenty minutes. These will be ninety minute sessions that go much wider and deeper, so encourage you to sign up for one of those. And then Workday Data Cloud, we are we've got an early adopter program. If you are interested in joining that, we have an application, there for you to apply. So other than that, I'm gonna end on this one. A big thank you to everyone for attending. If you have never been to DevCon or have an interest in coming to DevCon, you can grab that QR code there. We're there at the June in Las Vegas. It's an amazing opportunity to get hands on with all of the tools, and interact with all of the amazing developers who are building a Workday. Thank you everyone for joining today. We appreciate your time and interest, and hope you have a great rest of your day. Bye bye.