foreign this is Daniel Slocum I'm an itam technical practice director at Glide fast today I'm going to show you a video on changes to software asset Management's Reclamation rules in the servicenow Vancouver release I'm going to show you the differences between what has been in the norm for some time in a Tokyo instance and what is new in Vancouver to do that I'm going to look at the servicenow documentation and show you in an instance what the documentation is telling you with words here we are at the servicenow documentation for software Reclamation rules it gives a general overview and identifies what they do and if your software asset admin or someone working with servicenow software Asset Management you understand the basic overview so I'm going to skip that just a moment this note is kind of important the products in the software products related list on a Reclamation rule are based on the content updates in the software Asset Management content service for example if a suite component has been added removed from a sweet parent the change is reflected in the software products related list now why did they say sweet parents and components and that's because in Vancouver it now takes into account sweet components and Suites and it leverages the data coming from the Content Library to do that it also of course does what it used to do and that is if there's a single product it leverages it as a single product and if you create a custom product and you have the the details for a removal in your instance you can still add those as well so let us take a look at what they're trying to say here but first one more thing after a sweet parent is added to a Reclamation rule you can edit or delete sweet components you can also edit or delete the sweet parent if you delete the sweet parent the sweet components are also automatically deleted along with product processes if you edit a sweet parent then changes to the editor reflected for the sweet components example example example so if you change the sweet parent from o365 to Microsoft Word then of course all this week components are going to go away and anything that's related to Microsoft Word if it has sweet components will be added so those are some pretty cool things around sweet components and sweet parents you also have the um the new edition of filter conditions and I'm going to get to that in just a minute but let's take a look at at what this looks like so here in a Vancouver instance I have added just my engine generic Microsoft Office here um underneath it added the software product parent of Microsoft Office and all the basic sub-components sweet components for it I'll get to this filter condition in just a moment I want to show you the difference of what this looks like in Tokyo so here in Tokyo I added office and that's all you have so if you are trying to uninstall the entire Suite you may or may not be successful because the product processes that go into account for Microsoft Office are just these two whereas in Vancouver now you have the product processes for all of the different components and there's 26 of them note it also gives you a warning at the top the Skype for business Microsoft SharePoint workspace schedule plus software products do not have product processes in this content create custom processes here and so you can it takes you right to the place where you can create custom processes and then they will be added to the product processes in the Reclamation rule there is also a difference in the header so if I go back to the out of box Tokyo release you have Microsoft Office installed software last Tuesday because I chose that for the Reclamation type each choose the last use data and then you have you know notify user and if you do the notify user this is conditional it tells you how many days to wait for a user response before it auto reclaims that is the same here in Vancouver however you also now have an assignment group you can choose no activity and you have this software installed condition which we are really accustomed to seeing on a software model record where you begin to in a Reconciliation identify you know which software installations that are impacted so you can do the same here you can adding a software install condition at the Reclamation rule level will allow this to filter out or exclude certain software installations um and that would be maybe for a VIP or for installs that are in a lab where you don't have much usage very often that sort of thing and so this begins to allow you to very systematically identify what you want to keep versus what you want to Auto reclaim additionally the filter that I alluded to in the in the filter conditions here in the instructions on the servicenow docs site identify that you can add a filter condition at the sweet parent level and those would be automatically complied to all this week components and if you um open that parent you can add it from the product list your filter you can see that filter condition I found that that is significantly simpler to do from the office I created one here I simply clicked into it it automatically opened the record and I chose language is English so creating that filter for the sweet parent then applies to all Suite components the sweet components don't reflect those in the UI however if you open one and attempt to add a filter it's grayed out indicating that the parent filter is applying applicable to this sweet component so all in all this Vancouver release for Reclamation rules gets a big uplift that allows you to carefully manage what is impacted by Reclamation rules and you don't accidentally uninstall something and you don't have to have your admins go through the process of identifying wait a minute this is for a VIP or this device that it's attempting to reclaim from when you have a removal candidate record review before you kick off the the Reclamation workflow they can identify these here automatically systematically instead of manually simplifying their job there's one more thing I need to show you before we sign off and that is here under the documentation the notes about upgrading to Vancouver your current Reclamation rules if you are have any in your Utah or below servicenow instances will not automatically take into account Suite components and Suites and so according to the note here you must remove the sweet parent from your Reclamation Rule and re-add it so build into your upgrade process the removal and addition of your sweet parents in your current Reclamation rules and expect that to take a little time [Music] thank you