Transcript
Delays, I should say, and we're still sort of, you know, depending on what landscape you're on, we're still rolling out and so. May or may not have 26.1, but this is rolling out this month. And we do also have 26.2 coming here pretty soon in June. So that's the target anyway, and I look forward to some of that. Just a quick note, folks, on 26.3 and beyond. So a couple of things. The structure here might change. We're sort of evaluating as a company, you know, just changing up our release cadence a bit here. So there's nothing solidified yet, folks. But again, we'll definitely communicate to you all once we have more information there. But, you know, regardless of that, we are looking at generating some of our self-service V3 developments. So we will we'll get into that here. And 26.3 will be sort of one of those releases where we take a lot of our customers feedback and things that might be missing from self-service V3. And also some of the other areas that we have, like Graphical Action Designer. And we'll be looking to take on some of that work here in 26.3. So I look forward to some of that. I'll move to the next one here. Just a quick touch on the ideas portal. So for this 26.2 release, we had 14 ideas make it from the portal. And I just want to note, of course, that we don't take these ideas just based off votes alone. We're always monitoring. David Deister is always looking at it. And some of you have probably been chatting with him in the comments. So your feedback there, your engagement there is very much appreciated. And, you know, of course, there's many ideas on that portal. So if there's any that are still burning, you know, make sure to comment, raise it against the user groups and other customers so you can get some traction on it as well. Not to say, you know, I guess one thing we are continuing to focus on is looking at the ideas portal. But again, you know, some of that some of that work, we'll continue to prioritize in the future releases as well. Move on to the roadmap areas we'll be talking about. So for the most part, we'll be covering, you know, modern user experience, AI powered ITSM, what we have coming in the AI offerings. Low-code development platform. So these are sort of platform specific updates. We have some around the enterprise automation area, which is more around our LLB and ITAM integration pieces. And we also just want to call out here that we're also focusing on cloud infrastructure. And this isn't something that we highlight in many of these calls. Work that's always ongoing, of course. Right. But I just wanted to call out that we are making some improvements here to the performance stability of the platform. We're looking to modernize some of our infrastructure and add different observability tools so that we can notify our customers when there's things going wrong a lot faster. Right. So, again, this is important work that we don't really talk about enough. But I wanted to call it out. I won't go into too much detail today, but that's an area that we're focusing on. So the other thing here is, oh, yeah, we'll call out some of the ideas as well as we go through these. But anyway, let's start before we get into that discussion. So let's talk about AI for just a minute here and some of the new capabilities we have coming with the AI offering. And of course, this is a separate SKU that's what you would get with the standard ITSM. So but we made some improvements to some of the existing capabilities like instant correlation. Right. This is basically the ability to cluster incidents that are similar based on different parameters. And be able to manage them as a sort of, you know, we could define a parent in the cluster and sort of define it, manage it as one incident cluster. Right. So with this release, we've introduced some additional boundaries, clustering boundaries. So you were able to previously cluster on a service and category and sort of define boundaries in those areas. But now we can also cluster based on team and owner, status, impact, priority, urgency, location, which is an important one, and even description in the subject. So some additional enhancements will be coming in this area for instance, correlation. I'm just one of these small steps that we've made here to improve this capability. All right. We also added some more flexibility, I should mention. So basically now you're able to manually, whatever the defined cluster is, you'll be able to manually remove and add incidents. So, you know, whatever permissions you give to your service desk users, they'll be able to go ahead and do that as well. We also have a new capability around our summarization agent coming. So agentic AI, this is something that, you know, we've been working on and we have some customers that are using it today. But essentially, this is more towards our conversational AI that, you know, today we have a self-service use case. That's kind of our initial offering. We also have some additional capabilities for the analysts coming as well. And so this is kind of our first step into the analyst side of things with the summarization agent. But basically being able to leverage natural language, you know, just chatting with Teams interface, being able to summarize different incident tickets. And again, this is sort of a foundational piece, but more to come with the summarization agent. Different capabilities we're looking at building here as well. So, by the way, you know, we do have a native web UI coming with the agentic AI as well. It's Teams only, but they released a web UI pretty soon here as well. So, and with this release, we're also releasing a AI-powered text-to-code capability for expression. So anywhere you see the expression editor with an ITSM, if you have the capability enabled and you're licensed for it, you'll be able to take advantage of this ability where, you know, basically leveraging natural language, we'll be able to generate our expressions, right? We can optimize them and just speeds up the time to creation of some of our expressions, right? Good change here as well. More towards AI-powered text-to-code coming as well as we progress in this year, but this is kind of our first run at a capability. I just want to pause here before we move on to the user experience. If there's any questions in the chat, I don't see any. Please put those in the chat, folks, if you have any additional questions. Have any additional questions? You can also get to those towards the end of the... Let's move on to modern user experience and see what we have coming in this area. Let's start with self-service. And I mentioned, you know, we're accelerating some of the development here in this area. So we're already working towards things like... And I think we'll actually see some of this in this 26.2 releases here as well. But basically, your visibility rules and issues that we've had with those, really making that a consistent experience across the new UI. So we've done some work to improve, basically, the interaction visibility rules. We've also looked to, you know, the URLs change from V2 and V3. So we're looking to correct some of that as well so that your URLs, you don't have to go and change them all. That will also be coming here. And I don't call out those in a specific slide, but those will be called out in the documentation, the release. The first one here I want to mention is now offering for request offerings. On the self-service V3 portal, we're offering a multi-column layout support. So, you know, in the previous UIs, you've had the ability to have multiple columns. So now with the V3 UI, you'll also be able to create a request offering form with three different columns. And it's up to three, so it can be one, two, or three. But again, you know, if you had offerings in V2 that had multiple columns, or in the classic UI, now as you move them over to the V3 interface, you'll be able to kind of replicate that, the format there. Good one here. There's also an enhancement to the alerts and out-of-box notifications here that we have coming 26.2. So this is basically a capability where, you know, we've kind of gone and enhanced the way that the alerts display here. I'll show a quick demo of what that looks like, and being able to configure different business objects. I have alerts set up, but I can also, if I were to point to announcements, a knowledge-based article, I could do so as well. So let's just get into some of that. I'll do a quick demo just to show what that looks like, folks. And as you can see, this is the V3 UI. You can see that there's a stack of notifications here. I can click on this stack, see several of them. You know, I can minimize that, right? If I click on any of these, it'll direct me to the page. Demo's not going to do it for me today, but we can also go to view all. It's not going to do it for me today, folks, but I'll show you what that looks like here, the setup of it in a way. You can see the alerts show up here as well. I can mark them as red, right? I can go to that view all as well, and I probably just don't have that configured. But I'll show you how that looks here on this side. So within the new style editor for the new UI, essentially you'll go into your global settings, right? It's under this header category here, which is a little confusing, might be a little confusing, but it's here under header. You'll go to alerts, you can toggle that on or off. And then there's a couple of different configuration options here I want to show as well. So if you want to limit how many alerts show up on the top panel here, right? You can also, like I mentioned, point to a different business object. So if you have a net, you could also, this could be an alert. These are just some field mappings. Really, this is how it displays on the front end here. And how often do I want to update this? Also with the actions, for example, with when you click on an item, where does that take you, right? You can take it to a self-service workspace, whether that's alerts or items, some of your other workspaces there. You can also point them to a URL and click. So there's a couple of different options there. Same with view all. So if you want to direct them somewhere else for a view all, you can put a self-service workspace or a URL. So anyway, there's also some saved searches and things that you can, there as well. A couple of different configurations. So let's go back to the deck here. We'll move on to the next one. This one's around being able to have a configurable status bar for my items, right? So again, let's say, for example, I have 10 statuses on my incident business object, and I only want a few of them to be shown to my end users. This capability will allow us to define how we want our status bar to look, right? And they're all mapped to those statuses. So for example, here, what I've done is I've mapped my waiting for third party, waiting for customer statuses to in progress. So my end user doesn't have to see those. They can just see what I want on it here. So there's a way to do that. There's a new workspace to define the mappings. So more details, documentation first. I want to go into a couple, I saw a couple of questions come up, or maybe it was one question before we go on to the analyst UI. Is multi-column and V3 different when working on developing the RL than V2? V2 is painful to develop. It's a new designer. So the experience is a bit different, Suman. I'd love to dive in a bit deeper with you on that. We can definitely connect on it. But yeah, it'll be, there'll be a new designer and everything. I don't have a demo to show it right now. But just leveraging that new UI for builder, right? So Matthew, great question. Sorry, Danny. Thank you so much. And this is going to be in 2026.2, correct? Correct. Yes. Okay, great. Thank you so much. Yes, I'd like to talk to you more about that. Our team would. Thanks. Sure. Definitely. Right, right. Looks like there's a few questions here, folks. So I'll just, we can chat through some of these. Don't have as much of a time strain on this one. So let's say, I was playing with alerts in self-service V3 there last week and wasn't impressed. I'm really happy to see alerts getting some love. Yep, great. Come in, feedback, Matthew. We took some of our customer, early customer feedback on that. And it definitely, it's a much more improved experience. There's some additional capabilities that they're looking to add as well. For example, expiring or expirations on alerts, being able to color code the alerts on the top bar there. So still some work there, but the first version will at least be able, you'll be able to take advantage of what I showed here. Just to confirm, do you mean a new request offering designer? It's a, it's basically the layout builder. So we have, the first version will be just, being able to define the columns. But yeah, basically we'll be able to, it'll be a new form designer for any layout on the self-service side. The request offering designer, however, won't be, it'll be the same request offering designer that you're used to for now. So great question, B. Can the progress bar be dynamic per request offering? Some business processes have different, yes, they can be. You can set up different status bars for your different request offering sessions. That's a great question there. We have, does v3 allow access to custom workspaces from the homepage? Not today, but we are going to open that up here. It's in the later half of this year, 6.3.4 roadmap. Kenny, there are some questions about AI a little higher up. Awesome, thank you for that, David. Okay, AI text-to-code, will that help us make visibility require default expressions when designing request offerings? It should, Ashton. Of course, the meat is in how performant, the level of fidelity that we get out of it. But yes, you'll be able to use it there. And of course, we're going to continue to improve that capability as well. Looking forward to hearing your feedback. I'm sorry, there's not much more that I can give you there. Tim, is there an intent to have forums other than SRs built natively in the request offering? That's a good question, Tim. I'm not exactly sure about that. We'll have to follow up with you on that. I do know that we are going to allow some more flexibility for self-service v3 for building custom or creating and editing custom layouts for form offerings, for your custom business objects, right? I know there's some more work there, but I'll just have to follow up with you on that question. Is there any documentation on the end goal for the agent-to-AI or the functionality that's planned to be available when it goes GA? We're still working on the documentation, Lee. I can give you some background. But basically, the functionality plan will be the self-service agent, right? What it does today is it'll create incidents, it'll create service requests, basically looking at your entire service request catalog and being able to point the user to the right one, right? And you as an admin will be able to find that, right? It's not exposing everything. It's just the request offers you want exposed. It can be all of them if that's what you want. We also have the knowledge base agent, which will search knowledge, internal knowledge base, as well as external websites. And the Q&A agent, which allows your end users to basically check status of all their... So, the summarization agent as well is coming. But yeah, anyway, noted, Lee, we'll definitely, you know, definitely plan to provide more documentation around that as well. All right, I think one last one before I move on. If you have custom fields on incident, do they work if you change the UI to modern UI? So, that's a whole other conversation. But basically, within the new UI, you will provide a migration tool. But it's going to be sort of, you know, it's its own layout, its own business object form. So, anyway, it's going to be a little bit more complex than that. But let's move on here. And then we can talk a little bit about that towards the end. Migration will look like the question to focus on. So, yeah, anyway, with the analyst side of things, again, this capability I'm talking about is the only one that I'm mentioning in this modern UI section that will require the AI license. But essentially, it's a capability for your analysts to be able to leverage natural language or NLP to build their queries, right? So, I could say things like, you know, show me all of my instance arrays for river down with priority one, river down with priority one, all incidents that are breaching SLA within the next 30 days, right? It'll build that query for me and populate that list. And I'm also able to show some of that here, this demo video that we have. So, let's run in here. So, as you can see, there's like a little icon. If you click at the icon, we'll do an NLP-based search. And that'll give me all those records. And then it also builds the advanced filter for me. So, I can either save this or, you know, if I want to share it out with the team, for example, I could save this and add to it as I can. This is people that's coming here in 26.2. There's some configuration options here as well. Today, we just have, you know, which business object do you want to set for this? Or allow for an NLP-based search or querying. And also, there's some user feedback here. And this, Avanti takes this as well. And we use that user feedback, some of that telemetry data to improve our own models as well. But it's still, anyway, there's some of that that will be available here pretty soon. Yeah, the quick filters are pretty nice. This is just an easy way to filter on the new list. And we'll be able to, with this next release, you'll be able to share those out to specific roles and teams, you know, based on your permission, right? So, just a quick win there. This is part of the migration tool I mentioned, folks. So, if you are looking at migrating to the UI v3, and I'm specifically mentioning for analysts, right? Because we started rolling out some of these capabilities. You can now take advantage of this migration tool, where what it'll do is basically be able to clone any layout using the modern UI architecture. It'll make a clone of that layout. It'll also clone the views. We're starting with list views, of course. So, you'll be able to select any list views to migrate over to the new UI. And then same with the foreign views. When we have foreign views coming out, we'll also provide a migration tool for that. With that, the migration, I mean, it's not just a, you know, click of a button and it's all done. You'll still have to look at the, you know, the new forms and new lists and possibly make some adjustments. The goal is, and the hope is, right, it's more additive, right? If you want to take advantage of the new capabilities, some new flexibility with the newest views, new framework, you should be able to do so. But yeah, it will be, you know, you will have to sort of get it to look the way you want it. You can show some of that here towards the end as well. I thought for some questions here, I thought I saw a couple. Yeah, so, and the NLP-based querying, I think that's what you were mentioning, that is a AI functionality. The only one, yeah, this one here, this video, this is an AI capability. So, additional license, correct? Correct, yes. Thank you. Thanks for that. Ashton, I like the ability to ask for tickets that match criteria in natural language. Will it be able to help with search criteria for custom fields too? Yeah, I'll take that one, Danny. So, natural language processing for global chat is, excuse me, global search is a future enhancement. It's not in this release, but it's on the roadmap. If that's what you're asking about, actually, with the first search, or, yeah, let us know if that was your question. I took it more as, you know, basically being able to, well, anyway, sorry. If that's not the right answer to the question, Ashton, let us know in the chat. I may have misunderstood. I saw a screenshot a couple of slides back where you had somebody asking to show all of the P1s or something like that. Right. Was that part of global search? Yeah, this one. Yeah, this is a different capability, Ashton. This is NLP-based querying. The global search is also something that's coming, which is what David mentioned. Okay, so the NLP, will it be able to also understand contextually about information in custom fields? It should. To be honest, I'll need to get with the PM to ask for more details around that, and how the models, you know, what fields the model's looking at. So I don't feel super comfortable answering that right now, Ashton, but the custom fields are an important piece here, right? So. And I had one last comment about, and I had one last comment about the dark mode. Yep, dark mode. On your screen is full dark mode with 26.1. The outer borders are dark, however, the main forms are not. That's a good point. So the list views are available today for dark. What's not available yet is the detail form. Sorry, whoops. Got one of the, that's here. Go back to, so yeah, the list views here, I mean, these can be dark mode. But again, if you go into a form, an actual form view, that those are not yet enabled for dark mode. They will be later this year, right? We have that on the roadmap. It's a bit of a hybrid approach today, Joanne, right? It's, I mean, you can modernize your list views and have all the new capabilities for the detail views. We're still rolling that out, right? So it's going to be a little bit of a mismatch there. So the good news is if you've activated the modern UI for your analyst, it'll also spill over into dark mode availability for dashboards v2, but they're linked together. If you're not using the modern UI, then you're not going to be able to get the dark mode for dashboards v2. It's a little bit of a incentive to move to the modern UI. Great, thanks. I'm not sure that our list views are showing in dark mode. Is that a different setting besides just turning on the global constant? Are you a 26.1 yet, Sue Ann? Yes, we are. All right. Let's connect. I could have, it could be that it's, I don't know, I don't know if it's the same thing. I don't know if it's the same thing. It could be that it's a setting. I could be wrong. Let me check that and I'll ping you later. Thanks. Right, no, I appreciate that. And Matthew, only modern layout list, not all layout list. Yes, correct. Only modern layout list. All right, folks, keep them coming, but let's move on to this next section here. We are making some improvements to ITAM. We've actually, there's sort of a roadmap that we'd like to present to our customers here pretty soon around it. But our first step here is just some small improvements to consumables, really just streamlining the way that we manage our consumable items from a PO standpoint, right? Now with, in the past, we could only have, you had to have multiple line items for each consumable type. Now you can group similar types under one line item. And also, we also now support receiving on the portion of the PO instead of the full PO, right? In the past, if you only, for example, received half the shipment, it'd be sort of difficult to reflect that on the PO. So we made some changes, some improvements in that area. More coming with consumables and the whole purchasing process. So we'll see some more of this in future releases here. Up to ITAM. Some additional improvements. If you're logged in as an asset role, so an asset manager, for example, right? You click the help icon on top, right? It'll now take you to ITAM documentation, so ITSM, small quality of life change there. Honestly, it took way too long for us to do that one. But yeah, it's a small change there. Also, the CI map, the CI service map, now we have the ability to filter those tickets, right? So if you have a closed incident that's linked, we can filter that out so it's not showing on this. A couple small changes for PPM as well. This was more sort of a content refresh release for LLB in general. But for PPM, a couple things here. The callout really is a new action called the calculated capacity. And basically, it allows for ad hoc calculation of an employee's remaining capacity. So you can go to any project, your employee tab, right? Or your resources tab. You can go to a resource plan. And when you click this action, it'll basically look at all the employees of the role that you're looking for. It'll look across the date range that you select. And it's looking at assigned tasks and any actual effort that's allocated to those tasks. Looking at, I guess, tasks that have been completed and scheduled. And also looking at your availability as an employee. And then it'll take all that and calculate what's remaining over that day range. So just a fancy way, I guess, of saying if I need to see how much availability I have for next week, I could just say, look at product managers for dates. And then it'll show me some other smaller updates as well, just more towards some quality of life changes, updates to portfolio finances. So just a couple of callouts there. With GRC, our focus has been more around the risk process, right? And so we've made a couple of additional updates here in this release to GRC risk details tab, to some of the relationships, some of the layouts, just to sort of more align to an industry standard and best practice for risk management. So anyway, more to come with GRC. So we have a direction that we're looking to go more towards the different areas, vendor risk management, AI governance. So building towards some of that as well. You'll see that in future releases. I'll hand it off to David now, just for some of the platform. Okay, thanks, Danny. So let's start off with the Dashboards v2. So two ideas that were listed on the portal that we've implemented. The first was the ability to copy the URL for a particular dashboard, and then be able to cut and paste that into collaboration tools like email or Teams. You can see in this example in the screenshot, there's an industry standard copy URL link. You can also do it on all dashboards. I'll show you that in a demo in a bit. But that certainly helps you to share dashboards with people that have access to those particular dashboards. Another request came in to be able to configure the X and Y axis labels. So right now there's a default that puts out whatever the product name is for the field. And so you can now go in there and modify that during the editing of the dashboard to be able to put in custom labels for the X and Y axis. Works for bar charts, line charts, and pie charts. And really the value there is to make a label that's more familiar to your consumers so that if it's not just saying status, it could make rollout status or customer status or such. And I'll show you a demo of that in a bit as well. Some other general platform updates. So we've added the ability to roll back a package. This allows you to roll back a package that you've just imported into the system. So if you find that, for example, the value there is if you find the package is not working properly, the import didn't do what you expected, you can roll back to the previous state of that particular package. The gotcha here is this only works for packages that are ITSM only. In other words, the code within the product, not within the binaries or the executables for the product. So if Ivanti sends you a patch, for example, that includes a package plus has a binary update, you won't be able to roll that back because we won't store the previous version of the binary or the executable or the library. But it will work for custom packages that you implement yourself in terms of functionality change within the product. Or there's an Ivanti patch that is only, you know, internal code only and not binaries or executables, you can roll that back also. Oh, we also had a request for dependency checker for quick action. So this kind of comes in two, two, not versions, but two capabilities, two paths. So one is that when you're looking at a quick action, you can click a button that says references and show you all the references for that particular quick action where it's used within ITSM. So where the forms are such are used or where workloads used. That's made available at all times. So that no matter what, whether you're in production or whether you're in staging or UAT or development, or whether you're in the classic action designer or the graphical action designer, that button is always available. A second request was to be able to delete those quick actions even if there's references available. That's a bit dangerous. And so you put a guardrail on that. You have to consciously put a feature flag in place to be able to activate that capability. So if you look at the system without that feature flag activated, the delete button will be grayed out. And I'll show you that in a moment. But what you can do is you can activate that button. And then if you want to override it and delete it anyway, delete the quick action, even though there are references, you can make that choice and do an override anyway. We don't recommend that obviously, but because it'll obviously corrupt your forms and do bad things to the product. But if for some critical reason, you need to make that choice, you do have that ability to override the delete and do it anyway. And I'll show you that in the demo in a second here. Some other quick updates for the platform. So we're now allowing you to copy requests, excuse me, copy workflows from one request offering to another. So this has two use cases. So one is you're creating a brand new request offering and you don't want to have to go through and manually create a new workflow for that particular offering. You can select the existing workflow off an existing request offering and use that as your template for creating the new request offering. So it'll copy all the information from the existing workflow into your editor. And then you can make subtle changes to it that you like. It will also allow you to edit an existing workflow. So if you have an existing workflow and you want to overwrite it with a new request offering that you've created after the fact, you could do that as well within the editor. So both use cases will be supported. We have some feedback about some extra scroll bars in the graphic actual designer. And so we've corrected that. So now when there's no sliders necessary, we'll remove those and the old sliders only show up when you're starting to get a larger display. And then finally, in previous releases, when you deleted the audit option off a field, it deleted the audit logs silently without telling you. We had some complaints about that. And so now there'll be a warning message that says that, you know, do you really want to do this? Because if you delete the audit option, you'll remove the audit log entries as well and those will be removed forever. So just keep those in mind. Okay, let me go ahead and get to the demo here. So I'll start off with the dashboards. So again, here's the copy your dashboard URL, very industry standard. You click it, it copies it to the dashboard. Excuse me, the clipboard. Too many boards. And then if I go paste and go to it, then it'll automatically open it up. There's a question on the chat. What's the error look like if somebody doesn't have access to the dashboard? It's the same error as if you tried to copy and paste a URL you don't have access to. So there's nothing special about it. There's not a page redirect. It'll just tell you that you don't have access to that particular URL. But you can see here that I copied the URL and I'm able to launch this. Again, this goes up here as well. Excuse me, it's here as well. And then I'll show you the editing of the labels on the fields. So here I've got some labels. I've got status and I've got count. If I want to go in there and make those unique or different for my end users, we now have the X label access and the Y label access. So if I put in customer, for example. Now when I want to look at the label, it'll say customer status as the label. So again, it'll be nice for your consumers. And then finally, the last thing that I'll do demo for you is the quick actions reference webs. So if I go to quick actions and I go to the graphical action designer. As mentioned, I've got my guardrail on and so the delete button is going to be grayed out. So I could have saved action, get recommendation. The references button is there, but the delete button is grayed out. So if I had activated my system, I would have been able to say delete. It would have shown me the references and said, do you really want to do this? And if you said yes, overwrite, then I could have deleted it. But on production systems, certainly not enabled for the cloud of customers from Avanti. If you're on premise, you can enable it. Or if you're in the staging or the development environments within the cloud, you can put in a request to activate it. But here's the references. So I click on the references. It'll show me all the references for that particular item. We've got a nice pop-up and I can do the same thing for the CAD. So again, here, the delete button is grayed out. I hit the references button. I get my table of references. That's it for my demo. I want to check the questions here, see if anything's there. The dependency checker worked for quick actions to run from a child as well. We believe so, yes. We're doing some final testing on that. It was part of the architecture. But we haven't checked yet if it works from the escalation engine. But yes, it was designed to be able to work from a runner's child as well. So we have that covered. What happens if I overwrite this in staging? If you overwrite in staging, then basically you can delete the quick action within staging. It'll corrupt your form because all the references will still be there and you'll have to go back in and fix it manually. So basically, the best practice is for you to delete the references before you delete the quick action. If you do it the other way around, you're going to have to clean up your mess once you've done that override. And we're not going to allow that in the cloud environment for production. Obviously, it'll only be allowed for staging. Is that only available in GAD? No, it's also available in CAD. Although, obviously, we encourage the use of GAD whenever possible. And as Danny mentioned, we're going to do some rework of the GAD to make it even more usable in the next release. Any plans for reference checker for fields? Can you be more specific about what you're looking for there? Sorry, just thinking, like we've got a dependencies checker for picklists and you're putting one in for quick actions as well. Like you've just shown us. Is there any plans to do that for fields or relationships or any of that other stuff? I've had a few instances recently where I could have really done with one for fields. You're asking, so I identify a field and it tells me where it's referenced within the product. Is that what you're asking for? Yeah, that's the one. Yeah, not on the roadmap at the moment. It sounds like a reasonable idea. If it's not up in the portal already, I would suggest putting it up in the ideas portal and get some community feedback on it. Excellent, will do. Thank you. Sure, absolutely. Appreciate your time, folks. Thank you, thank you very much.
