[Music] good morning good afternoon good evening wherever you may be thank you for joining us today uh for our platform analytics Academy couple quick things that we'll go over from a logistical standpoint and things of that nature and then we'll get directly into our conversation and our topic that we have today so always this is for you uh this is another great session of bringing ideas to you and some better understanding and practical guidance as it relates to platform analytics for you it is going to be recorded it will be out on our YouTube channel later on today or early tomorrow morning as well as in the community event itself along with um a new thing that I'm doing is putting the questions that are asked via type also into the community event quite often those kind of get lost the ones that are recorded obviously are in the video but I'm going to go ahead and put the uh questions that are typed there as well so those will be there for you uh if you need those so with that Q&A please ask questions uh please use the Q&A if you can we do have other uh panelists that are on the call that aren't necessarily delivering the content today but they are here to answer questions uh as they can and they may come off of mute as well as we sort of proceed through the uh content for today so Safe Harbor always just like to mention this um I don't know how much will be in this today but it's always good idea to mention this so you'll have that understanding as you go into what we're delivering for you today and as usual my name is Thomas Davis and I a host and a panelist and Tara and Dan my co-workers are actually going to present the content that we have going on today and we also have Adam Marta Olga and uh Rober Jean or RJ as we call him on here uh as well so as always we have really good people here to answer questions and we hope to be able to fulfill that for you today and have some really good conversation around platform analytics housekeeping Solutions so with that Dan Tara whoever wants it you may take it hey everyone uh my name is Tara fiser and I am here to talk to you Dan and I are here to talk to you about some housekeeping Solutions um what I want to start this off with by saying we know that there's quite a few people on the call today um we know that some of you are shy we really want this to be an open discussion um what what started off us wanting to talk with you about housekeeping Solutions was obviously this migration and that's been in the Forefront of every conversation we've had with you lately um we are moving to a new experience within the platform it's um a newer and better way of doing things for sure but it's a it's a learning curve and so one of the things we started talking about is hey prior to this migration maybe we should give you guys some tips on how to how to clean up um what's going on in your instance and you know housekeeping stuff but while we were talking about it we realized that this is probably stuff you should be doing all the the time not just because we're migrating so this will be an ongoing conversation that we have with you over the course of the next few years um making sure that you're staying top of this as we migrate to a new experience we're going to talk with you about different ways of doing that and going about that um as well so let me go on really quick uh with the agenda this is uh we're going to cover pre Migra pre migration cleanup conversations um how to prune and get rid of some duplicates Dan's going to cover some scans suggestions talk about organization and then open Q&A but we want you to have open Q&A the entire time we're having this conversation so we do have some breaks in here where we're going to ask you to come off mute um raise your hand whatever it is that you're more comfortable with but we definitely want this to be a group conversation because we can leverage your experience and share that with everybody as well as some of the experiences we have so one of the reason reasons why I am presenting to you today is because I used to be in your position here at service now I was the performance analytics admin for our operation side of the house and I have felt your pain and I can only imagine what it's going to feel like moving forward so why do housekeeping this migration and it's not just because of the migration like I said you should be keeping your house clean at all times it's very important to make sure that we're bogging down our instance with a bunch of stuff that really doesn't need to be there anymore and so we're telling we're kind of kind of give you some tips on how to check and see what's been forgotten everything that's been long lost because when we do this migration that we're talking about we are going to look at everything and it's going to pull everything over so this is a great opportunity if you haven't done housekeeping before to jump in and start that um it will also help you complete the migration and batches so if you we're going to talk a little bit about organizing your your in your environment and making sure that you are using the things that we've provided for you indicator groups um dashboard groups stuff like that if you have an opportunity to leverage it and you haven't this is an opportunity for you to take that so that you can group everything and be like okay these are the ones I want to look at next in this little group um and it'll alleviate some of the stress of having to learn new features and also having to treas through unused and forgotten content we want to make this as stressfree as possible um so we we want to have an open discussion with with all of y'all throughout this this entire conversation this entire presentation so remember that this is an open discussion um I will look at my colleagues while I'm talking to tell me if someone raises their hand or if something comes in that um is pressing and we we all want to talk about it together I'll uh look to to you uh everyone my panelists to tell me to stop talking and I will be happy to do that um as we move into the next couple of subjects these are definitely things um we want to discuss with you we got you and we're ready what was that I said we got you and we're ready got I just I just want to just kind of add on to the what you're saying about the about the why we want to do this I just want to really stress when it says the migration tool the migration application when it's available looks for everything every report every every report every widget every indicator every breakdown everything in so including every report as I mentioned so that's why you know you really want to be you know put some thought into it's got to be worth the effort to put some thought into helping you find the uh the content that isn't being used that being said part of the reason we're having this discussion is because there isn't a one size fits-all perfect automated tool within the platform to say here's all the stuff that you that you might not need instead we really said we're gonna we're providing some tips but we also want to hear your ideas as well because because there isn't because I know many of you are already doing this but some of you are just at the very beginning of this journey of trying to keep yourself organized so it's so they just kind of want to reinforce that point absolutely absolutely all right let's roll up our sleeves and talk about the first thing that we need to talk about only migrate what you need always look at regardless of migration always look at what's not being used there are always opportunities and candidates for removal and that this is just going to help keep everything clean and simple so what I'm about to share with you are the things that I did here at service now um I used a combination of of reports um scheduled reports and stuff that I got sent to me that helped me kind of stay on track and kind of top of everything as Dan said we don't have um a tool like that for you because it's it's Unique to every situation and so it would be hard for us to come up with something like that but we can definitely tell you we've been in your shoes and here are some tips and tricks that we have so the first thing that was important to me was managing my indicator sources I wanted to make sure that my teams my my power users weren't replicating queries that were hitting the system that were exactly the same so I just had a simple report that showed me what was being created that was new to review to review it and make sure that there weren't any um replication of queries and also now before I gave anyone access to actually leverage performance analytics they had to pass like a test that' go onto a seprod and develop um a dashboard or Widgets or queries or whatever it is that they needed to do to show that they knew how to do it and that they understood the structure of the data and how to write a proper query however things slip to the cracks uh sometimes things happen and we miss it so this is also a great way to monitor whether or not you have any queries that are kind of taken off or doing something that they shouldn't be doing um things that it kind of helps you just kind of monitor what's going on in your house that you can um interfere immediately and make sure that things get corrected if needed another thing that I like to look at was automated indicators with no job so if they weren't on a job or if they didn't have a source now this was several years ago you could create an indicator uh sort uh indicator and you didn't have to associate a source with it I don't know if um I haven't done it in a while so it's probably not something that you can do anymore but you can definitely create indicators and then forget to put them on a job or or create a different one or have several people creating them and um just kind of miss that that they didn't actually get picked up and used and so this is a great report to look at what you have sitting around out there and um if there's stuff kind of floating that's a good way to describe it floating around out there with no purpose and these are good things for you to look at and review um maybe there's reasons maybe they're creating them in succession to get ready for something that they're going to create or maybe it's just something that got missed and overlooked but these are always great things to look for and remove were applicable um and then formula indicators where the automated indicator is not in a job right so obviously all formula indicators are created uh using different automated indicators to come up with your math equation there and so we want to look at that as well make sure that we don't have anything floating obviously in active dashboards I will tell you there are are some good use cases for inactive dashboards um we used to have everyone who was a developer of uh dashboard had one inactive dashboard that they used um once they did all their work in their sub pra they would use like as a staging dashboard so there are some use cases to have an inactive dashboard or maybe I'm building it right now um it's not going to be ready for actual consumption because I've got a bunch of widgets and stuff I need to place and I've got you know visualiz uh you know like design things that I need to work out I want to put you know content block hair there or whatever so if that's the case there's always good use cases but there's also a lot of stuff that just gets created forgotten about um overlooked so this is a great one to look at as well is how many dashboards do I have there out there where active um is false and is there a reason for these should I have this many you'd be surprised when maybe not but I was surprised how frequently that grew because I thought oh there's only so many inactive dashboards that I've I've got you know control over I didn't realize how many other ones would pop up hey T as you're talking about dashboards we did have a question come in and we may need some context I think I may understand it but it says if dashboard is not being used how to check how many users are using dashboard so I I if I'm understanding this maybe if a dashboard is not being used meaning somebody doesn't want somebody using it but users are still using it I think how can you tell I think how can you how can you tell other than marking it inactive I believe or saying is how can you tell and by and uh Agata you can come off you can come off mute if you'd like to clarify that for us but I think that's what you're asking U yeah and I would look to um Olga or Mara to answer the question hello am I audible yep we can hear you yep okay so that's that's exactly exactly my question uh so for example I'm maintaining couple of dashboards and I'm simply curious if it's being utilized because as far as I know I can I can check uh how many times reports is being used but it can be uh published on multiple dashboards so um currently I don't know on which dashboard it is uh for example if if report is being used where you so you'd see it in report view if it oh that's from my homepage um where I look for dashboards is uh insist CIS UI Navigator history I believe is the table we have a Blog on it that we'll to track down but um if you really have a question there's there's a Blog on how you can query csui nav Navigator history to get get who the the number of view counts in there um you need to be admin to see it to see it's in there but particularly if we're doing this um if I'm going through the migration I'm probably gonna ex get a clone get admin on that clone and I can query that and you can summarize it um the blog we have talks about running a job to go through it because it can be a pretty big history uh but it would give you at least recent history of people who are accessing the dashboards it's not a click away but it's it's there from Vancouver we have also added as you mentioned there are the report statistics and the PA widgets statistics from Vancouver we have also added the dashboard statistics so you can see um how many executions the dashboards and from which users uh you add the like they have viewed that the dashboards so then um to to have this information without without admin I will have to wait until upgrade but that's that's that's that's Improvement so yeah because there isn't a perfect yeah because there isn't a perfect tool today to do pre pre Vancouver so Adam's discussion about you know looking at basically it's looking at the the the history of you each the individual users and you can you can pull out the dashboards you can run a report or a more inl a an create an indicator based on it that will it requires a script just to be to be up front about that one the the old way requires a script to parse it out but there's a Blog that I'll show you how to do it yeah it's not yeah it's not it's not simple but it's not it's not as St not a one click but it's not something that but it's something that is absolutely doable and the effort is the effort is worth it can we post that blog in our uh chat please one yeah yeah yeah we'll get it there just to before we're done that's good so thank you got okay I got that um anything else Thomas okay so uh moving on I was muted sorry no we're good that's okay so moving on uh orphaned widgets right so what that means is someone went in and was like oh I'm going to put this indicator on a widget um well you know as you know you can't see the widget unless it's on a dashboard or some sort of canvas for you to view um so they become orphaned and and I know I'm guilty of that because I'd be like Oh I'm going to create this one get sidetracked walk away and then be like oh I changed my mind I wanted to be a bar chart instead of whatever else I was working on and so I'll I know I have done that in the past and so any widgets that are not on a dashboard are considered unused and therefore those are great candidates for removal um let's talk about reports on system tables we do heavily frown upon that now we understand that there's always circumstances where you will have to do that but in in most cases you want to be keeping a close eye on that you don't want anything that's going to cause a Major Performance issue and when we report on system tables um that can be the case so you definitely want to have some sort of report in your queue that allows you to monitor whether or not these are actually being created and and something for you to definitely consider before migration as as a candidate for removal if it's not absolutely critical I'm gonna add I'll say I'll add this reports there's a few tables um subscription management some of the tables start with CIS um and they allow reporting on it so uh ATF stuff if I want to report on that it's often starts with CIS and there's another one that I'm thinking oh some of the um gen stuff report starts in CIS they're not all bad we want to be really cognizant of reporting on CIS email CIS AIT stuff that's that can be massive so this is not they're not all bad but you need to know what they are that's the the big thing here and I think it's true with a lot of these things they're not all bad but you want to be aware and so we want to make sure we show that awareness I'm going to throw a link in there too the about the the there's a doc article that actually talk actually mentions the various the specific system tables that are very bad and we'll add this to our one of the things we're to talk about at the end is where we're going to be gathering resources for all of this so uh we'll we'll make sure it's in there too but I'm put it in the chat here right now awesome thank you um reports that have not been shared with any roles we call these single use reports um they can become overwhelming and daunting um not that you want to prevent folks from creating reports to do trouble shooting or whatever it is that they need them for but generally if they're not on a dashboard they're not on a schedule um they can fall victim to becoming single use black hole reports right so it's something to keep an eye on um a good a good way to do that is just you know write a report and look at that and see how many reports haven't been shared generally that means it's not on a dashboard it's not being shared with anyone else and keep an eye on that look at it if it's growing if there's folks that you can re reach out to you can combine that with reports the next one reports not run for three months obviously if they're not looking at it for three months Mon and it's not on a quarterly scheduled Cadence it's a candidate for removal so these are just great ways to look at combinations of different things maybe three months is too long maybe you you don't want stuff that's been sitting around for a I mean these are all things that are in your control and there are all different ways for you to really kind of stay on top of the little things that slip through the cracks these are some of the tips that we had does anyone have something on here that I haven't mentioned as a a candidate for removal we would love love to hear from you what are your ideas not just ours I know there's a few of you folks on here that have been using our stuff for a long time so anything that we overlooked maybe or something that you figured out that would be a great tip to share with everybody else we might have to be that old teacher that just calls on no we wouldn't do that Philip tishberg there we go can you take him off mute yep yep he's ready it's here hey how's it going guys um one thing I noticed that seems to get clogged up a lot in a lot of organizations either don't have the connectivity or don't monitor CIS user table lots of users that are no longer in the organization or oh yes right yes and that tends if you can get away you know you get a latest update from either workday or take your ldap and filter it and you can figure out who's active who's not active that tends to be a table that fils up a lot you are absolutely correct in that I'm going to add that report um stat to this before we share it out because we definitely want to be looking at any reports that have been created by somebody who's inactive no longer here at the company whatever um those are things that we actually had talked about um a while ago and I think it just missed it just fell off of our radar so that is thank you but be careful that's that's an information point if the report's not owned by somebody but it could be what you need to do is get it assigned to a new owner right doesn't doesn't mean I'm just saying I'm not I'm not speaking from personal experience but if I were make sure you don't just delete things that are run because some of that those things have been run you know a thousand times a day but it's a great piece of information um to to go hey if this is run a 100 times a day maybe we should have an owner who still works here yeah well we had talked about Adam too like if they change teams and they're you know looking at kind of like who's created what Within this this you know we were we were trying to figure that out right how who has these roles and is this created by somebody that's not in this role anymore and should it be moved and so there's I mean there's a bunch of different ways to kind of dig into the details but definitely at least staying on top of having active users owning uh your data out there is is critical right you can and like like we talked about combining it if you combine it with you know inactive user hasn't been run in three months or hasn't been run in two months or whatever you're your thing is um those are good ways of you know combining your queries to make sure that you hone in on where you need to have a conversation before you just delete stuff thank you Phil yep yep I'll unmute her yep J you should be able to talk y can you guys hear me yep y so um this one's kind of a specific use case but it's something we ran into while we're were trying to clean up um last year is um we have a lot of in we have so many so many indicators um automated inators we're trying they're they're still on jobs which is the really not good things because they're you know impacting our performance because we're running on jobs for things that are really not being used anymore so we're trying to clean it up what whatever's indicators are not um attached to widgets not attached to to um dashboards and things like that but we were able to kind of find connections to be able to do that but where we kind of reached a blocker is um we realized some automated indicators look like they weren't you know attached any Widgets or dashboards but that's because they're attached to um formula indicators which are then on um widgets and dashboards so we kind of had to stop um retiring ing things so that we weren't impacting that I thought and it and this is um when I don't know how to say this if an indicator is not on a job then it shouldn't be I thought if it was in a formula it would show up as part of that job no they are on jobs so that's our issue we have we have things that are run on jobs that are really not being used on Widgets or um but that's because the formula indicator is the one that's on the widget yeah right so you definitely have to be careful with that um this way we started with just automated indicators that aren't on a job for sure so the the data that's there if you go to a formula indicator today this wasn't there this was added a few releases ago but um it wasn't there in the beginning uh but if you go into a formula you can see the contributing indicators which I actually don't recall if it goes through all the levels or not um but there if you look at how we do that related list um you can see how to how to process that but you can look for that the data is all in there and it's with a formula it can be recursive there's no level there's no limit to the recursion or limit to the levels uh but you it is absolutely a gacha that you have to look for about those indicators but if you have the lists of indicators you can then run that through the contributing indicators to make sure they're not contributing somewhere um so you can you can go through it to go it's not in AIT and it's not contributing now now it's one we can get rid of okay thanks yeah that's helpful um because before we really couldn't really see that relationship other than the dependency um free functionality but that one kind of just goes like indicator by indicator which is not great yeah you definitely want ones that are not contributing and not in a widget okay but in a job right and P we did have some some ideas that came came in so I just kind of just read those off real quick so yeah let's hear it one there is a PA Diagnostics job you can run that can catch indicators in Formula so that's another way of knowing that um let's see reports owned by inactive user we kind of talked about that a little bit and using launch dependency usage but would be helpful to have um report so there that is available as well and then let's see reports with old inactive report sources that's a really really good one um and that's really comes down uh report sources for me from a management perspective like are you using report sources have they been updated are you looking at them uh is the is the date in them stale things like that so that's another great one um let me see that that may be it a lot of the other comments I think that they're um talking about maybe another comment but uh Drew had one it says would be nice to see indicators that are pulling the same indicator Source in same additional conditions so are there duplicates out there right is it is it why are duplicates things of that nature yeah so that's what the first um what we'll do is we'll we'll look at some of the queries that we have put together but like the indicator Source manage it bullet here is kind of it was a kind of a a way to report on what's been created to see whether or not there were duplicates um it is hard to do it though I will be honest with you if someone created something um new and it was one of the the prior one was created you know a year ago you know then it then that becomes a little bit clunky I was trying to do something that kind of give me visibility onto the new stuff that was being created assuming that I knew everything that was out there already but I can understand that could be a little bit of a challenge if you aren't aware of everything that's out there or something that's that's Legacy and so yeah we' have to think a little bit more about that but that first one was kind of trying to hit that trying to keep it kind of keep control of what new things are being created you know simple things like you know stuff from the incident table that was created you know on today like whatever like those were easy ones to catch but some of them uh maybe specific ones would be harder I agree with you anyone have any ideas on how to address that oh when I say anyone I mean Adam Stout just so you know sorry I was creating a short link I was finding the dashboard usage one uh I'd write a script for that okay so and that's where me and Adam go different directions so yeah unfortunately there are situations where we we you will have to write a script um to kind of get on stay on top of this stuff consistently uh and I want to throw out here too and we talked about the dashboard usage which I'll put the link in in just a sec the script in here a lot of what we're a lot of what we see the advantages once we migrate to the platform analytics experience is that we've put it built in a lot more reporting a lot more telemet a lot more everything to help manage all these things management is now uh is not an afterthought it's it's something we think about as everything that rolls out so we do need to get over these hurdles uh and and we're talking about this through migration but life is better for us in 24 and in 25 and going forward a lot of these things where um we're just going to prevent you from being able to do it right or give you visibility into it but not have all of these uh pieces out there that may or may not be causing us issues so a lot more visibility and unified you you'll see in some issues we have today we have it's different for widgets than it is for reports it's different for homepages than it is for dashboards as we bring all these things together it just makes life will be much easier once we get into the new world right and we will have new ideas for you on how to make sure you stay on top of this you know further down the road getting lots of so yeah we're also getting lots of additional good ideas in various chats here too so uh so let make sure we capture all that so we can add it we um we just had a couple a couple highlighted kind of reiterating on tips for finding duplicates um there are ways to look at breakdown Source conditions and review them using a report to help you know make sure you're looking at your breakdown sources same thing we just talked about with indicator Source management um as if you're looking at it frequently you can kind of catch things that are new and being created but you may need a script to get stuff that might match something that was created you know six months to a year ago and then obviously reports with the same table and conditions um these are kind of some of the things that stand out to us on how to try to catch duplicates um but if anyone has any additional ideas um that we missed on catching duplicates we'd love to hear from you I would just even think about one thing I'm just thinking about here now too is looking at it from the opposite persp itive what are reports that are named the same but don't have the same conditions don't have the same table or those might be good to clean up as well and they the same type right so I I use the same report name but one's a pivot and one's a list that's fine but if I have the same pivot chart with the same name on the same conditions on the same table and I have six of them yeah yeah that's a great uh a great thing to look at and it does come back to these are things to review right so and and as especially as we start uh mashing these things together then we can find things that are pretty safe to to Archive delete whatever whatever we want to use deactivate group them into put them in a in a penalty box yeah exactly our recommendation is to inactivate wait and hear if you hear any complaints give yourself a time period at whatever your patience level is right and then delete so we you and and that's something that we actually did he service now was like well just inactivate it and see who complains right because some stuff does get forgotten and so um we do that like dashboards we change we would remove all the sharing um and uh remove all the sharing maybe change the owner to a sis admin or something where we basically take it away but something that was very easy to undo yes um and and as Tara mentioned before it's things like report inactive users information inactive users who own reports that haven't been run in six months yeah just go ahead and anything ah hits that let's just archive right archive delete whatever whatever you want to do you can export all the um uh CIS XML stuff if you want but there are things that if it's on you know three of my three of my naughty lists I might just go ahead and take care of it exactly yeah I just want just add I I had a couple of the questions I think I can knock out here fairly quickly because they're based upon things we've just been talking about about okay um so one of them was the our reports on the CIS user table are concern and I think we just talked about that that really CIS user is generally not a concern u a report that's directly on that table um but it's you know that know there isn't it depends if you've got 200,000 users um even that's not a terrible issue but you want to probably want to make sure that your that your report conditions are on like use indexed fields and things of that sort um that you know there we have we have a uh a whole other session just talking about report tuning that will that can help with that as well another question was about the guidance on system tables for indicators um so instead of running reports against the table directly the idea is so so should I set could I you know does it apply to I'm going to say indicator sources should okay if it's not okay to do for some system tables it's not all right to do reports against them what about indicator sources generally the same would apply I would avoid wanting to run them on on some of the on some of the particularly naughty system tables um that are in the uh the doc article that I referenced but uh but in general Leo that's a yeah I think it's a good idea to stay away from using system tables in your indicator source uh assuming they're on that the list of the six or seven and and the the um the system tables just as we talk about that there is a out of the box there's a property that says don't allow uh sorry that blocks everything that starts with CIS uncore then there's an allow list there's a property with allow list if it's on the allow list just it's on the allow list it's fine CIS user on that it's fine you're going to have to do it uh CIS audit is not on that CIS email is not on that um but I find myself adding lots of tables to that because I want to report operationally on um I want to write my own reports or indicators on um ATF on subscription Management on U flow flows on AI usage and you're going to add tables on there it's okay it's okay I the the blocking all cyst tables there's a lot in that are cyst tables now where it's very legitimate to report on there um so be aware but don't be afraid um and understand if you're reporting on CIS audit yeah performance is not going to be good right and that's why it is blocked but don't be afraid if you need it and it's working well it's fine you don't need to ask my permission but just be very aware of those things you can also report if you report on task you can also get bad performance if you you know don't use any index fields and you have 20 million active tasks it could be bad there too but we're just trying to make sure we're poting in the right Direction and we're aware of what we're doing and we're we're doing it the most effective way all right sorry so box stepping down from no no no no that we always we always welcome you in your soapbox and yeah and more great ideas in the in the chats here too so again we're going to be capturing all of those include and including those in the summaries so things like we really appreciate that yeah things like breakdowns with no tables mapped fa yeah yeah that we didn't even think about that one yeah there's stuff that we didn't even think about that you guys have already thought about that that's why it's a let say we're crowd sourcing we're definitely looking to CR you know this is and we'll talk more about that in a few minutes too about so how we want to a little I won't say formally crowd Source but have a little bit more organized crowd sourcing we're GNA try to try to work through with this uh so good okay all right now we are going to quickly talk about organization organization so these are some things that kind of came from rolling up our sleeves and being part of your side of the fence um definitely not things that you have to adhere to these are just recommendations that we found made things easier for us on this side um naming conventions I was specifically a big stickler on naming conventions as well as using grouping it's kind of the combination of the two helped me keep an eye on what was going out there when we first started using performance analytics in platform uh many moons ago um I was the only performance uh analytics admin at the time obviously that increased as we continued to grow as we recommend uh for you as well but at the time on my side of the house I was the only one and so it was really important that I kind of had as much control or perceived control as I could possibly get and so I did I did um stress naming conventions I wanted every single indicator that was created to start with a prefix um whether and kind of like in the same concept of grouping right if it was incident related if we were reporting on case if it was um for cessat specifically there's certain things that just kind of had natural groupings in my head in the way that we did and managed our business we had a lot of um operational reporting so stuff that we did per specific products each uh development team had their own dashboard and so I insisted that we prefixed every single indicator so that I could see immediately how many indicators do I have created for instent and you know if everything has the same prefix I could see also what conditions were being applied um and whether or not a group was Associated to it so I could have that double kind of squished in view of my world for that specific category and I could definitely um felt more organized but also could see where there were some maybe replication things happening or teams maybe being a little bit um confused on on how things U might need to go and so it was a really great way to help me feel uh like I had as much control as possible I know that's not actually a thing uh that we ever actually attain as a performance analytics admin but it feels good to feel like you're almost there um same thing with you know like I mentioned grp grouping there's dashboard grouping there's indicator groups all things that are provided within the platform that kind of help you maintain that semblance of control is there something uh those are things that work for me I'd love to hear anything that worked for someone else that didn't fall under this kind of umbrella I just had one other thought on it that for it's kind of borrowing stealing updating from uh and and we'll put we'll have the link for this as well but there was a a there was a knowledge conference presentation on kind of keeping your environment clean um some of so as so one of the ideas that was that was by a customer by the way it was a customer who was going through it um and so it has some great tips and tricks in there a lot some of these are are the same things that they were doing but one of the things in regards to naming conventions I I thought was kind of neat um instead of just maybe removing reports that haven't been run in three months might do something like take the reports that haven't been run in three months and add the word archive to the end of the to the end of the name though the title of the report so then you can run everything that ends in archive now if it hasn't been run now for six months when you get to that point you say okay these these I feel very safe in in uh in actually removing that that sort of thing so that's really really great tip and great way that's I can't take it myself it was it's a great way to use naming conventions though too right to kind of give you that extra extra filter reporting capability um I do want to touch on one thing really quick um and it's because we have enough great people on this conversation to talk about the difference between a published and a shared report and just making sure and thank you Stephen of course I'm uh bowing down right now for thank you for pointing that out because we definitely um want want you to have visibility onto how many reports are actually being published versus being shared and understanding the difference between that and that could be another great uh report to keep in Your Arsenal um of checking things checking on things is how many reports do I have out there that are being published and and what's the use case for the specifically does the end user understand the difference between the two um and those are things you just kind of want to you know on top of so you know what's going on I have I have a rule of thumb for this oh let's hear it never publish anything okay well I was trying not to say that because I don't want to be bossy but okay but to be clear but to be clear publishing means you can see this data without logging in right and reports now the report and the report view ACL is actually going to block a lot of these things uh the use case for publishing was to have a wallmounted display and I can with a or on a portal if I'm logging into a portal I'm not logging in I'm at a portal and I want to see a report of the of the number of incidents in the queue right or the a average weight time or something like that it's probably a better way to do it you maybe you would have to publish that report so public can see it but the the number of use cases I've seen where it should be published versus the number I where it shouldn't have been it rounds to never so be very conscious but it means I can see it particularly something like a pivot report you would see the data and what you need to be really really really focused in on are are the acl's tied so that they can't click on it and then see the data and what I've seen happen is that they they they when somebody published it something didn't work and then they went in and added an ACL to share all my incident data um or or just a little bit too much than that there should be so um it's rare that there's a valid use case to publish because publish means not logged in at all not not shared with everybody share it with snc internal share it with everybody I I don't care but don't publish it um somebody can tell me where there it's in there and I know there are some valid use cases but super few and far between um and so you definitely as a as a um uh report as a admin you should know every one of those that's on there because you don't want to get the call about why is this data exposed right and particularly if somebody added some ACLS um he the wall mounted stuff am I gonna say what am I gonna say about the wall mounted thing Tara Thomas what's my favorite sentence I got a Blog about it I will find it I will get that up there about the wall mounted stuff uh I do a service account is is is what I a service account one that doesn't time out necessarily that needs the password stuff I'll put that in here but public means not logged in not logged in and what data what are you g to tell just anybody so there you go that's my rule don't do it thank you for that I agree with you very much I just I was trying to be nice and say hey really pay attention to this stuff okay you let me be the bad guy all the time I always always I will I always let you fall on that sword all right and I think with that I am going to hand off to Mr Kane yeah and actually I think in this for the sake of time I'm I would like to I think it's more important for us to talk about how we're you how we're planning to gather all these resources because you notice everyone shared a bunch of great ideas here we're sharing some ideas if you're feeling overwhelmed about like uh oh my gosh how am I going to remember all of this we have a plan so and that and then I think I might want to talk about the instant scan stuff at the very end if we have time for those who are familiar who are not familiar with instant scan I would like to briefly inter roduce it to you um but that's uh that's not I think that's less important than our or than our resources so so I think it'll I think that I think that moves over to Thomas then if I if I am oh sorry I was answering answering questions sorry no worries we will jump that for does that sound does that work for you Thomas and we're kind of uh you having meting y yep yep to just talk about this while you're getting prepped Thomas H Drew you mentioned tags H go ahead no go ahead Thomas get your stuff ready um you mentioned tags tags are definitely a great usage for helping categorizing grouping they're kind of wonky with reporting on them so just that's why we kind of mentioned a couple other ways and kind of stayed away from that but definitely leverage those um if if it works for you yeah so so as Dan was saying so and a lot of great conversation a lot of questions and good comments and ideas and all that stuff and we're and we're grabbing all of that stuff directly from uh the chat and the Q&A and and keeping account of that because what we want to do our plan as you can see down there at the bottom we we have created a Blog at this point and and it's empty because we wanted to wait for this to uh this call to happen so we could get great things from you all as customers the ideas of what you're doing every day uh within your instance to make things like this possible uh so what we'll do is we're going to we're going to put a lot of this stuff directly into that community blog and also like I said earlier the questions that we had uh from this and the answers uh will obviously be in the recording but they'll also be the typed ones because there was a lot of questions that are being answered via type we'll make sure that we put those uh on the community vent as well and then these Academy links you know are some of the ones that we've done here lately um the two bottom two I think directly really correlate with what we're trying to do in this particular one the tuning Solutions in performance analytics and the tuning Solutions um for reporting and those are two really good sessions if you were not on them or if you had forgotten about them it'd be a really good idea to revisit those um just to kind of help out your instance uh anyway uh but it it does sort of correlate with this a little bit as well so because if you're able to figure out some tuning Solutions and fix those then obviously that always helps with migration uh as well but uh a lot of the conversations that we have had the past U couple months few months have been around you know moving to uh next experience and what's coming in the future future and things of that so that's really why we wanted to make sure that we put a session together today to talk about that and honestly truth to be known I think we could probably have a part two to this we'll have to figure that out because I think that there's a lot of questions that uh continue to come in and we want to make sure that we um get those answers and then also if people people like coming off mute and want to talk and and express ideas that they have I think it's good as well so maybe we'll look at doing a part two uh here in the future we'll definitely get on the list of things but um we asked attendees today uh ask your user base right so ask your customers I mean or the people that you're working within your organization of different things that you need to be done and then I mean the one that's always the greatest to me is ask community so a lot of the people that are on this call today I I hope all of you are within the community and not only asking qu questions but sharing answers and you know any one of these scenarios there could definitely be a question in the community that has talked about this and giv ideas like Adam referenc in the blog that he created uh some time ago to be able to to use that for whatever you're doing so you know there's a lot of additional resources that are out there and again the big thing is what we're showing here but um I'll make sure all of these obviously you can't click on these links uh because it'll be saved as a PDF but I'll make sure the links to all of these are in the community event and that Community blog that will be one that is actually going to grow uh over time so yeah anything else with that Dan no but there was one other item I wanted to just very briefly because we have a few questions left here too but um Marta I don't know if I'm going to put you on the spot here for a moment but could you talk because there is there there is some tools coming post Mig you know at the time with Washington or that actually you can talk better about that not with Washington but actually a store app later yeah just talk very briefly about what's coming so what's uh these were all great information and feedback what we are thinking about is to have uh some configuration settings in the migration Center that will allow you to specify when you're are doing your migration your full bulk move of your content if you want to um not include some of the content and that could be uh maybe dashboards and reports that have not been viewed or could be uh as you mention even like dashboards and reports that are not shared at all and and uh that the users the only users that have access are actually now like inactive or locked out um so we are trying to gather uh which are the the best kind of filtering uh options for for the migration for to move all your when you're moving all your content to actually have a more cleanup version once you have moved to platform analytics experience so the idea is we'll we're we will be providing you with some stats that you don't have today that's one other big part of that but it's but it's a that's coming what first half of next year I will say more towards second enough but we to you go back to the old Safe Harbor disclaimer yeah all right so did you have one that you want to answer live about tags I was talking talk I'm sorry I was on mute I answered it before I marked it answer live oh okay saying yes tags are always useful there sometimes they can be a challenge to report on but um if they work for you I think that's great I didn't call that out but that's a great in addition to what we've already suggested uh awesome tags the the reporting issue with tags is one visibility so make sure you have those Shar the tag shared with the right group whether it's your dash report admins or it's everybody make sure um you can't dot walk to reporting which is which is a challenge sometimes but if I'm tagging dashboards I'm tagging reports that's okay it's it's actually totally fine so I in what we're talking about I actually really like tags um but just be cautious in other cases it can it's because of the dot walking thing it's more of a challenge you can't do some things but I Pi here like reviewed um you know archive tags can be incredibly useful for what we're doing I um uh hate naming conventions if I have to use a naming convention it's because I failed um as a designer right that being said terara was absolutely right on requiring everybody to do it um I like to add new Fields with choiceless uh tags tags work but I like to add new fields to to do it um but lots of good stuff there um I there was one question a comment that came in that I want to chime in on about the uh system reports so I'm actually a and I'm good with I'm going to open up system reports to everybody I actually want to get rid of the property that blocks it and I want to use the report on ACL so we've done a session on the ACL assessments and if those you've been around went through this exercise or or going to report the property blocks even admins from reporting and it blocks everybody or nobody the report on ACL and somebody can correct me if I have that wrong but the report on ACL will say hey report admins can report on it or I can create a new group which is uh allowed to report on system tables and not just system tables can report on integration Hub or flow designer can report on subscription management can report on ATF I can create those different groups and have ACLS that give those groups a a report on so the property predates everything I mean that's that is a very very very old property about a no system tables except for some that are allowed and some that and some that are allowed that the default is don't allow things but reporter and those ACLS give you the control that you actually want and need whether you know you want it or not you definitely need it and it allows you to give reporting access to the right people sorry I saw another thing about about the repor ACs that came it's always did so uh there are a couple more so the one from um shisher if if I'm saying that correctly um what do we do when people have created same set of reports multiple times just filter by service de agent so if I'm understanding this correctly so it's the same report and they have the filter for assigned to as one specific person and they've just replicated that report over and over uh obviously I don't I don't think that that's a great idea unless it's you know necessary I think that you could definitely put on a filter to that or some sort of breakdown if you had an NPA but I think that's probably a bigger sort of management question of why why are the individual reports needed of that nature but I I don't personally think it's a great IDE when you could utilize interactive filters or things of that sort especially if it's the same type of report I don't know if anybody else wants to add anything to that I do hey what I imagine that I got an opinion on um so one of the things I do uh we put a we put a um a link to a Blog about report use so I um really like report use looking at report use and which reports and which dashboards are used a lot and start looking at the tables they're on because what I'll start doing is going hey we actually have 50 minor variants or or even you know 50 identical reports and they're all coming from the operations team they're all coming from marketing they're all coming from Finance they're all coming from um Amsterdam and go how about we build you a dashboard and then is with Thomas said to go and we'll add a couple interactive filters well person actually a lot of what I see is not the interactive filters it's personalization you know it's my my view of this so I'm going to start looking at all the spread and actually we can consolidate and we can build a better one I don't want my my let's take my Frontline managers my first line managers I don't want them building reports I'm going to let them I don't want them building it I want them spending their time managing so if I can create a a a power user group or a product advisory and go hey we're going to create a dashboard that works for all of the Frontline managers with some interactive filters with the best visualizations that's going to be better if I see lots of variations of the same thing I have a process problem or an organization problem which I want to solve by bringing things together and all of that you know there's lots of stuff we have to do now don't waste your time get on the works spaces and if we get a workspace and I have a my my Frontline workspace I have my analytics together I can let them take action I start integrating that with um with sidebar I have all my AI powered stuff you're going to get an awesome end user experience reports are not our job is not to look at a report it's to get something done so we want to hook in what why am I looking at this data what am I trying to get done and get with that team that has to do that and get that into a Works Space I'm just to let you know I'm using my hands right now and I'm really I'm really selling it with with the hand gestures to bringing this together and I apologize you can't see it have to get like some AI to do that but imagine it's great um but again let's focus on the workspace and getting the analytics in the workspace while they're getting work done we're going to be much better off we're going to have a better end user experience they're going to be more productive they're going to be happier and not spending time creating duplicating dashboards and tweaking okay great thank you Adam um and we are at the top of the hour if we did not get to uh your question please ask that in the community and feel free to tag any one of us but also in two weeks if your question can wait for two weeks we are having uh our last ask the expert uh session of the Year where almost all of the people that are on this call now will be right back on this call again and then uh some additional ones to actually open it up again to any questions that you may have not necessarily around what we talked about today but anything as it relates to platform analytics so again if your question didn't get answered or if you think of more definitely put them in the community if you want to do that and tag any one of us if not we can see you back in two weeks where we'll open up the floor and let you uh ask as many more questions as you would like thank you to all of the presenters and panelists and we'll see everybody in two weeks thank you