[Music] thank you hi everyone welcome to the now platform Utah release features I'm Emily Walker one of our it operations management solution Consultants here at servicenow today I'm going to be talking through one of our new major features within the configuration management database or cmdb using the identification and Reconciliation engine to identify and reconcile Core Business data I'll also be showcasing a quick demonstration of this new major feature within my demo instance so let's jump into it as always here's our Safe Harbor notice just letting you know that this presentation may contain four looking statements that reflect the current beliefs of servicenow and are based on current information available these four looking statements should not be like relied upon in making purchasing decisions years ago servicenow introduced the identification and Reconciliation engine or ire for the cndb the ire really made it possible to control how records were identified thereby preventing duplicates and unmatched records it also made it possible to control which sources were trusted to populate each value in the cmdb including Fields such as model memory or disk space as it has been enhanced and refined since its first introduction it's gotten even better at managing the identity of records from different systems and reconciling all of this Associated data attributes while the ire for the cmdb works well with configuration data Integrations from other critical platform data tables including user location department and cost Centers do not share that same engine to uniquely identify records and reconcile them and this means that data can become corrupt and the effort invested in identifying and reconciling non-cmdb tables is not managed in the same location or with the same methods as the majority of other data Integrations and this is so important because consistent and accurate data feeds healthy business workflows and we don't need to have manual intervention to research discrepancies more rework due to Broken updated processes so with our Utah release servicenow is extending the identification and Reconciliation engine to other business tables to put the management of all critical data under a unified methodology so let's see how we can create a new identifier first let's start by going to our CI identifiers right here under reconciliation the first thing we're going to do is click on new and we're going to be adding a new identifier here we're going to give it a name like location and we're going to pick something other than a cmdb table like location we want to make sure that for any non-cmdb tables that we are creating identifiers for it that we must make sure that we're checking this independent box at this time dependent rules cannot be created for non-cndb tables let's click submit and we will go back into our new location identifier that we just created so coming down here into our identifier entry we're actually going to add two so let's add the first one and again we want to search on that location table there we go and we want to give it some criteria here we want to search for specific attributes so let's add in Street let's add in City that's it and State and zip code we want to keep it at priority 100 and let's submit this one and then we'll make a second one let's make our second identifier entry we're going to search on that same location table we're going to look for the name for the Criterion attribute and instead of giving this priority 100 we want to change this and actually give it a priority of 200. we're also going to be creating a related entry rule in the cmdb related entry table let's go into related entries and click on new and here we're going to keep our related table the same for our referenced field we are going to choose parent for the Criterion attributes I'm going to use the name and in this one the name plus the parent sis ID will help us to uniquely identify that related record so previously the related records can be non-cmdb tables which has reference to the cmdbci but with this new change a non-cmdb table can refer another to another non-cmdb table and in this case we're referring to the location itself and that is how you can create a non-cmdb rule I hope that you found this helpful and I appreciate your time today thank you