Name: Building with Workday Extend: Customer Spotlight with Danaher & Enmax
Uploaded: 2025-11-18T18:16:06.592Z
Duration: 59 min 44 s
Description: Building with Workday Extend: Customer Spotlight with Danaher & Enmax

Transcript for "Building with Workday Extend: Customer Spotlight with Danaher & Enmax": Alright. Let's get started. So hello, everyone, and welcome to today's webinar, which is the Workday Extend customer spotlight session. We're thrilled to have you joining us today. We're gonna be featuring two Workday customers who have been driving real innovation leveraging Workday Extend. But before we get into the content, just a few housekeeping items. So all participants have been automatically muted. For any questions that you might have, please use the q and a feature, that's, provided to to you on your screen. And also this webinar will be recorded and distributed after this presentation. Now moving on to our product statement, please make all purchasing decisions based off of product that's available today as opposed So let's begin with some introductions. My name is Sam Shaw. I'm part of the center of excellence team here at Workday specializing in all things Workday Extend. I help our customers evaluate the toolset as well as any use cases that they might be thinking of building. And today, I'm joined with, we're joined by Shail Goyal. Shail is an enterprise architect here at Workday. And then I'm thrilled to introduce our two featured customers, Maureen McKenzie as well as Brad Sandy, and you'll be hearing from, from them more shortly. So the majority of our session will be spent hearing directly from Maureen and Brad. But before we transition, to their stories, we'll start off with a brief overview of what extend is, especially for those of you who might be newer to the product. And then we'll also, follow that up by, a short demo where we'll review an application as well as some, functionality on how to build an application. So moving on to the extend overview. So when we think about Workday, you know, flexibility has been at its core ever since, you know, Workday's existence twenty years ago. And that remains true since you know, until today or from now on as well. But over the years, we've consistently heard from our customers that Workday is fantastic for all of the core functionality that it provides, but every organization, has unique processes related to people and money that should live inside of Workday, but it doesn't simply for the fact that that capability doesn't exist, within within the Workday. It it's not provided within, within the modules. So with that being said, a lot of our customers are having to kinda go outside of Workday or to build them or they're having to, really, like, do it via a manual process and not really, able to digitize them. And what Workday Extend does is it helps our customers basically ensure that Workday remains a single system of engagement for all things people and money. So when we think about Workday Extend, it's a toolset that allows our customers to build applications that natively live inside of Workday. And it's the same tooling that our developers use internally at Workday to build applications, or delivered applications. Now our customers are able to do the same thing, with their own custom bespoke applications as well. So when we think about what an application is, think about it as an experience. Right? So you're building an experience that natively lives inside of Workday and looks and feels like Workday. You're able to capture new data via business objects as opposed to custom objects. This experience is protected just like anything else inside of Workday. You're able to deliver this experience via both a desktop as well as a mobile, mobile device. And what's unique about Workday Extend and what you build with Workday Extend is not necessarily only the user experience that you're delivering in Workday, but the interoperability that you have with those experience. So for example, this is a charity donation application that you see on in your screen, and this application basically allows, an end user to go into Workday and choose a charity that they would like to donate to. And what's unique about this application is not only, you know, does it allow a user to choose which charity that to donate to, but behind the scenes, we're able to connect it to do things like one time payment or connect it to payroll. So the ability to build these user experiences and then connect it to other processes within Workday in a seamless way is really what's unique about Workday Extend and what you build with Workday Extend. And not only are you able to connect these applications with, with other things inside of Workday, but you're also able to connect it to third party systems as well, and then also leverage things like Prism analytics, some of our AI and AML capabilities, Workday journeys, and anything else that's offered in core Workday. So Workday extends been GA since 2020 and the feedback that we've been receiving from our customers has been extremely positive. We've have over 2,500 applications that are currently live in production. We have, 14,000 developers in our developer community and over 1,200 customers that currently own a toolset. And in addition to that, we have 50 certified implementation partners, that are helping our customers deploy and build applications. And one thing that, that we've been working on from a product side is making it easier for our customers to build applications. And quite recently, we introduced what we call Workday Developer Copilot. And what this is is it's a Gen AI companion tool, that allows a developer to build applications much faster. So what it would do is it would allow you to do things like build pages, or create pages via a prompt, or generate WQL statements via a prompt. And from the customers that have been leveraging this toolset, we've been hearing, amazing feedback from this as well. So developer productivity has increased over 50%, when leveraging developer Copilot as opposed to not leveraging it. So we're we're we're introducing AI to help our customers build and deliver applications much faster. So enough about me kinda just telling you what extend is. I'm gonna go ahead and pass it on to Shail, and he'll cover, an example of what an application looks like as well as, developer Copilot. So Shail, go ahead and take it away. Great. Thank you, Sam. Let me share my screen quickly. So as Sam said, by the way, my name is Shail Goyal. I'm an enterprise architect here at Workday. I focus specifically on Workday technology platform, including Workday Xtend. And what I'm going to do is, give you two quick, demo or show you two things. First is an app in action, meaning, you know, what does the end user experience look like for something that you build with extend? Then I'll take you more into the developer experience and specifically using the tool that Sam was just talking about, our developer copilot. But in terms of, you know, leveraging what you build with extend, meaning the end user experience, it's no different than, the end user experience for any workday delivered functionality. And that, what it really means is, you know, your end users will not know, don't need to know if what they're accessing is built by your organization or it's something delivered out of the box by Workday. It is by design to provide a seamless experience. User will consume the functionality just like they're consuming the delivered functionality. That means, you can put it as an announcement, that app you build on the homepage. You also now will have the ability to create like what we call these cards on homepage and other places like a custom hub and search. You can always have it searched using the the Workday global search functionality like I just did here. Look for AI gateway. It can also be deeply embedded as a related action. So the multiple ways you can actually, get to the the app. The app I'm going to show you, it's leveraging what we call the AI gateway functionality, meaning it is leveraging what they delivered AI models. There are all those different AI models that what they use out of the box for delivered functionalities, and some of those we also have option to leverage within our custom apps. That is through what we call AI gateway. The app I have here is for what's referred as the Document Intelligence APIs. It's a set of APIs that enable you to call the Workday core AI models without having to really train those model or know any technical details. Just with a simple API call, you can leverage those. In this app, it's a proof of concept. Obviously, what you build will look entirely different, but it conveys the point that what first of all you're looking at is an extended app. I have a page. Obviously, it says here as a footer you know, powered by Extend. You don't have to. You can put whatever you want. But, you'll notice again the look and feel and the behavior of the app is identical to the delivered functionality. But this app specifically is about processing certain documents. Through this document intelligence with AI Gateway, we give multiple different type of parsers. There is a generic parser for processing an image that may have text. I have, for example, if I upload this dummy employee badge, and I would like to extract the text out of this image, I can leverage this parser. It's a generic parser that processes an image with a text. If I do this, it's going to give me the wall of text out of this image so I can then use that for further processing or whatever my use case that I may be working on. Now, it is a generic parser. It does not know what ID number or zero zero zero or DOB or any of this data really means, but it at least gives you all that text from that image. Right? We can also use it more interestingly for other type of by the way, I don't have all the ones listed out here. We have parcels specifically for things like driver license, passport, invoices, a whole bunch of, right, along with resume. The idea with resume is you can upload, let's say, if you're working with a candidate or someone and you would like to do, let's say, a skill gap analysis, meaning, infer the skills out of a Word document of a resume that I just uploaded and compare the skills of that it will the AI model will infer and compare it with, the skills from a job profile. Let's say this candidate is applying for HR manager position. So we can infer the scale out of the two entities, the resume word document as well as the job profile that's in your workday tenant and do a gap analysis between the two. So multiple things happening. We're using two different AI models here, the document intelligence as well as the skill gap analysis, models. But excuse me. In this case, it gives me some of the basic information like this one is specific. It knows that John Hensley is the name or this employment history you see here, that store bound or human resource manager, that's the title and the employer and so on. But other thing, you know, it does is infer the skills and then compare between the two. It's telling me there are two skills, that are in common between the resume and the job profile. There are nine additional skills that are in resume but not in job profile, and then there are nine that are missing, meaning those are being inferred from the job profile but not found in resume. Just a quick example of what's possible, what you can do. Obviously, you would take this data or this information to do your further processing of what you would really want to achieve from a business use case point of view. But it hopefully gives you an idea of what you can do. Again, in both these cases, the two models we are using, all we need to do is just call an API. It's a simple restful API call to do that document intelligence as well as the scale gap analysis. Hopefully, again, this give you a quick idea. You'll also get to see a few other apps that both Danaher and Nmax have built in a little bit. But let me also give you a quick view of the developer experience. From a developer's point of view, you utilize this resource, a central place we call developer site. It is a central place for all things related to extent development, meaning this is where you'll find resources to learn like the documentation, the developer forum. It's a great place for all the developers to communicate with each other, the product team, to share ideas, to share best practices, ask questions and so on. But this is where you'll also find, for example, a catalog of pre built apps, what they provide to all our extent customers. These becomes templates that you can leverage to get started with the use case you may have on hand. You may have a similar use case. There are, what, 59 of these apps in this catalog. It's a growing list in different areas of what they like both in HCM and the finance area. But again, you can leverage these for either as a learning exercise or a starting point for what you're trying to build. There are also other things. You obviously have different mock up tools and so on. But let me actually take you into one of the app I have here. It's a very straightforward app idea, meaning you have a need to, give recognitions, for employees. In this case, you're nominating an employee for a recognition. What you see on the left hand side are the different app components Sam was earlier talking about. You have some pages, UI pages, you have some security domain, a business object. In this case, I have called nomination. It has some fields, date, employee name, and so on. You define it declaratively. As you are noticing, you don't necessarily have to write any code for all this. You can do it visually. You see this switch at the top, visual versus code mode. I can flip this if I am interested in looking at what the code is, but you don't have to. You can do this declaratively or visually. In this app, all I have is a security domain that secures this business object that has fields like date, employee name, the reason we are nominating, and the organization core value we are nominating them for. Then I have a starting page that looks like this. Now again, pages you can build visually. You can also see what the page will actually look like when you deploy in your tenant. What we call the app preview functionality. As you can see, I have two cards. Each card has a button. At this point, it does nothing. It keeps just coming back to this page because there is no other UI pages or any action to take. What I can do is I can leverage the Workday Extend developer Copilot, our generative AI powered companion. It does two things. I can leverage it to ask questions. I can find out information. For example, if I'm not sure what's the best API to create a prospect, for example, I can ask this. Obviously, all this information is available in Workday documentation and other places on the developer side, but you don't have to go look for it. You can interact with the co pilot, meaning give your prompt and natural language and find this information and summarize it for you as well as give you the list of resources if you want to read more. Or even technical questions like, how do I get max of two dates? You can ask these type of questions as you're building your app to get you started to build ultimately your app faster. In these cases, as you'll see, it returns this information. It tells you how exactly days. It also gives you the code that you can copy paste. You can just take this code and put it in your app. But you don't have to actually do a lot of time copy paste because you can also leverage Copilot to actually do the things for you, build the code or the pages and the queries for you. I can leverage this to generate components and as you can see here, to generate graph queries, WQL, PMD script, pages, and such. Now in this case, let's say I would like to build a page to give a nomination. Right? So you saw I had a business object called nomination and it is very context aware. In this case, if no I have that, I can provide that prompt or I can even write. I picked it up from the prompt library, which is dynamically generated, but you can also write your own prompt and it generates the code for you. You can also view what that page will look like, and there you are. There is that core value field, the date, the employee name, and the reason. But if you want, you can also continue to iterate upon it. So for example, move the employee name field to the top. And for, let's say, core value, put customer service as the default value for the core value field. I can describe what I want my page to look like and Copilot will generate the page accordingly for me. And by the way, it's not just generating the page. First of all, let's see if it did what I asked it to do, meaning apply name right there at the top and I got core customer service as the default value. By the way, it's not just generating the page, a skeleton of this page, but it's a fully functional page, meaning you see this employee name since there was a relationship defined between this field to the workday delivered worker object, it built a graph query to get the list of worker and have it as a drop down. You can see this is the page, but this is the get worker query, also create nomination as it put a whole bunch of mob data as well as any other changes that are needed in the metadata file. Once the page looks good, I can go ahead and add all this or some of this, whichever I want, to my app. Once added, if I go back to my app, you now see earlier I had only one page. Here is the second page that we just built with the Copilot. This is that page. Again, it's a fully functional page. I can continue to select and add value and even have it persisted because we got that create nomination graph query also built for us. Now, you can further customize this page using this page builder functionality visually. For example, if I want date field to be at the top, I can just drag and drop. If I want this reason field to be not just text box, but let's say a rich text box, I can pick that, make those changes, and then refresh the page to see how it looks now. Again, the idea is with these type of tooling and functionality, your development work will be much faster and efficient to get you started. Let me stop here. Again, just a quick preview of what the end user experience as well as the developer experience will look like for using and building your extended apps. Send, let me give it back to you. Great. Thank you. Thank you for that demo. One thing that I did wanna know is for the developer Copilot, and this was something that we announced at Rising, but this functionality is also being expanded to, also, help with orchestrations as well as API. So our customer our extend professional customers, will also be able to leverage the developer copilot for those two, components as well. Thank you, Shell. Now onto the customer spotlight segment, which I'm thrilled to have. I'm gonna go ahead and, let's bring in Maureen to to the stage. And let me just see if it's green. Well, Maureen, first of all, thank you so much for, for agreeing to do this. And I also wanna congratulate you for, being a winner for the innovation award, at Rising this year. And it was for these apps as well. So really excited and looking forward, to to hear your story and to have everyone learn learn about what Donahara is doing. So maybe, like, just to kick things off, if you wanna go ahead and just introduce yourself, Maureen, maybe share a little bit about yourself and and your role. Yeah. Thanks, Sam. So I am Maureen McKenzie, and very excited to be here today, and thank you for the opportunity. My role is I'm a Workday solution architect with a focus on security and compliance at Danaher. So that's me. Yeah. But, yeah. yeah, and and what what exactly does Danaher or Danaher do? Yeah. So, essentially, we are a global science technology company. We're based in DC, which is also where where I'm from. We're a conglomerate, I would say, that owns over 15 businesses, and we're specializing in biotechnology, diagnostics, and life sciences. And right now, we have about 63,000 associates located all the all over the world, which makes security very fun and exciting. And and I suppose we are customer 1,254. So. it's pretty pretty great. Yeah. And then, maybe talk to us a little bit about your, experience with Workday Extend. So when when did Donna, her, procure Workday Extend, and, how many applications do you all have live in production today? Yeah. So we went live with extend in 2024, and we only have two applications that we went live with that we're gonna talk about today. And that's our security access request application, which I'll call SAR. We went live with that in October 2024. And the second is our user access review application, which is how we perform our recertifications. We call that UAR, as many customers do, and we went live with that application in March. Got it. Awesome. So let's talk about those applications. So let's let's start with the security access review application. So what what prompted this project? And maybe maybe kind of talk about what what you were looking to solve with this application. Yeah. So I think and this is sort of what led us to purchase extend was we had these two audit findings, and they were internal audit findings, and we have a very strict, audit, process. And we needed to rectify these by the end of the year, and we were basically shopping around for, out of the box solutions, but, you know, nothing there's always those trade offs and and this could still be costly and and take and be quite expensive. So so one of the one of those things was our security access request process. And so, basically, that's how we now provision security for both role based and user based roles in Workday because we use job management at Danaher. And and I know other customers have built security access request extend apps, and so that was what inspired ours. And thank you for putting those out there on marketplace. But before this, we essentially had two ways that we were having our security partners request access and both had their issues from a compliance standpoint. So first, we tried just allowing security partners to assign roles using the business process directly in Workday. We were able to route those for approval which was good but what we didn't have was documentation tracked of why the access was needed and what scope was intended. So then we also had this other process and this was for more complex access like intersection roles. And I think it's because we didn't trust our security partners to get it right. We had them fill out a clunky Excel template and then open a case for our team to assign that security. And that became our number one case type at 32% of our cases, and these had a three day turnaround. So not a great user experience if you're trying to do some work. And the biggest thing was managers were involved in our security access provisioning, and they now needed to be per our internal auditors. So for us, you know, our our big question was even if we are able to create the request form, how are we going to educate managers to pick the right roles, the right organizations, and then understand complex topics like intersection security? So so we we were looking at these other solutions, and we do have SailPoint, Saviynt, and ServiceNow at Danaher. We use them in some capacity, but when we spoke to those teams it, you know, again, just there were a few things that we just couldn't do. So as you can see on this slide, this is how we now request our role based security and we have the exact same thing for user based. And it's really cool because you'd launch this process right off of the worker record or search for this as a standalone task. We actually have this living in sort of a dashboard and so people can quickly get that task along with user based. And then I'm gonna go over to the next slide. And so, you know, after you input that business justification and explanation for the for the role, then that's where you're able to select the roles. And one of the coolest things that we were able to do is if you look to the right, you know, you you click the the role. We have our role dictionary now embedded in our application. And so then when the manager picks that role, they can see the role dictionary filter for that role description and approval criteria. So also if it's an intersection role, the app is going to clearly tell you what the other role that's required is. So everything all in one place for that manager experience. They don't have to go outside of the application to find this information. Then real quick, wanted to share this with you. When you click the roles, we actually have you go role by role so that you can actually pick the organization. And this was a huge deal for us and one of the main reasons why we went with extend. So, believe it or not, being able to select the current organization was not possible to do with SailPoint or the other solutions. And so with those, we would have to have an integration and it would have to sync at some kind of regular interval, be it four hours or eight hours. And at Danaher, we're creating and activating soup works, cost centers, companies, locations constantly. So having, you know, a four hour, eight hour sync just wasn't going to work. And so when we were able to build this app and then select our organizations in real time through extend, that that was the the major reason why this this application was just so so meaningful and is so successful today. Once you submit that request, it routes for approval. Once approved, we have an integration run and it either assigns the role or removes it. And we're also able to use all of the reporting for, you know, this business object, which before it was actually very difficult to answer simple questions for audit of, you know, who was given access, you know, at what time and what time period, because of those role snapshots. So this this app has made that, much easier and has made it made audit so much happier. Yeah. That's amazing. Thank you so much for walking us through that. And, again, like, what you had just mentioned, which is the one of the huge value for building things inside of Workday is it's like the real time sync. Right? If we're building experiences that have something to do with the data that lives inside of Workday, elsewhere, you see, one, it's not going to sync, right, in real time, but also, two, like, you're gonna have to manage the security and the data component as well. And then another point that you had mentioned was just like the uptake for the managers. Right? Like, you're creating a new process and you're for a manager and having it in a in an environment that they're really familiar with and it's it's a natural kind of place to manage this, just removes a lot of the friction from an adoption perspective, right, and and the change management as well. So I really appreciate you sharing that. Well, let's move on to the user access review application, your second application, Adanar. Maybe same same kind of question. So maybe kick us off with, like, what this application is is as well as, like, what prompted you all to build it. Yeah. So this one and I know just being at rising, many other customers struggle with coming up with a process for this. So, again, our audit team found our current way that we were performing user access reviews to not be in compliance with, you know, Dan and hers internal, you know, general controls. And so the main reason was we didn't have our managers involved in the process. And so what we were doing was before we would have our individual security partners at each of our businesses, they would run reports, take screenshots, complete Excel templates, and our our team had to collect all that information, validate it. We then we track completion. We sent out reminders, escalations, all manually. And if a role needed to be rejected, you had to submit a case for that access to be removed. And then we have something called a a manual look back process, which I don't know if other customers do. And when we ran the numbers of how much time this was taking, it was over two hundred hours worth of admin work, you know, across all of our our different businesses. And this wasn't even counting the time to perform the actual review. And despite all of that effort, we almost never saw any changes out of the cycle. And so usually it was just a handful and we had over 18,000 role assignments that were being reviewed per cycle. And so essentially we knew that there was no way to scale this current process that we had to hundreds of managers who were now going to be responsible for executing the review. So, fortunately, we had extend and we had experience with the SAR app. And so we kind of built this one from scratch and didn't have the inspiration that we did from the other customers. So hopefully, this could be, you know, maybe that that inspiration for other customers likewise. But in order to launch this and as you can see, this is our our application. But prior during each cycle, we take a snapshot of each user's roles at a point in time. I'm then able to select the dates of when I want the kickoff reminder and escalation alerts and emails to go out. I run the integration which takes the role snapshot report and feeds it feeds the data into our application. It's a set it and forget it. Then managers come, they open this application. You can see they can click on that first card, which is the step one manager review card, and that starts the the certification. And so if I come over here to the next slide, once they they click next, they're able to see a list of direct reports with access for whom they need to perform the review for. They can select one worker at a time, you know, a handful of workers at a time. And then when they go and they they actually look to the right, you can see that they're able to see all of that workers' roles right at their fingertips. And, again, we embedded our role dictionaries so that the manager is able to clearly see right within the app, you know, what that role does and what criteria their person should have in order to maintain that access. So then pretty cool here, we were able to add the mass actions up at the top, you know, prove all, reject all, your standard. And then we were able to add some conditional, I guess, fields here where if you, like, if you clicked reject, then we would have this this question pop up which was, you know, was access appropriate up to this point? And so that only appears if you answer no. The explanation field, we were able to make that turn into a mandatory field. And that question, if you answer no, fires off our look back process. Then when the manager finalizes their decision, an integration automatically removes the rejected roles immediately. So no more cases, no more waiting around. And then as you saw from the earlier card, we launched that look back process, and we fully automated that look back process. And and then that's made our lives so much easier. Awesome. Thank you for that insight. I also wanted to and and you mentioned, you know, a little bit or briefly around just, like, the number of hours that you all have saved. But maybe you can just double click on, like, like, what what was, like, what was the kind of, like, what was the ROI, right, with this application? Like, in addition to just the hours, like, what what type of value did it provide the organization? Yeah. So amazingly, you know, I talked about two hundred hours worth of manual admin work. We were able to automate so much of it that it now takes fifteen minutes to set up the app for each cycle. And it's just me kind of putting in dates and then running that integration. And, you know, even to perform the audit, we used to allow four weeks to complete the audit, and it was always, you know, a rush to the end, you know, begging managers to get it done at the eleventh hour. Now we only formally allow three weeks and we're finding managers are actually finishing in two weeks. And so less chasing, etcetera, a lot better. And then to me, the most important thing is our findings and, like, the number of changes jumped from almost zero because it was just a check the box exercise that security partners wanted to get done. And now managers are actually flagging 5% of our security assignments and having those removed. And so the quality has just, shot up big time thanks to ease of the application after you remove all that manual pain. Yeah. Amazing. And I guess shifting gears here, like, who manages these applications internally, at Donner Hart? Like, is there a lot of management that's involved? Yeah. So I I think first we wanna think Deloitte, because Deloitte was our partner in building these apps and, and we built them so quickly. We had to do each one in less than six months and then get them live. And so, you know, after Deloitte handed them off, fortunately, one of our solution architects, who was with us here today to answer questions, Hari Nayak, he was already certified in extend. And so now I would say it's Hari and I who maintain these applications, with support from our Deloitte AMS teams. And we've done a ton of enhancements, you know, since we've gone live. Just kind of perfecting and tweaking and then continuously getting that customer feedback of, like, hey. What help text can we add or, you know, what was confusing? What other features? Originally, when we did our SAR app, we didn't have current role assignments, like, V. pop up in the the home page, and so that was one of the things that we were able to add. And we're now looking at future dated, you know, role requests and also embedding our SAR as a sub process and change job. And that one we're hoping to go live with in just a couple weeks. So, yeah, we're constantly maintaining this, and it just we're able to kind of put it into our normal change process. pretty seamlessly. Yeah. No. That's amazing. And and that is one thing that I would I did wanna call out is, like, when you when you build an application with Workday Extend, like, those applications are update safe. So from a maintenance perspective, there's not really much maintenance that's that's in like, that's required. It's more enhancements. Right? Like, what Maureen, you what you had just mentioned on on adding additional functionality is, okay, we build something and then, you know, when things change or as our processes evolve, like, we can kinda just go in and enhance the app and and add additional features to the app as well. Yeah. I 100% agree with that. Not much in terms of maintenance. It's more enhancements. Absolutely. And and for the audience, if there are any questions, for Maureen, please enter them in in the q and a chat. We'll we'll have some time at the end to, to answer those questions for you. But, Maureen, again, thank you so much for sharing sharing these two wonderful apps that you all have developed and deployed in your environment. Thanks, Maureen. Thanks, Sam. Now let's shift gears to our second customer spotlight, and that's gonna be Brad with n max. I'm gonna share screen. Alright. Brad, come on in here. Perfect. And again, Oh, Brad, thank you so much for agreeing to do this. And maybe just to kick things off, just tell us a little bit about yourself, as well as your role at NMX. Sure. Brad Sandy. I'm the manager of finance and planning optimization. I've been at n max now for about fifteen years, doing various things, here and there, but really the last seven has been focused on finance IS. So kind of like HR IS, but just more focused on the finance modules. So, Workday Fins adaptive planning, and then, the extend development falls in my portfolio. Awesome. So we've been we've been around for for a while. We're customer 672. So we've we've been in, the Workday ecosystem now for, I don't know, ten, twelve years, something like that. Yeah. No. Perfect. Perfect for that background. And and you've also been an extend customer for a few years now. Right? So maybe maybe you can kinda share just just your your journey and then Max's journey, as it relates to Workday Extend. For sure. It was kind of interesting. I, I actually didn't know extend went GA in 2020. You you mentioned that where we kind of started with our first app, 2021. That was the the COVID app that, we kind of all did where when we returned to work and vaccination, all that sort of contentious stuff. So it was it was good to have that safe. So our journey really around extend, you know, started with that and, then we worked with, Workday Professional Services to build a customer invoicing app to simplify the customer invoicing process. And then to be honest, we kind of stopped a little bit. You know, back kind of in the earlier days, the development wasn't near as interesting as it is now. There was no copilot. There was no natural language. It was much heavier code base. So I think we kind of stalled out on using the tool that we had, but we saw some other things going on at DevCon and at Rising, and it kind of really got us thinking again on what we can use. So then we started getting a bit back into building apps. We got more interested in in what it looked like. And then once we kind of got that interest going, we really just started. We started building one small use case into another, and I think we're up to, like, seven or eight apps now, all in. Right? So we we started with, internally building a a app relative to customer conferences. We've built apps regarding driver's profile. And then we're actually working on two apps right now with two part two different partners, with Mercer and Intercrowd. We just found it interesting on things that they had worked on, so we engaged them and and trying to get those delivered. So by the end of the year, I think we're gonna have built five apps this year. That's amazing. And that's one thing about extend. Right? It's it's not when customers are looking at extend, it's not about just building one application, but extend is more of a strategic asset that's you know, will allow you to build multiple applications whenever whenever a use case or need arises. Now let's talk about some of those applications in more detail. Maybe we can start off with the driver profile app. But why did you build it? Can you describe what it is? Sure. So, really, the app itself is is pretty straightforward. It's really a tool to take a look and and load and track information around who we have driving our fleet vehicles. So we have requirements and I'm sure every organization that has commercial drivers has the same obligations is are the people driving your vehicles skilled and allowed and authorized to do so? So before what we had is we had a bunch of spreadsheets, people would track licenses, they would send it into some admins, they, you know, had paper copies of abstracts trying to keep things things going. So it was kind of clunky and cumbersome. Right? Going through and very similar to what Maureen was talking about earlier where it was a big process to have to go through and verify and maintain and keep that up to date on our license is still valid. And then things could expire, you know, you have a big compliance issue that you could have. And and not only that, it was a big exercise for our field crews. And, you know, you kind of always hear that, that old trope about, hey. We're from the government and we're here to help. Well, I think that's what our our workers kind of thought is, hey. We're from head office. We need all of your license information. So it it wasn't great, what we had before. So when we deployed this is it's one time load. You know, every couple of years, people actually have to go and do an update. So rather than having to do it every every year, it certainly has saved a great deal of time for for our utility workers, how they wanna engage on their computer systems and, you know, gets them back out in the field doing real work. Yeah. No. That that's a great example. And and it's not and we have many customers have built apps that are very similar from a design perspective. Right? We have, like, managing law licenses, right, is another one that's that's really popular with our legal teams. Managing certifications, right, for our manufacturing organizations. So this design pattern is pretty pretty common, but it makes sense for it to live inside of Workday. Right? Because your people data, is inside of Workday. And let's still. go we even have copies of the actual PDFs of all of it stored inside Workday. So not just information about it, but the actual PDFs as well. Sure. And and maybe you can just double click on, like, just what what the value was. Right? This application delivered, it's a $120,000 in savings annually and over seven hundred seven hundred hours, per year saved. Is that right? Yeah. That that's what we estimate in because they you know, workers are taking, you know, sometimes two, three hours by the time they upload, get the information sorted through as part of their training program, the admins spending time on it and keep it all all centralized. But you know what? To be honest, even if we didn't save any money on this is the value that we got to make sure our drivers are compliant and where we can audit it, that is actually the that that was really the benefit. that we had. This this could have cost 10 times as much, and we could have not saved a dollar and we still would have done it because it's more around of a certification functionality. But the fact that we save time and it was relatively easy to, deploy was a big win. Mhmm. And easy to adopt, right, from your drivers. Absolutely. Yeah. And let let's transition to kinda just to, like, you know, your decision making process when it comes to, like, what use cases you're looking to build. Because I'm sure the business comes to you with a lot of ideas, right, on what, you know, what they should have inside of Workday. How do you determine, you know, if it makes sense to build it with extend or if it just makes sense to leave it as is? Yeah. For sure. Well, I'll I won't take credit for this idea. It actually, we totally plagiarized it from Sun Life. It was at either a Defcon or a Rising session that they did was, you know, just because you can build something doesn't necessarily mean you should. Mhmm. You know, extend is a great hammer, not everything's a nail. So what we came up with and they had a couple of different questions, but we came up with, I think, six questions or concepts that we basically ask ask ourselves is is this suitable? How does it do it? How does it fit? So if it's about people and money, that's one of the very first criteria we take a look at. The second one really is business impact. How many users are you touching? You know, if you're building an app that helps one or two people, we're not gonna do it. Mhmm. If you're building an app that helps two, three, four, five thousand, you know, we're not that big of an organization of 5,000, but hundreds of people, that that's certainly one that we're we're going to to take on. Right? So and the other piece is is there's a couple of smaller ones that we've looked at but have large, large impacts, and and they're on our back burner to take a look and to build out, you know, not as many people, but bigger dollar impacts. No. That's great insight. And maybe we can just double click on a few other applications that you all have deployed. One being the conference and external engagement request application. And and, again, for for the audience, as you can see, it looks and feels like anything else inside of Workday. Right? From an end user perspective, they wouldn't know the difference between an extend application or something that's just available with core functionality. But maybe you can double click on the on this application and what it does. Yeah. So I think this, you know, probably common across all customers is we all send people to conferences or maybe maybe not conference. You know, the same idea could work for a, external education. So one of the things that we found is we were sending people to conferences and nobody was really tracking it. Right? You would ask your boss, hey. I wanna go to the conference. They'd say yes. Off you'd go. But what we found is we were probably over investing in some employees or sending far too many people to number of conferences because, you know, maybe 10 or 15 people asked to go to the same thing. So it's you know, there's nothing really special or exciting about this. We're gathering, hey. Conference is gonna cost this much. We gather a bunch of information around it. Here's where it's gonna be. I'm gonna be traveling, I'm gonna be flying. Here is who the conference is related to. So I think I put in here an example of rising, which I put in right after we went live, so I think I was user number one. And then it goes, you know, just use a supervisory org, goes to your boss, and then if it hits a certain value, it could go up the chain. Right? So it goes to my director, which then could potentially go to the VP, and then circles back around. So everybody kind of knows what it looks like. You know? And you talked a little bit about continuous improvement. One of the thoughts that we had to enhance this is, okay, now you have the conference app the conference approved, you go. How do you make sure that what the expenses are and get the feedback? So we're taking a look at it at then tying now this to the expense module. Right? You have an approved conference, it'll then trigger off a expense app. We can restart to restrict spend categories where you can't get reimbursed unless you have an approved conference. So that continuous improvement mindset is great. And then also at the end of the day, the conferences and what you've attend to is tied to the worker, so it almost starts to act like a a syllabus or, you know, a history of, hey. You know, this guy went to 10 conferences or this lady has has gone to these external engagements and here's kind of a big big summary of it directly tied to the worker object. So it's great. Yeah. And you can report on it. Right? And and you can have it tied to to the worker inside of Workday. No. That's that's great. Thank you for sharing that. One of the questions that we get asked pretty often, is, I understand what Workday extend is, but where do we start? What do we build? Can you just share some guidance, to customers that might be new to to Workday Extend or that might be just, you know, looking into it and evaluating Extend? Yeah. So I think, what I would say, and this might sound trite, but you just start. To be honest, build you know, find a small use case, build something, make sure it's not delivered. You know, we kind of started exploring that with income verification letters is where that was our first use case before we figured out that that actually was delivered functionality. But, you know, you just start building. Get in there, start building the muscle, start practicing, you know. And and if you can't get in there to start yourself, partner with, one of the the fantastic partners that are there. You know, we've partnered Workday Professional Services, Intercrowd, Mercer, where they've gone in and and they've built or are building apps for us. And to be honest, they're, you know, conversations are fantastic. They take time, they walk you through what they're doing because at the end of the day, you own the code. They're gonna turn it over to you, and and they wanna deliver a good product that you can maintain. And if you can't get in there. Right? So that's kind of the build buy. There's also if you wanna get in and there's the capability, what I call leasing apps. Mhmm. Right? This is now the build on Workday where people have built things, some standard deployments that you can get in and do. And and and sorry. When I say get in and do, you can get in and have deployed to your. tenant. Some great ones in there, we prefer to build versus lease. So we haven't taken, haven't really taken that up yet, but that option is certainly there. And then the ecosystem. Right? The ecosystem, as you start building, there are so many people that are generous with their time and explaining things. You know, The Groove, I think, has a webinar right now, the wizard sessions, where they are talking about things that are going on. So, their their the ecosystem is like none other where people are helping other other people. Yeah. 14,000 and and growing. And we have a DevCon conference every year that's specifically for our developers and their builders, for Workday extended as well as orchestrations and and kind of everything underneath the build, Workday build umbrella. But, I know that we have only a few minutes left, and I do wanna get to some q and a. So, Brad, thank you again so much for, sharing some some wisdom and your experience with Workday Extend as well as some of the the cool apps that you all have built, with MX. Really appreciate it. Absolutely. Alright. Let's move on to q and a. So I'm gonna just pull up some questions that we have not answered yet. So one of the questions, that came up was, around workday build versus, versus workday extend and if they're if they're similar or if they're the same or if they're separate SKUs. I do wanna call out that Workday build is not a SKU. It's kind of, it's our marketing, umbrella that where extend kind of falls into, and it's everything that revolves around building inside of Workday. So that includes Workday Extend, that includes orchestration, integrations, data cloud, which is coming soon. So everything and the entire tool set that allows our customers to really build inside of Workday, kind of falls within Workday build. So Workday extend itself is is the skew. Let's take take some more questions. And any any questions, like, any other questions, that you all see on on the q and a screen team? For some reason, it's not. Alright. Well, I wanna first thank thank Maureen and Brad for agreeing to to do this. We really appreciate it. We appreciate you all sharing sharing your stories, and then, of course, Shail for, for doing the demo as well. If are there any questions, Maureen, do you see on the q and a screen? No. Looks like we're doing a great job answering all the questions. So, Thank you for that. Yeah, thank you everyone, and, we wish. you all a great work day. And, again, thank you, Maureen and Brad, for for sharing your stories. But. have a great day, you all.