so the topic for today is how to test deploy an upgrade employee Center I get this question so many times what is the best way to test it should we do it in production should we do it in subplot how do we move employee center from one instance to the other um what what considerations to make that would make sure like you know we are set up for a smoother upgrade how to upgrade and so on so we will try to address all those questions as much as possible in this session today um to introduce myself my name is Puja Gupta I'm a Staff product manager with um with the unified employee experience product team and I'm joined by two of our esteem two of my esteemed colleagues um who are on the engineering team one is Rohan rasani I'm sure you have heard from him before in this session and also Ankit Kumar in addition to these two and and the three of us we have more people from the product team joining in um everywhere from like testing the QA team and engineering team and and just the product team as well so please ask your questions and you're free to go technical if you want to thank you what we will cover today we will cover um how to work with different application Scopes as you are familiar if you have if you have your hands dirty with employee Center there are multiple different application Scopes uh shipped with employee Center and it can be sometimes confusing on how to use them what they are for so we'll try we'll try to give you some context behind it and also share some best practices on how to work with them um and so on the second we'll talk about how to move employee Center changes to production so you're most likely working on subtraud environment and how do you move to production like how do you how do you create update sets um um what can be captured in an update set what cannot be captured how do you work with that so we'll talk about those things as well and then finally we'll talk about how to test employee Center and what are the different options available for it now I do want to say that you know employee Center may be new for a lot of you folks but there are many people on the call um who have been joining these sessions every month so employee Center is fairly fairly familiar for them so we're going to keep steps to migrate from service portal to employee Center out of scope for this conversation how do configure individual widgets out of score so all out of scope all the basics function functionality um is out of scope it please focus on the topic that we have for this session uh while asking your questions but there is a lot of content that we have available so I want to highlight a few of those if you have those questions you know place to go so Community great place for like you know self-serving yourself for like a lot of FAQs implementation guide best practice guidance feature overviews so I highly encourage you to try that you would see links for these coming in your chat as well we have deployment office hours so if you are currently um in the process of deploying employee Center I encourage you to join these office hours these are also monthly um and our next session is going to be on March um and um the difference between these office hours and Academy is that we have a topic in Academy we are kind of um it is discussion but we do have like more sharing from servicenow site office hours we don't bring an agenda it is your time we if you don't have questions we'll we'll like end the meeting it's like that so it's your time to just free flow questions and there is there are no slides that we bring in now if you are thinking about how to set up taxonomy there are multiple resources we're not going to share all of these via chat today um but because there are quite a few of these but you will have access to these slides so all of these links will be available to you I'm just highlighting here that we have a lot of support available if you are just looking for help on how to set up employee Center taxonomy um or thinking about how to migrate from service portal to employee Center um there's there's a ton that's available we also have resources like a now learning course on employee Center Essentials it covers everything from like all the different features related capabilities governance and so on um in our newer release um for the employee Center Essentials course so highly recommend this for for your team who's going to be working on employee Center and then we have um self-implementation resources from our now create um part of the world where you can see a success path there is there are things like uh taxonomy workbook which are extremely helpful so I highly encourage you to use all of these resources to get help now let's let's dive deep into the topic that we have for today um which is like which is the upgrading testing and deploying employee Center and the first one that I want to start off with is working with employee centered application scope now what is an applications code so if you think about just servicenow and and how the instance in is architected um typically an application will be shipped within their own application score and that is true for employee Center as well so if you think about employee Center we have its own applications that are on store each application on the store ships with its own application scope and these application Scopes are important because they they one identify the code associated with that application and then they restrict access to that application files and data for anything else in the system or in the instance to access so it's it's a it's helpful from a security standpoint um you don't want um the data that is in your application or like in anyone in the uh in the instance to be able to make changes into it so um it's an important way to secure and control um what's happening in your instance and if you're making configurations changes in any in anything in that application you typically need to be in that application scope and in the screenshot you can see an example of what that looks like and this if you're working in servicenow platform this must be pretty familiar so what are the Scopes associated with employee Center and I want to like highlight those but also give you some context behind it so if you think about just employee Center standard it is shipped with the employee Center Store app and most of the functionalities that um are associated with employee Center standard whether that is the header whether it is the Mega menu navigation um favorites um popular topics what uh topic Pages all of that are associated with employee Center but if you remember um and if if you know this context employee Center was created out of a pre-existing portal and that portal was called Employee Service Center so we also have a dependent app called employee Center core and you would see this often in your in your instances and you may have to make some changes in that employee Center core if if you are touching anything that is that was considered Legacy so to restate what I'm saying employee Center core was essentially um the Legacy code that we brought in when we were updating the old portal and making it employee Center in an Ideal World if you're just working with setting up employee Center you wouldn't need to make any of the changes in employee Center core and most of your changes would lie on just being plus Center now employee Center is built on the service portal Tech stack and a lot of things that are on the service portal Tech stack available for everyone not just as an employee Center deployment per se are included in things in in the global scope so things like search my request shopping cart these are all these are all service portal Tech stack capabilities which are available for all the portals that you may be creating on on the service portal Tech stack um are all in the global global scope now when we are making new enhancements and new features we are always trying to maintain it in the employee Center side of it to make this easy um and uh um is there anything else yeah so yeah and just to reiterate the Legacy code is an implicit now there are also other applications like employee profile which are ships separately from employee Center and capabilities associated with employee profile will be found in that application if you see employee Center Pro there are additional applications and different Scopes and this is really important like this was really important for us to do because the licensing is associated with these applications so employee Center Pro related capabilities are all part of the employee Center Pro Storer so app launcher organizational chart POS search which is our manager Hub they're all part of the employee Center Pro now employee Center pro has a really strong set of applications as as its dependency and these are all the applications that feed into the employee communication space so content publishing and content experiences are like one of the main ones so content publishing everything that you can see from um like working with style contents working with Banner announcements the video Carousel widget Rich content or microsites um events anything that we have associated with employee communication is typically in the content publishing app and it content publishing is a dependent app for easy Pro so you're not downloading content publishing or content experiences separately you're typically only downloading downloading EC Pro but these are available separately because you could apply them in some other portal as well Nicole um is app launcher same as my applications widget it is the same yes so the back end name for the widget is app launcher the campaign's functionality if you're familiar with it um it's part of the content experiences Twitter application scope so that's that's where um the um the capability associated with campaigns lies then we have additional applications like content governance um let me give you some context because content governance might be relatively new for folks here we have an end-to-end workflow predefined for making Communications requests to the um to the communications team so let's say I'm a user uh and I have and I have some communication that needs to be made on the portal I can use a request from which is predefined by servicenow um to make that request that request will go to the content author who can work on it share it as share it as a task for me to review in the same portal view ad approvers if needed and then you know go directly to like preview the the final content and publish it we have a end-to-end workflow Associated when doing this this whole thing which is typically managed via emails and organizations and that's called content governance so there's a there's a separate app for it um and and all the workflow associated with it is part of that app and there are many other application Scopes that you would see right there is manager Hub there is content analytics so you know um um so I see someone Olivia you're asking about um how to do how to get campaign metrics um I would suggest exploring content analytics functionality so um you can plug in with different systems to run analytics on your campaigns and other communication content on the portal so try it out and happy to take questions in that later so just to add on to what Puja said uh like we had a constant request from our customers where uh customers and their Communications teams saying that okay there are application application requests coming up to them to send Communications but they cannot track it there's no way to approve it there's no way to audit them like why this content was created or who created it and who approved it so content governance uh save serves that purpose and there are more features that we are adding in the August 3D so uh yeah we'll keep you posted on that thanks Rohan now now we spoke about everything one particular module that I want to go deeper into and that's the content uh taxonomy module now it is among the few capabilities um within um within let me see so this is this is the one let's try to can I yeah so this one so it is among the few capabilities that we have um kind of aligned with the family release on that could fill life in global scope and is associated with family release so in um um just want to let you know that so if you are updating you would often see that you know there are dependencies associated with the family release if if there are changes made in the content taxonomy and as you're familiar we do ship an out of box taxonomy that is the employee taxonomy over here this is part of an employee experience taxonomy scope so if you're making changes to the out of box taxonomy you would see that you know you are updating the employee experience taxonomy score now here's what we recommend if you are um if you are just playing around with your uh employee Center you're trying to get the feel of it and you're just trying to set it up for like a demo for your stakeholders use the Autobox taxonomy make some minor changes that you need them if you are actually setting up your own taxonomy you should clone the out-of-box taxonomy and make changes to that cloned version of the outer box takes family and of course the Clone that you will create whatever scope that you create the Clone in that's what scope it will lie in so if you create it in the global scope then that's where it is if you create it in the employee Center scope that's where it will be and the content mapping that is associated within the topic it's not it's not in any scope because it is not associated with any application table or sus meta table and we'll expand on that a little bit so to recap the content taxonomy is is family it's a global scope the out-of-box taxonomy is in a separate app is something that you should only be using if you are doing a demo um and you should create a cloned version of it and make changes um to that clone version in the scope that you want to work with let's talk about best practices so of course you should be working in subprod environment as much as possible um with with especially if you are in a new deployment um you could potentially work in product and we in in production and we have seen many organizations do that um it's it's it's not it's not going to harm anything because ultimately it's a new portal that that you have not shared the link with uh with anyone else so if it's a brand new implementation or if it's like you have only service portal deployed so you have slash SP and no ESC you could be working in prod environment as well foreign changes we recommend that you make all of those in the existing scope you don't need to work with a custom scope to do these configuration changes and I often get this question um configurations are not customized the configuration in the sense like you know um um you want to Define um quicklings uh to be quick you are adding quick links to the quick links widget um you are um making any changes in terms of like you know what kind of task details are I've made available on the my tasks page these are all configuration related changes um and and you don't need to work in a custom scope for that and if you're making any customization in a widget you should always clone the widget and make your customizations in in that widget in that cloned version of that widget and this this kind of helps with smoother upgrade and like I said you like when you create your own taxonomy topics you should be like cloning it and create we typically say you can just work out of the global scope it makes it easy we have a demo shortly in a few minutes where Ankit will show how you can like you know separate um separate the chain the small change that you have made and create a separate update set so you don't have to update the whole scope there are things like that that you could also explore but you don't need to create a custom score is what I'm saying now let's talk about moving from subprod to prod you you need update sets to be able to move from subpro to fraud and and I'm pretty sure like people here are familiar um what that is but just to set some context it's a set of configuration changes that are captured in the form of an XML file that you basically extract from and one place and you import it in in um in a different instance um anything that that is assist metadata table so basically you know configurations that you are making and is it and those configurations have been fed in an application table those are captured as an update set automatically in service now so these are like I said changes like the task configuration or to those configurations the variables and the variable choices that you're making all of that will automatically get captured as an update set when you're going to do but the um the the simple data or data associations that you're making um they they're not considered this meta table assess metadata so those are not captured um as part of an updates and then you have to manually fetch them and I'll and we I will highlight just in a few minutes how to do that a perfect example of what this is is all your taxonomy associations so your topics uh will be captured but if you if you are um so your topics are captured in the update set because they are associated um as a they are available as this meta table but your content mapping is not captured and the way you do that is essentially if you go to your connected content you right click on on the top on the top menu and there's an export button that you will get over here and you just say export and XML and when you go in your actual instance you say import XML and all the content mapping will be imported from the sub product environment to problem now let me let me pause here and tell you one thing many organizations choose to build their taxonomy structure in production so it's not unusual to do that and there are two reasons for it one um um one is typically like especially in organizations who are not extremely mature in in managing their subprod environments the data that sits in the support environment is going to be different from prod environment so um what the mapping that you do in subcloud environment um might not be valid in the in the broad environment um secondly even if you do it in the subtraud environment you will um you will have to make sure you do the mapping almost again in prod because they will almost always be a few more additional content or different things that you will have to validate okay now here's the process I'm not going to go to super deep in it because Ankit is going to just highlight how we capture the update sets and you know what are the different options that you can work with but you love the slide so you can review it later we wanna just share your screen [Music] raised hand for a better I don't know I don't see that anymore but I think he had that yeah I see a couple of raised hands um um let's just do the demo and then we can take the questions yeah uh Jen and Olivia uh we'll get back to you I'll get over to you yep thank you Pooja uh let me share my screen hello everyone good morning good afternoon and good evening I hope you guys are able to see my screen so uh the agenda of this demo is I would be basically showing how to create the update sets in the employee Center how we would be tracking the customizations inside that let me log in yeah the first app which we usually recommend is to create the local update Set uh to track the customizations so I am going to do that now so before creating uh the local update Set uh we should be firstly changing the application scope so I'm just changing the application scope to employee Center after doing that uh we can create the new update set in employee Center scope to track my changes so once we will do that this track changes would be my current scope and whatever changes I would be doing in employee Center scope it would start tracking those so for an example I'm taking an example of quick link widget so for going that way I'm just moving to the widgets so once you will navigate to the quick links uh basically you can go and do whatever changes we want to do we want to do a CSS changes or we want to add some uh server script code changes for now I am just adding the comment over here to track my changes oh okay I think uh this is yeah so once we will move over there we can add like suppose I want to uh override one of my API or I if I want to do some changes for now I'm just adding the comment say over here to track my changes so once we will do that and save it it will start tracking my changes and if you will go to the update sets we will start seeing those changes so whatever changes I am doing so after completing those changes I can move my update set to the complete state and save it and then we can export that XML for that update set after exporting it we can re-import into our prod instances uh and if suppose we want to uh close basically clone a widget itself I am showing the second thing now I'm creating a new update set for tracking my cloning of the widget and uh the changes which I am I would be doing in clone of my widget oh yeah now we can navigate to the widgets we can take an example of this widget we can clone this widget so once we clone the widget uh this would be automatically created in the employee Center scope and after saving it it would again start showing into my update set so after cloning this widget I can do uh my CSS changes or my server script changes whatever changes is required so after completing that we can again navigate to the local update sets and if you will see this we can see that our custom copy of actions widget is already present there again we can follow the same process we can mark that as complete save and then I can export this update set my system and then I can move these update set from my subplot to prod yeah this is what I have to uh show the update sets do you want to take over yep thanks Ankit um I'm getting a lot of question like this is this was very helpful um and I hope um everyone else also feels the same but I'm getting some questions I'm seeing some questions on the Q a panel related to why we are following this approach uh for cognitive taxonomy um for migrating updates to content taxonomy and I want to reiterate um it's just in the the way the platform functions and Rowan please add to that explanation connected content is not us captured as CIS meta table and only this is meta table gets into the update set so you have to do a manual fetch of this um this information if you want to move from that's correct yep there are few other things because it's a legacy thing it's already a table and that is more at the global scope rather than the employee Center so uh at this point we don't plan to make it as a metadata kind of a table where once we do that we could create an updates and track it and also that's the reason we uh are saying that create a record export them as XML and then import it hope that answers thanks Ron hope that helps um let me see there were a few hundreds Jenny um I have allowed you to talk Could you um go off mute and ask a question Dave I see your hand raise I've allowed you to um talk as well so you can ask a question okay it seems we have some issues in having people unmute um but please please put your questions on Q a and let's keep moving ahead and and we'll I'll I think we'll have time for like more questions in the end so um we can do a little bit more of live engagement at that time so let's talk about how to test employee Center um there are multiple different types of testing that you can do so the first one that you should of course have like first best practice that you of course need to think about is um recruiting a representative sample of test users so yeah is that Dave yes oh somehow I got unmuted sorry about that no worries go ahead uh I had a question around that content uh exporting uh content to a taxonomy so I know for example in taxonomy Canada for example it HR whatever for example I.T we would add at a bunch of uh subcategories and we add connected contents for example catalog items or knowledge bases and those connected contents come in come from different Scopes again so when we import update set actually or uh actors like contents from different scope how do we handle that one and second when for example one of the knowledge base is retired or no longer is there a way we can automatically think that it does not show up in employee Center because I had the situation that when you add the import the content from uh to a taxonomy and that content or for example uh color item or knowledge base is no longer available but it's still done a related list new record in the connected contact exists in in Placer Center um Rohan add to it but I'll try my best to answer both these questions first I think um when you were exporting as in in an XML format over here um the it's just a mapping of where the content sits um and what it is mapped to um so even if the content is sitting in different Scopes it would still be captured in the XML file um that's my understanding and Rohan is that is that correct yes that's right okay awesome and for your second part um could you help me understand um when you had this knowledge base that had retired did the content just show up as a connected content on topic or did that content also show up on the on the user side of the topic Pages it does not show up on the user side but it still shows up on under connected content because once it's retired people won't be able to see however we we still can see that record under connected content okay and that is by Design so are you saying that you don't want to see um or you want some sort of indication that this is retired and connected yes for example if I move that specific knowledge article from one category to another but under it still actually shows up under unless you manually remove it from that specific item so it does not automatically switch when you move to one to another okay okay I don't know if we do that I'm gonna take it and it I can investigate into it right that's I was hoping if it was can I get being fixed but uh thanks for the answer thanks Dave um in the interest of time I am going to go ahead and finish the content on testing and we can go back to the questions thank you Dave for like participating in the live engagement I always love that um so yeah so the first best practice was that you should always have a sample set of test users identified um not at the very end of your deployment from the very beginning of your department because ultimately you want to do different kinds of tests and one of the first test cases that we recommend um from a design standpoint is to do usability testing and usability testing is different from user acceptance testing usability testing is more about just observing what people are doing how they are using is um is the platform intuitive enough or is the portal excuse me intuitive enough for them to do what they want to do that's what you are kind of inherently testing with the usability testing and we have some details on how to conduct this and this is like expertise expert guidance from our own design team which is in the link over here um and we can share it on chat as well um the second testing is more around user acceptance things and I know like almost everybody does that um once you have completed you have deployed you would want to have demo users at least five to six members of Like Aquarius Rose and essentially you are testing different scenarios and use cases that you have deployed um um a must-do step both on the subplot side as well as on the product production side now I want to highlight one more thing which is in the last point over here um servicenow has automated testing framework and and there are um there are some quick start tests that are shift or employee Center as part of it so I highly recommend you to try those and it will help you at least test all the basic functionality that should be working um for a good experience or an employee Center and then anything that you have customized or custom use cases that you have who you would need to add on to these quick start tests so um some rules that I'm highlighting start thinking about your test users from the very beginning because it's not about just user acceptance testing it is also about usability testing so you want people from different personas partnering with you from the very beginning of your deployment um when it comes to testing the taxonomy structure a lot of people have asked me like you know we want to we want to evolve the taxonomy and like we don't want it to be stay taken how do we do that in the system uh in in the platform the answer is you don't test the taxonomy structure in the platform if you are testing the taxonomy structure in the platform there are a lot of different design elements that are going to um dilute or like you know impact or your results of the study you want to do a separate um test which is basically just focus on your taxonomy structure um and the one that we recommend is basically doing a tree test um we have heard from customers who um who sort of do a card sorting exercise to to get to a taxonomy structure that makes sense once you do that car sorting exercise your next step is to do a tree step and you know uh the three test is essentially validating that you know people are able to get to the right content um following the tree structure that you have created for them and there are a lot of tools that are available for it muiq tree Jag are among those it's it's not very time consuming it's like 15 minutes per participant um and and the more number of participants you engage or more diverse number of participants you engage the better it is um and there are some instructions on this on this slide both the card sorting and three test exercises are heavily used within service now when we are guiding customers um at the same time when we are deploying or building our own our own box taxonomy for employee Center so uh important to have this in your planning especially if you are modifying your taxonomy structure if you have fun that is already working and you are looking to um you know completely redo it um how do I test employee Center in production before go live and and we'll talk about all the different scenarios here um but I do see a question around a b testing Rohan you want to take that one I'm just going through the questions okay let me let me read it out um yes there's a way to roll out employee Center Pro in a staggered approach um like can we do random a b testing um and so on yeah so I think uh the next slide should cover that but uh to give a sneak peek I think you can create pages and Target it to a pilot audience to start with and then go on adding audience to that role you'll see more of that in the next slide okay yeah no absolutely and I'll we'll talk about it but I do want to highlight one thing about a staggered approach there there are different things that people are thinking you you cannot limit the portal per se completely like anyone who has um the link to the portal and has access to it will be able to get into it you can't have limited access um defined for the portal then and it's very hard to do a pure a b testing which would say if you are user a you get into um this experience versus if you're a user B you get into the other experience you cannot do that um if you are migrating from a different portal or if you are implementing service center for the first time what you could potentially do is identify a set of early adopters and give them um give them the new link you could also if there is a way to like divert um um or like divert the URL um if that is what is it called I think that's what it is called so when they log into the portal they are redirected to employed Center portal uh that is possible if you are in these two scenarios because it's ultimately a completely new URL but if you are upgrading from employees service center which is our old portal to employee Center Pro both these portals are slash ESC so it's not that simple to do what you could do in terms of you know uh defining early adopters so what Rohan is talking about is that you know what you can potentially do in this scenario is work out of a service portal page that is not currently linked with your user facing experience and you can limit access to just that page with your early adopters or test users you want to make sure that you're rendering that page to employee Center and share that URL with with your test users and here are the steps for it so um we say clone the employee Center Page let's say you are you are updating the EC Pro dashboard which is the employee Center Pro home page you make changes in the cloud version of it you can Define roles so if you would see the screenshot over here so you can Define rules to um to say this these are the people who it is used for so like you know Rohan has it defined as EC pilot users so you could say here are the pilot users that I want to test the new experience with make this page available only for those and then when you are rendering it on employee Center that's an option that you get um so like um you you can you get a new URL which is over here and you can see that you know it is a pilot um it has it has the ID associated with your page and once you have tested once you're good you can make this page the default page for all your users so this is not like an automatic nav like redirect for the uh users but uh um it's it's a workaround that you could use to sort of test your design while you have a a portal um in in production live and in use does this make sense any any questions in this sorry feel free to go raise your hand if you have additional questions on on this approach okay that's all I had in terms of content but we can take some more questions and go from there um let's see so David is asking on KB categories in service catalog categories explicitly unconnected to the taxonomy by Design so yes David they're not directly connected but when you are defining your taxonomy what you're essentially doing is um mapping the content in those categories to the taxonomy so yes the categories is is not connected to the taxonomy the content is by Design and what you are extracting in the XML is the mapping to the content not the categories as issues are found in testing the efficacy of the taxonomy how do we resolve them for example if a Netherland employees keep using U.S benefits result which does not um keep saying okay so um that's a good question I think if when you are doing a tree test there are two parts of your question so if you are doing a three test you would want to evolve like as you are saying something is not um is people are not able to reach a particular topic that there should be reaching you would want to try different combinations and see um which one works better you could also like redo the card sorting and see if there are some gaps from that one point but the example that you are highlighting which says like needle and employees keep seeing the U.S benefit results I think the root cause for that could be something else um ideally your needle and employees should not be able to even see the U.S benefits results so what that is suggesting to me is that the content that you have Associated for U.S benefits is available for Netherland employees as well which should not be the case so I would say um the the this personalization aspect or like you know the the relevance of the the search results all the content on the portal depends on how well you have defined the restrictions or availability of your content so make sure you are looking for that so to add on uh you could use content publishing to create the content and Target it to a particular audience and then tie that to a taxonomy so that way you can limit who can access what uh so that could be an option if we are using EC Pro foreign yes hi um thank you again for this time you can hear me okay correctly yes okay so what I was just wondering about um so I was looking to get some metrics on campaigns that we've posted and so I installed like the content analytics plugin um in sandbox which was uh directed to me from our servicenow architect on like our itsm side so I put it in I downloaded it in sandbox but then like when I'm trying to actually get metrics for clicks and see if it's actually working um all of the dashboards come back with zero and then also just trying to understand how like the campaign bundles just like the the process and I and I have not been able to find very many um like I haven't really been able to find a course or anything so I was just seeing if there's additional help um or someone could spend time with me um you know in that space I can speak on that cool drive so uh that's a great uh great feedback Olivia we are constantly working to add more troubleshooting uh kind of stuff in the documentation so uh that this feedback helps but if you want someone to take a look at your instance I think the best way would be to create a case uh on the support side that we have and then one of our support persons or our product team can jump on it and see what's happening uh but uh yeah we will try to add more documentation no and best practices are on campaigns for sure okay thank you so I'll put in um I'll put in a case and just provide this detail yeah so that's good thank you and if there is a lot of interest please put on chat we can make one of the future Academy sessions um focus on this as well so that would be amazing but that's just me I'm biased like you know use the chat give us some some thoughts on like whether it's a runoff thing or or you all struggle with content analytics um on campaigns so happy to do a Obsession on that okay um let's see if we have any more questions Karen um you are allowed to talk please go ahead and yeah hello can you hear me yes thank you um I had a question around how much we can um leverage from existing SP portal we are in Sp portal right now and planning to migrate to AC Pro this year so we're trying to figure out how much we can leave us Ace and plan to continuously migrate after the first you know go live trying to figure out what our MVP is so we have questions around how much can we leverage existing pages that we have created in SP and simply connect them to um the mega menu or others in in AC Pro um I honestly the answer is it depends um on like you know what you're trying to migrate is he is employee Center is on the service portal text app so um you can you can use all or none of your customizations or pages from service portal and make them available on employee Center as well so that's that's definitely possible but I would encourage you to think about and you know is as you're thinking about your migration approach um think about what you can use out of box from employee Center and um and also do a comparison of you know here's how we did things in service portal and here's how a newer version of doing that particular use case is on employee Center if that doesn't fulfill only then think about migrating over um the the customizations or Custom Service portal things into employee Center um but here's what I would do this is like a very very quick answer to a very broad topic um I would recommend you to uh I would recommend to watch the migration from service portal to employee centered Academy session um the link for that is in the slides and I would also encourage you to join the employee Center deployment office hours which where we discuss topics like this at stretch thank you and I I think the one that uh the webinar you're mentioning is the one from November 17th yes is it 17 that 17th on way back it's probably 19. there was uh 2017 okay yeah probably that yes I saw it yesterday yeah that was very very helpful um thank you and I am already part of the office hours I appreciate it awesome thanks Karen um all right so let me look at the um chat Rohan Smithy any question that you think we should answer live okay um I'm seeing some requests on like you know where we can improve I I really appreciate um those those feedbacks please please do send them our way and uh um um we're on top of the hour so I'm going to like you know um let everyone go carry on with their day any of the unanswered questions we will also answer in a q a format which will be placed on the event page for this so thank you so much everyone for your participation and and we'll follow up with anyone who who has unanswered questions thank you thank you