Name: Unlock Your Investment in Workday Prism: Roundtable
Uploaded: 2026-05-14T18:32:25.480Z
Duration: 57 min 13 s
Description: Unlock Your Investment in Workday Prism: Roundtable

Transcript for "Unlock Your Investment in Workday Prism: Roundtable": Everyone. Thanks all for joining. Hopefully, you can all hear me okay. My name is Aravind Chandrasekaran. I'm a senior product manager with Workday. I've been with Workday for eight years now. And a quick fun fact about myself is I love talking about data. That's why I'm here. Over to you, Addison. Hi, team. Really excited to be here to talk through Prism. My name is Addison Allen. I am with the Workday build solution strategy team here. So I'm covering Extend, Prism, the Workday data cloud, our upcoming agentic offers. So, if it's if it's a complicated and fun solution, I get to help out, with creating it. So, really happy to be able to drill in more on Prism and its great offerings today with the team. And hey, everyone. My name is Paul Alexa. I'm an enterprise architect. So I'm more of a get get my my hands dirty in the product and then and let's, talk technology from a Workday perspective. So looking forward to the discussion today. Sounds good. That's a solid crew for the next fifty five minutes, guys. So let's make full use of it. So what's in store? So today, we have a four part agenda as, Christine was covering. So I'll do a quick prism analytics overview, maybe a couple of slides talking about, like, what it is and what are the top use cases I know. And already a question has come up in regarding some use cases, so I'll be touching on that one. And then I will touch upon briefly on what is the looking forward with Prism and with data in a cloud. Not sure how many of you have heard about data cloud, but I'll cover that. I'll show you exactly and piece it together in terms of what exists in Prism right now, what's coming up with data cloud, and how you can power all of your analytics and decisions together. And the last part will be the roundtable, which is what you're all here for. So I'll cover maybe ten minutes, and then we'll open up the floor. This is pretty much yard time. Right? Like, you can ask questions to all of us, and you can get answers right then and there in the next fifteen minutes. So and then we'll close out with some next steps. Okay? So I'll get started. Again, this session is not gonna be the typical one way street conversation. So I'll be presenting for ten minutes, and then I'll drop it off so that we can have the chat. So let let me go through, a quick Prism overview. So what is Prism in a nutshell? Right? You've heard this from the prior webinars. You've expressed a lot of interest, but it's your workforce and finance data hub. Right? It's work based data hub that lets you blend in external data with workday data, and you can derive insights. For example, if you have payroll data, recruitment data, all data sitting any any data sitting outside of Workday, you can Prism enables you to ingest it. You can secure it with Workday security model, blend it, and then essentially create datasets and pipeline to answer business critical questions. So what kind of questions are we looking at? Right? It might be different for every single person. For example, for employees, this might help answer questions around their total compensation in that profile. For the HR team, this might be to do with what is my total workforce visibility without relying on IT. And for finance teams, this might be to do with how can I make strategic decisions and plans? So whatever be your outcomes are across varied set of personas within Workday, When you blend in external data with Workday data, Prism lets you give you that transformed and blended data source and the power to really unlock all of those insights. So and it's very closely blended and coupled with our Workday reporting framework, meaning once you blend this data with Prism, a, you get a suite of big data platform tools which are highly performant, which means all of your data sources are index data sources. You can query them much, much faster. And b, you can use those data sources very closely with your existing reporting framework. You're already building custom reports. You're already are building dashboards and discovery modes. All of them are plug and play with the Prism data sources. So so anytime you think about, historical use cases, then that's the that's when you need to consider Prism for. K? So So that's pretty much it in action. We'll talk more about this one. But then I know there was a question that came up, and it's pretty timely. It's a good segue to talk about what are the top HR use cases that we see across Prism. So let me start from the left, which is, total workforce spends. Let's try this through a simple m and a m and a example. Assume you acquired a company in the last quarter, and your acquired company is using a non workday system for managing all their people data. So this is your Workday. You're tasked to with bringing all these employees and their profiles from the non Workday system to your Workday system. And how do you do this? You use this you use Prism to achieve and blend all of this data together. And when you do that, you consolidate your entire workforce population all in a single system with Workday, making it much easier to manage retention, attrition, and even contingent workers. Next, compensation. That's near and dear to many, many of our customers. In fact, we, at Workday, as an employee, I can see my payroll details, my total rewards in my employee profile by bringing in benefits data, stock plan data, and base pay data all within one place on via Prism. And not just right. Prism has become very increasingly popular across other workforce areas like time tracking using badging data, absence management data, employee sentiment, talent and learning data, any recruitment data that you need to bring in, mandatory trainings that you need to take so that and a manager can will be able to look at who are all the employees who've completed their mandatory trainings. All of that are fair game for Prism. We have bunch and bunch of customers across varying industries using Prism for all of their historical use cases. Right? So one takeaway from this slide, anytime you think about historical use cases where you need to blend external data with Workday data, then Prism is your default choice. K? So you would have we spoke a little bit about Prism. Yes. You get it. We spoke a little bit about the use cases. But let's talk about what the future is gonna look like and what is data cloud specifically. Right? Because we made this announcement back in pricing of last year, and, we've been sharing some information across in our community post as well. So I wanna make sure that we are aligned on how data cloud complements Prism. Right? So what is the Workday Data Cloud in a nutshell? Workday Data Cloud is a new open and secure data platform for all your people and money data. Essentially, with Data Cloud, you can get two things. First, you have direct access to data sitting in your existing data lakes and data warehouses, the tools that you already use within your enterprise. Think Snowflake. Think Databricks, Salesforce, Google Cloud, any of these partners. Right? You can use the data as is in those partner platforms without copying and build your analysis in Workday. That's the first thing. And not just that. Second part is you can tap into Workday data from all of these external systems, the same BI tools you use today. Think Tableau. Think Power BI. Think Qlik Sense. Right? All of these, again, using a zero copy mechanism. You have two options to read data out of Workday. A is a live data query, which enables you to get real time access to Workday data. And second is through Workday data lake with a curated list of business objects. And you know what's the beauty of it is this is all zero copy. This is achieved through an industry standard called Apache Iceberg Technology. So now your question is, this is great. You can blend external data with what they did in a zero copy manner. You can use what they did in your external system or BI tools. So where does Prism come into play? So let me give you a brief background. Prism and Data Cloud are complementary access patterns. What we have with Prism today is a unidirectional data story, meaning you can just tap into external data and bring it into Workday and build your analysis. With Workday Data Cloud, it's going to boost this by allowing a bidirectional zero copy access pattern to maximize flexibility. Data can stay in external systems, and Data Cloud will offer direct native connectivity options to your default partners. So what changes with data cloud is, in a nutshell, ingestion or copying the data is no longer the only option, guaranteeing data freshness and no ETL. So the next big question on your head is, okay, this all sounds great. So when is it available? Right? We are working through our early adopter program and validating, what we're building with our early adopter customers. We'll be launching and going generally available in September 2026, and we'll make big time promotions. And we'll have dedicated test sessions and updates to share during the rising of this year. The other common question that I get asked is timeline, data cloud, prism, this all looks great, but talk to me a little bit more on the road map for taking data out. Because right now, if you imagine a lot of our customers are using RAS and WQL to pull data out of Workday. Right? And there are a lot of challenges with that. And data cloud really fixes or really corrects a lot of those challenges. So as part of those, what we are doing is you'll be able to tap into Workday data in a live data query format, or you can also use the list of catalog of objects. So when we talk about catalog, what kind of catalog are we referring to? We are talking about people catalog. We are talking about financial, business object catalog. We are talking about business catalog. Right? So the people catalog of objects, which is the worker objects, the talent objects, those are the ones that will be made available in September 2026 and be co GA. And following that, in the twenty seventh r one release, that's when we will be focusing on the Fint catalog and the Prism catalog. Alright. Spoke a lot. Let's turn in and go focus on the main reason why we are here today, which is on chatting. If I can ask my experts, Paul and Addison and Christine, to come on board, please, and we can start answering some of the questions. Christine, Gammons. anything burning right. now that you wanted to highlight? Yeah. There's a. few questions in the chat, and if any of you would like to if you, use the, the hand raise, we can actually have you join us live if you wanna ask your question live. Otherwise, it looks like we're looking for some more specific use cases. Okay. Here we have a hand raiser. So I'm gonna approve that. And we have Virginia joining us. Hi, Virginia. Hi. Can you hear. me? We can hear you. Yes. So I know that we are, I think, I guess you call it beta testing, the cloud, and we'll also and one of my, colleagues, just asked a question, because we are actually about to go live with, a creative use case solution. And so that's why we're interested in I'm interested in the feedback on that. But, I noticed that with the cloud that not all of the BOs that are in, HR, for example, specifically learning are available. And I just guess I wanted to know, I guess, what's the rationale around that? And, is there a plan to by the time you go live with that to have all of the b o's, especially with learning available? Yeah. I I can take that product question. So, thank you for the question. The main the main reason why we have selected a few BOs is based on customer feedback. Right? Like so across the board, we have chosen our people catalog, which is what we are beginning with. And for September 2026, we have a selected list of business objects which will be published out on Workday community in terms of what will be available. Right? And that's based on prime priority of customer feedback that we have got. But to your point, we will be rolling out additional POs as part of the catalog as and when we progress towards more data. So, yes, we will the high level bucket is people catalog people catalog of objects. Subset of them will be available in GA. We'll continue to enhance those people catalog of business objects, and then we will roll out the FIN catalog and the FISM catalog as well. So we will continue to evolve, and we'll be making it a much more robust and more complete, catalog of business objects. Thank you. the plan. Thank you. Great. Thanks, Virginia. Okay. Did anybody else okay. Here we have Lauren coming in. Hi, Lauren. I got my mom on different screens. Thanks for giving me a chance to ask a question, Virginia and I are colleagues. So we just were in the process of implementing like a pretty creative solution for like our pre boarding team using Prism. And I've been in a lot of these Prism, calls, webinars, collaboration crews, etcetera, that, like, talk about use cases. And I feel like every time they're really focused on these, like, really big high level ones. And, you know, I asked this question in the chat, but I'll just, like, vocalize it. Like, would you guys be able to share or even if there's, like, customers on the phone that would, like that have some, like, creative use cases, that maybe you wouldn't have thought that Prism could solve it, but it it really did. Just to, like, think of think through those, I think it, like, really helps us, get some new ideas. Paul, do you wanna take that one? I know you talk a lot to customers and on use cases and the solutioning, you think so. Do you wanna chime in? Yeah. I mean, I'm I'm kind of at a loss because when you say creative, that's really, like, pie in the sky. It could be pretty much anything. So I'm I'm not really I mean, I don't have, like, a specific, oh, customer did this, customer did that. I mean but I will say, like, it I think the power of Prism is the ability to ingest data from any system, system, you know, any way. So, like, there's there's no limitation of what you could bring in to Prism Analytics. They they as long as you can get the data out of wherever you need to. Think of, like, if you're using Zoom or Teams. You wanna take transcripts from those meetings and and you can get them in a data format and put them in a prism. We can use that, for example. The the that that's kinda like my thought process because, like, did you have anything specific? When you say creative, is there anything specific you were thinking of, like, in in what So, I mean, like, I can share, like, the use case that we just? did. So we have, like, a preboarding team that, has to check, like, clearances for people before they start. And, you know, sometimes if clearances don't get completed on time, like, they're at risk of missing their start date. And so one thing that we created with Prism was we did connect, like, with the vendor that, does all the background checks and that kind of stuff, and we connected that together and created, like, an instance field that could be filtered to say, like, what's the status of all these people in preboarding. So it can flag who's at risk and whose start date is gonna need to be updated, and it, like, gives our preboarding team, like, so much more visibility than they possibly could have had before just using, like, native Workday functionality. And so I was just curious, like, if there were other, like, kinda specific use cases like that. You know, I always see, like, oh, just combine with your old HRS system or, you know, combine with benefits data for total rewards. I was just wondering if there were, like, anything, like, more specific that people have encountered. And that excuse me. And that's a that that definitely sounds like a a great use case. I will say, you know, when we think about, like, creatively using Prism, you know, Prism is really great what its functions are, being able to pull in data, transform that, blend it with your data. Like I mentioned, I'm with the Workday Build Solution Strategy Team. So Prism is a really important component in a lot of those kind of more creative solutions to help bring everything under kind of the Workday tent here. So I think, you know, if we're thinking creative solutions, a lot of the time, we see pairings between extend and Prism. So, you know, being able to build out, you know, UI experiences to help, you know, maybe validate, maybe update, maybe change, help help administer some some Prism, you know, data flows, pipelines, etcetera. So in like, in the the item that you mentioned, your use case that you just mentioned there, you know, your preboarding team is interacting with that data. There may be a need to update that from their end. You know, like you mentioned, there may be some tasks that then, you know, might might need to be kicked off by some of those flags that you set. You know, an extend could be a great, you know, additional tool within that to help provide that. So, Usually, when I think of creative solutions, it's a combination of multiple pieces there, especially that extended and prison piece. I just wanted to add that piece in there. Thank. you. It's helpful. gonna I'm gonna try to add in. I'm gonna have see if you stay on, Lauren. I'm gonna try to add in Germaine. I think I can add in another person. Hey, Germaine. Have you joined us? Yes. Can you all can you all hear me? Yeah. We can hear you. I think he has some ideas to share with you, Lauren. And I'm also gonna add Virginia in as well. So I'll put you all here so we could all chat. Yeah. I was just saying I put in the chat. We we use it a lot of times to just reorganize Workday data. You know, we came from a legacy system. Users were used to seeing things a certain way. Are we able to group things, you know, in a certain way, for their processes, you know, whether that be HR or, our grants team or our finance team. So we've used a lot to just reorganize data, aggregate it a certain way, and present it back to users, you know, in a way that they can easily digest it. It can help them move along different processes and work day. One of the biggest places was allocations. You know, my company is big with costing allocations, and we found the reporting solutions, you know, around those b o's to be to be a bit short, you know, from Workday. So, you know, we use a lot of different things to, we use Prism and, you know, brought together a lot of different points to solidify that reporting for us. That's cool. know, we've yeah. And we've also. used it to, you know, obviously for, you know, for for, you know, outside, you know, outside vendors again, getting data, getting those reports how we need them to look, without the limitations of standard work they're reporting, so we can get that out to users, you know, in a respectable way. Thank you. I think one more one more thing that I wanted to add, I'm sure this script fits into the creative bucket. Right? Let me share a story that I've, shared multiple times and resonates really well. So when we were all in this, pandemic situation, we were all forced to work from home quite a bit, which means naturally which meant, like, naturally, we were in lot more meetings than what we were used to prior to the pandemic. Right? So then what happened was we slowly went into this aspect of a lot of companies went into this aspect of, oh, meeting fatigue, like Zoom fatigue. Right? So we there was a solution that was put in place across a couple of organizations where we were trying to get employee sentiment data to understand how much time are they spending in meetings, what can we do better. Right? And blending that Zoom meeting information and understanding how we can incorporate a better work culture in that organization. We that is one of the creative ways that I've seen where you can use the survey data. You can blend all of that information with worker data within Workday, and you can really derive insights in terms of, hey. I want to block some time on Wednesday afternoon, which really happened, across our company where right now we have a time block on Wednesday afternoon where it's a no meeting Wednesday. Right? So that we avoid the Zoom fatigue. We avoid meeting, fatigue in there, and then eventually, we work and be productive across the board. So, again, I know you were looking for some creative solutions, but this is something that I've heard quite a bit. So this is not something that existed in the past in the traditional historical use case. Again, think about Prisma as like, you can survey data. You can pretty much blend in and say market data, label statistics data, learning data that you're using across the board. Like, anything. Right? Like so that historical use case, just wanted to make sure that we we are clear. When it comes to Prism, there are two options. Either you are retiring your legacy system and you wanna bring this data into into Workday. That's something that you can use Prism for. The second is you have an external system. You constantly are appending net new data in your external system, and you need to you need to blend it and create a pipeline in Workday to blend it with Workday. Right? Like, so you need to probably bring in data every day. You need to bring in data from this excellent system every week or every month, whatever be that. Right? Like, so you can use Prism to actually create that pipeline and ingest it on a specific schedule so you can derive your insights as well. So your reports will be updated whenever new data is ingested. So two two mechanisms, scheduling mechanism or a one time mechanism. Both of them are pretty common, and you can be as creative as you can. Thank you. Hopefully, that answered and gave you different dimensions. Great. Virginia, did you have another question? Sure. It's more of a comment, piggybacking off of, Lauren and and giving, an example of use cases that one that's on my docket to look at at some point in the future. I think it may be a missed opportunity, to not also mention, what Jermaine did, and I'm glad that I saw his post, and I jumped on before he posted it. But, it's just finding, it's not just necessarily combining, external data, but one use case that I have is the serious limitation that we're encountering as far as regulatory reporting around certifications is concerned. And that was my use case, to use that in in essence, taking, say, equivalence rules, for example, that the I had to have an integration built for me to be able to at least get to that, but it's limited. And so now I have to dump that out and manually massage that and then bring that in as if it's an external data. Right? And be able to use that to improve our regulatory reporting that we have. So I'm glad that, there's someone else who is actually using it in a different way. And so when we say creative, we're thinking about ways that, we have limited, ability in terms of meeting, some serious requirements that we have as far as reporting is concerned and, looking to presume to be able to help us solve that. For example, I just had an ask an expert get back to me for something that, you know, learning is not able to do. And I'm thinking, oh, you know, that might be something that we may be able to solve using, Prism. But again, a lot of the focus, I think, is around marrying external data with Workday when there are some limitations within the actual Workday depending on what domain you're using or even within a domain. For example, learning as well as certifications is one area that we have that you can actually use it to make reporting better, so to speak. And so those are the kinds of things that we're looking for. So I'm glad that, I now have a connection of someone else who's doing what we're interested in as an additional example. And so I wanted to, you know, comment on that's when we say creative, we're looking for things that customers are doing that's not the norm because we have a whole bevy of use cases around what we're trying to accomplish to better service our clients. Yeah. Along those lines, I wanna make sure that you guys are set up for success. All of you are set up for success beyond this roundtable. Right? I've placed a link in, the docs or the reference link. There is a community link that I've placed. Christine, can you help point all of them towards that community link, please, Yeah. on If you go over to the right into the docs tab, there's two links. The first one says Workday community prism. If you click on that, Yeah. that will take you to where Aravind is referencing. Perfect. Right? So if any of you are not there in that customer group, please join. Right? Once you hit that link, it'll give you, like, request to join, and the request will come directly to me. I manage this group, and that's exactly the reasons that you just just mentioned. Like, how are customers using Prism? I wanted to speak to a customer. I want to engage with a customer who is in my similar industry, right, who's just starting out with Prism. Right? Like, so you can ask any question in there. And if you go into. some of the questions that have shown up recently, people ask, like, I tried on this feature. This is what I'm trying to achieve with best practices, use cases. And these are things that you can uncover in a much more scalable and robust fashion in that community group. So we already have the community group. It's product to customer interaction and customer to customer interaction. So you can get best practices that can be scaled beyond something. So just wanted to make sure that that link is available for you. The tooling is available for you to use it. That's really helpful. Thank you for sharing that. I definitely. didn't know that existed. Sure. Absolutely. Yeah. Just hit on, if you're not part of that group, once you click on the link, there is there'll be a button call request to join. It'll come directly to me, and I can let you in. So that's it. And then you you can search for post. I do, every quarterly, I do a product update from there. So I I do, it's a it's a Zoom webinar. The links for all of those events will be there. People join in. It's recorded. So if you are not able to make them, you can listen to the recording. It will open up, a lot of, use case and creative ideas in terms of how you use. K. And. just, yeah, just to let you know, just to one add on to it, we have many customers using Prism for just enhancing their reporting as well. Right? Like, so yes. Absolutely valid. Because with Prism, just wanna follow-up in once, it's a big data platform, and it spits out an index data source. Many of what the data sources that you might have might be non indexed, and you might want to make sure that you make, make use and leverage the the workday reporting functionality when it comes to performance and having an index data source always helps so you can achieve that with Prism. So, yeah, external data or data sitting in workday, both of them are, use cases that you can track purpose. You know, I I did think of another thing too when we just bring up. Because the creative thing is just so, like, open ended. So one of the other things just like Carn said about bringing, you know, bringing slow running reports and making them fast, that's one creative piece in general. But the other thing is in what I've heard a lot of our customers do is is is basically changing security a little bit because before you when you bring things into Prism, you are resetting security potentially on that data. And what our customers have done is they've said, well, look. I purposely don't allow people to see other people in our other organizations. That's a very valid security thing. You don't want them to see that. But what people have done is take the data into Prism, aggregate that external data that they can't see to a higher level, maybe doing counts or something where you don't have in PII data, and then publishing that. And then they can get at and seeing that data on a higher level in the other organizations. So, hey. How is my headcount versus the other organizations? How is my time to fill for JobBox versus other people in my organization where I couldn't see any of that before? But that's another another I I think that's extremely creative to actually be able to take the data and bring it to a level that you're, you know, you you all agree on within your organization, and then you can give them that visibility on that higher level. Mhmm. Yep. There's been a few questions. we've answered in the chat, Aravind, and we shared the user group with some others. I think we've covered more most of these. I don't know, Paul, if you wanna address the one about, the one about the data from Drive, maybe, that might benefit the rest of the group. did have a question about the, as well. I'm sorry. I know you added, me. for Lauren's question. ahead today. Please do. Please do. I had a question about the scheduling. You know, as of right now, you know, the scheduling feels a bit limited in Prism. I was wondering, like, when would there be an opportunity to expand that, you know, regards to, multiple schedules per data change tags or publishing tasks or, allowing the the schedules to be dependent on other workday events such as, you know, other or other workday schedules. You know, as of right now, they're only allowed. to be dependent on workday other prism tasks, or, or even hourly schedules. Right now right now, the the lowest you can go is daily, which, you know, you know, adds a lot of work when we, we need something to be, refreshed multiple times a day, during during business. hours. So I was just curious about that. Yeah. Yeah. I can take that road map question. So a couple of things, Jermaine. So one is we have we recently released a new feature called prism component in orchestrate. Did you get a chance to, were you able to go through the any of the community links? Because, that's one part of your question is in terms of if you have dependent DCT jobs, how would I configure that? Right? So that's something that you can now achieve with Orchestrate. Orchestrate is a orchestration or local tool where you can build event driven workflows within Workday. Prism is integrated closely with Workday Orchestrate. It's available. I I think you just need to sign up. I don't think you need to purchase anything additional for orchestrate. But then once. you do that, you would have the ability to wait on dependent TCP schedules in Prism. Right? Like, you can say, wait for this job to be complete before you move on and run this TCP. Right? Very similar to the question that you had. So you might want to explore that. That is something that we released couple of months before for twenty six hour. Okay? So that's one part. The second part is I know you talked about hourly refresh and the day the daily aspect. So currently, we support a granularity of daily. The hourly aspect, this is our thought process. Right? We are building as I was sharing with data cloud, we are building a more robust long term solution with respect to that zero copy Apache Iceberg technology approach. Meaning, if you have data sitting in outside, as long as you connect that data without copying any of the data, the data sits right in there, you can enable syncing. Right? Like, the the data sync will start. the syncing process, and you will be able to sync and update all your Prism pipelines and, eventually, your reporting or analysis within Workday. Right? That's the approach that we are taking when it comes to longer term approach in our roadmap. So it'll not be more of a hourly schedules, but it's more like you'll get even more flexibility when it comes to connecting external data. So you don't need to worry about it. The automatic sync will be taken care of. Yeah. I agree. Once you, you know, I I saw in the beginning for the data the data cloud, and that definitely seems like a. a viable solution for these types of things. Correct. So I'm definitely excited for that. Just, I guess, one last question about the data cloud is that would that be, would that is that, like, a separate product that we will have to pay for? Is that Yes. okay. Correct. So what we what we're doing is we are, so there are couple of, there's a couple of criteria that you need to be on. So, we'll go through the process. You can talk to your, what they contact as. well, the sales contact. But, yes, it is a separate offering. So Prism is the current offering that you have, but then data cloud is something that you migrate over to if you feel there is a lot of value in this one, which is what many of our customers have. You need to be on public cloud. That's one of the main requirements because we are trying to make sure that we can query the data, much more live. So. it it again, Prism is a separate offering. Data cloud is a separate offering. But a lot of Prism customers, depending on their usage, will have a place in terms of what they take that. That's that's that's something that I wanna make sure that you understand. Okay. Thank you. Yep. Great. And now we have a question from, Kiran. Hey, Kiran. I think, Kiran, you need to, you're on mute. There should be a button at the bottom of the screen where you can unmute yourself. On the bottom left hand side let me see if I can unmute you. Yeah. I can't do it. Okay. Asking about regarding performance and if there's any tool to tune it. That's the question, Aravind, for prism pipeline. Okay. So, Addison, do you wanna take that one? If I haven't seen anything from your implementation. Yeah. As far as, the to tune performance to the, prism pipeline, there there are some, you know, specific, options we have, especially WSP. If there is some you know, you need help from an expert to go into the, specifics there with some certain help. I we also have, you know, some options available out there for review. But I think it'd be very dependent on the use case in terms of like, it might be amount of calculated fields, the amount of calculations that are being done, the volume of data. There's a couple of different variables there. So, if you can put more information in there as well, hopefully, that'll help. But, in terms of from the services side, we definitely would be able to step in and provide some more in-depth guidance that's needed. Well, hopefully, that gave you a little bit of, direction, Karen. Feel free to chat more. I'm sorry that, the system is not letting you unmute. Sometimes if you refresh if you wanna try to refresh and join jump back in, sometimes that works. And we also are most successful on Chrome. So those are if you wanna try again, but or put some, more information in the chat function. We also, Karen can follow-up with you after. So if you're interested in talking to somebody, one one of the folks here or, if you have a Workday CSM or account executive, we can also try to help get some of your questions answered. Then Lauren has a follow-up asking about a little bit more about governance of data in Prism, even if it's just a link to best practices for naming conventions, organizing tables, especially as we continue to pull more and more data into Prism. Yeah. I think the first thing that jumps off, maybe I'll let Paul and Addison add to this, is, there is a a very clear user and admin guide for Prism, which calls out, like, as part of your setup and going through process, what all information that you need to have as best practice, meaning adding a description, having a naming convention. All of those are listed in there. And that's pretty much something that will be covered even in your Prism training. If you have or not already signed up for that one, I would highly recommend that one. Paul, anything else to add? You know what? Refresh me the question I was answering or a tech question. What was okay. It's about the. governance governance of data in Prism, Oh, practices, naming conventions, organizing tables as they pull more data into Prism. okay. Yeah. What Aravind said is about right. I mean, every org I mean, you're gonna wanna just set standards for your organization. So you wanna do it a certain way. We give you the flexibility to do it however you prefer to, but you do you do want to enforce standards. And then when you're moving pipe pipelines from nonproduction to production, you're gonna want internalize at that. So look at the pipelines and look at the naming conventions to make sure you're you're, you know, adhering to that. We wanna give you as much flexibility as to as you can to name it or do whatever you want, but, that that's about what you'd wanna do is kinda just have eyes on it to make sure you're consistent across those naming standards. This way, when people are looking at what's already existing, they can understand it, much much easier and so forth. So, like, you might wanna prefix, as you know, a a dataset that was already enhanced with a a prefix first as an example. Make sure that you're consistent on that as you know, and so forth. Or you can, you know, set base data datasets coming from external a certain way as well. So give we give you the flexibility, but you wanna make sure you you you have your own standards. Because ever and quite honestly, Google, we don't wanna we don't wanna restrict you on how you can name things or or do things. Each customer wants to do things differently. So hopefully, that helps a little bit. Yeah. And just I think one on, definitely, agree on on that piece. As far as you know, I I really wanna, you know, double click on that point of, you know, obviously, in when you're we when you first pull into a table, you know, your list of tables can be really overwhelming. You may not understand, you know, if you especially if you go off of, you know, certain naming conventions, it could be confusing to see where it sits in the pipeline. I've also seen, you know, not only calling out, you know, what's been enhanced or where it is, but, you know, being able to come up with a convention that clearly calls out, hey, this is not the end product table that we have here. This is you know, it might be step four or six in a pipeline, for instance. You know? So being being able to make sure you understand which table sits in what part of that pipeline and that we see, you know, being a best practice as far as that data governance. Yeah. I think one more thing that I would like to add thanks, Paul and, and Addison. One more thing that I would like to add is from a best practice and a data governance standpoint, bring the data that you need. Right? Do not bring all the data that you don't want to report on into Prism just because you can. Right? So we have options within Prism as part of ingestion where you can bring in selected data. So you can bring in through CSV. You can do file upload. You can do SFTP. You have direct native connectivities with AWS, Snowflake, Databricks. So just bring the data that you need and make sure you use that data. Because if you bring in 100 rows of data and then you are filtering it down to 50 rows of data that you actually want to analyze and report on, that's the data that you need. Right? Like, so how can we empower our end users who are consuming all this Prism data to be able to make and try decisions? Right? What data is required for that? Think from that angle and bring the data that you need to power those decisions. And be be sure that you are going to be applying your already set up work based security on top of that blended data source. So you have that ingested data. You blend it with work based data, and you have a blended data source. That blended data source is what will be secured by your existing work based security model. So that is something that you can totally do. Yep. So some governance best practices and admin guide trainings. Yeah. Hopefully, that gives you something to note a lot. Okay. We have another question. Jermaine. Hey, Jermaine. Hey. I had another question about the about the data cloud. So just I was quickly reading through something. I saw in I saw in the slide that you said you mentioned the zero copy, between Workday and then the external services such as, you know, Databricks, databases, whatever whatever. Will that also happen between, like, Workday data source and Prism? Like like, what if, like I said, again, like, we did a lot for just reorganize data within work from Workday. Will that zero copy be happen between Workday business or extend directly to Prism as opposed to an external source? Yeah. Currently, the primary focus domain is on reading the external partner sources of data in a zero copy mechanism. From reading Workday data into Prism in a zero copy mechanism is something that we, we can potentially. So that's not specifically on the road map right now because it's mostly to do with how can you move how can you do attack into external data in in Workday, and. how can you tap into Workday data in an external system. That's the primary focus of data cloud so you can derive decisions. For data already sitting within Workday, we haven't seen, high customer brainstorms in terms of loading that data into Prism. So hence, the focus is primarily for data cloud is on the external data and what the data getting exposed and stuff. Okay. Thank you. K. Hopefully, that happened. Question. Jermaine, I don't know if you saw I answered your chat question in in another way. I don't know if you saw that. Just another creative way. Some of our customers got around the scheduling issue. Okay. I didn't see it, but I'll go back and look. Thank you. Yep. And I know. there was a drive drive oh, go ahead, please. There was a Sorry to interrupt. So, I hope I'm audible now. We. can hear. you, We can. tell you. Yeah. Mhmm. Yep. So, regarding one, one other thing that you told Aravind that not to bring in all the fields. Right? So but but that we try, but then sometimes what happens is while you bring in only the linking field like worker, we are not able to link that up. So what we are currently facing is, like because we don't have any linking objects between Workday Prism data source and the native work they deliver data sources, we had to bring in an external object in between and then both the data there and from there use the Workday data. So is there now, in in short, is there a possibility that we can write LRVs? Right? And we use the report effective date or the effective date on the prism data source as a linking element to look at, data for a specific point in time. K. Harrison, do you wanna take that one? I think it's pretty apt for your extended prism question. Yeah. Sorry. I I I kinda had some audio issue. Could you repeat the, what where we're using the extend object? I kinda had that half where you're trying to bring in more. data, but apologies. So we have, used Prism for our comp review process, but that data, we could not call directly into the planning grid. So, hence, both, we brought that data into an extend business object. And from there, the adjustment for business object is able to call that. So it it is basically to establish a link between a prism data source and a native will be delivered data source. Okay. Okay. So so we're pulling in, you know, essentially are you saying we're point pulling in that point in time data into the extent data source? Is that right? In order. to be able to use Okay. Yeah. Awesome. And then, also, if I if I frame it a little simple, in other words. Right? So if I build a prism data source with 10 objects in here, I have the what they, worker, reference fields in the work they already. But then since I have to build an LRB, an LRB is not all possible on a prism data source, we have to again make, build a pipeline and traverse the new fields all the way from the pipeline to bring it to the prism data source. So that's very, intensive effort to do that all the time. But then if we can directly use what they deliver data sources to bring that data through an LRE, it basically solves, a lot. of problem for us. Okay. So the question is more in terms of a possible product enhancement to allow that kind of lookup related value action into Prism. Is that is that what the question is? K. Yeah. That's Yeah. I don't know, Aravind, if if if the a feature like that. I guess currently, yeah, the the current process would be continuing that kind of pipeline refinement, blending those. datas, to kinda service that. But I don't know if there's any Yeah. Yeah. We don't have any. specific future enhancements in that area. Most of our energy is on the data flow piece. K. Okay. Thanks. That that asks. Thank you. And there was a question on drive, Paul. Is that something, that you wanna come off mute and maybe share? Yeah. I was just typing it in. So, I mean so, yeah, we don't have any direct from Prism into to Workday Drive, but, I mean, I think that without knowing the details, Robert, I would think that you could use a, report as a service to actually input into Prism if that's possible. I mean, I would assume that that's that's unless you're just dropping, like, a spreadsheet or something into there, then you would have to use a file upload that you use instead of dropping to the drive, you use this file as an input into Prism. So either file load or a raster report, or I I would think, based on your question, what you would use. Okay. Okay. It doesn't look like we have any more hand raisers right now, but why don't we kind of have one I have a few questions that came in off to the side for each of the each of our speakers. Addison, I think there's a lot of questions from you. Do you wanna talk a little bit about how the audience actually engage Workday services for Prism? Yeah. Absolutely. Really happy to talk through that. You know, there may be certain use cases that you find that you may need extra help on or or maybe a little bit more in-depth than, you know, your current usage. That's where, you know, especially if you don't have, you know, your first kind of set of pipelines up, we've got some great Workday services available for the team. You know? We're able to, begin that conversation, help you understand, you know, what what that flow is gonna look like, how that data is gonna be transformed, any reporting that's needed. So definitely, Workday services are available, and we'll have a slide kinda towards the end here that'll point out the specific steps. But essentially, absolutely, we're here to to help with any kind of, you know, deployment options, available. And and thank you for pulling that up. But exactly that, you know, reach out with your, account executive. They'll be able to connect you, to a services executive. We'll talk through your use case, understand, you know, the amount of data that you're bringing in, what you're trying to do with that data, how it's secured, and then plan out that implementation from there, which take you from, you know, idea all the way to execution, and and start getting the most out of your Prism, subscription here. So Sounds great. Thank you. And then, folks, the survey is up. If you fill out the survey, you can kinda let us know how you'd like us to follow-up with you and then give us some other feedback on the event. For Paul, I think another question would be regarding would there be any additional data cloud partners coming in the future? Yeah. So exactly. So just when you're thinking about a cloud and what partners, Aravind showed you, like, the four that we you have the ability to, you know, with zero copy right now. We are continuing to evaluate additional partners and and and very much expected to expand, over the next three, six months. I know one in particular that I cannot mention yet, but it will be live. It will be announced next month at, DevCon. So we were always we started with these four. We're gonna have a fifth very soon, and we're continuing to add more and more partners because the whole I I built the whole reason we're bringing data cloud together is to make it easy for your when your whatever extra whatever data lake you're using, whatever tool you're using from a an external vendor perspective to enable that system to zero copy, push and pull data from from Workday, from data cloud, so forth. So we are always continuing to to look forward in adding more partners. Okay. Great. And I think to bring us home, Arvind, related to that is give us a little bit more information about that zero copy approach for Workday data cloud. Yeah. Sure. I I can share more details. So, I I think I briefly touched upon when I gave the data cloud overview. So the zero copy approach is through an industry standard technology called Apache Iceberg. Right? So what happens is say, let's consider an example of Snowflake. Right? Snowflake has, all of that information loaded into that Iceberg Apache Iceberg table. What what they will do is, through, a concept called external catalog, we'll connect to that Snowflake, catalog. We'll be able to just point and read that data. And I know there was a question on syncing this data, on a much frequent basis. So we'll be able to not you don't need to do any copying, but you just point to the data in Snowflake using Apache Iceberg tables. So you'll be able to get that in, reference that in a Prism pipeline to blend and report on that data. And the exact same thing, we will host something called as a Workday catalog. Right? That's where our people catalog of business objects, our financial catalog, our Prism catalog, all of them will be posted. And Snowflake, for an example, exactly the same example, Snowflake will be able to tap into our catalog in a zero copy manner so that they can we can derive insights in Snowflake. So, again, pretty flexible bidirectional zero copy approach through Apache Iceberg technology. The way we tap into Iceberg tables in each one of these partner environments, and the partners can tap into our Iceberg, our catalog, what they catalog. So that's how it's gonna work. Sounds great. Okay. Well, if that's, do we have anything else that we wanna cover, team? Yeah. Oh, one last plug. I know, Paul collect cover collected about, mentioned about DevCon. So, yeah, if Defcon is full, in person attendance is full, that's a classic, developer conference that offered by Workday. It's been a huge success. That's happening June 1 to June 4. So the the in person attendee list is full, but you can always go on the website and do a digital version. So you can join it. You can learn a lot more about data cloud. You can learn a lot more about Prism, customer use cases. All of that information will be there for the digital audience. So just go Google it, and then you'll be able to, look up, DevCon and register for it. That's pretty much it, Christine. Okay. Well, sounds great. Thank you everybody for joining us. We are really happy that you're here. Hopefully, we answered all of your questions today. If not, you may can please follow-up with us. Reach out to your CSM or your account executive, and you can always respond to the emails that we sent out to you regarding this event as well. But we appreciate you being a a great Workday customer, and have a great Workday. Thank you. Thanks, everyone.