CHAPTER THREE, working with data. In this chapter, we'll talk about data structures, import sets, and configuration items to CMDB. Data Structures ServiceNow provides a sophisticated graphical user interface built on top of MySQL database. All data operations utilize MySQL services. This means the hierarchical data structure with service now appears somewhat like shown in here. The database and underlying tables and tables have records and records consists of fields.

Information related to service now instance is stored in database tables, which have records consisting of fields and the related values within them. Reference fields reference fields are the fields within a list, which referred to the records of other tables stored within the server Now, they're accompanied by a reference lookup icon next to them. Example, in here, the value of color field. Within the incident list is a reference field, where the field is referencing to the users table records within ServiceNow. Note, it can be observed that each table within ServiceNow has a common name, and a system name. There are several ways in which the structure of a table can be viewed or modified.

First is the table module. Within system definition application tables module provides a record for each table stored within the ServiceNow instance. The list shows the common name along with the system name for each table. Using this module, we can perform following operations. Add view or modify the fields within a list using column tab. Define order number format, make tables extendable by other tables within control, stab, or provide application access.

A graphical representation of relationships between tables can be displayed by clicking like the one shown here, show schema map link, which is available when we scroll down. Or we can view dictionary entries for additional information on database elements by right clicking the header of the form and selecting an option called show dictionary record. redirect to the list or form view for the table by clicking the respective option. It was also shown before and delete all records in one go by clicking Delete all records, which is an option provided on top right corner of the form header tables and columns module. This module is also available within system definition application and position is read only capabilities. This means user can simply view list of all tables, their columns along with related attributes and indexes.

It is mostly used to view the schema map for tables and is accessible only to system administrators. scheme schema map as mentioned before, it is the graphical representation of table relationships connected to each other via class reference or extension. In here, schema map for execution plan task table is shown. A legend is shown on top describing the different color schemes followed by tables in the graphical representation. The tables group package, execution plan, application, service level agreement and user available to the immediate right of the execution plan task with the red bar are the tables that are referenced by Similarly, the ones with the green bar, like in here, the application file is extended from execution plan task. In case the entire table is not referenced or extended, but rather a few columns are.

The color scheme is represented by the mix of color scheme code shown here, like this one, right or even in here. System dictionary. System dictionary is simply a table called dictionary entry. The table name is sis underscore dictionary, which contains additional information about each table along with definition of each column within them. Thus, each row within this table represents a table or a column of a table available within ServiceNow. This enables the system administrator to update tables and their fields, thereby defining the list And forums frequently use tables, there are a few tables which are commonly used by users of ServiceNow instance.

These include, first is task. This table is represented by a system name task. It stores records corresponding to work. Thus, it is comprehensible that this table is extended by various other tables such as incident, problem, change request request, requested item and more. Feel free to check the schema map of tasks table for more information. Next is configuration item CMDB underscore ci.

This table records with information corresponding to configuration items. Commonly used tables that extend configuration item table include computers which is CMDB, underscore ci, right. And data center CMDB underscore ci underscore data center database CMDB, underscore, ci underscore database etc etc. User this table is represented by system name as sis underscore user and stores information pertaining to all users with access to ServiceNow instance group. This table possesses assist underscore user underscore group as the system name with group records knowledge. This table stores the knowledge base articles to quickly browse through and look for potential solutions to a problem.

System name for this table is KB underscore knowledge. Note, there may be other tables frequently accessed by users that may cater to form specific requirements. All information related to tables such as their structure extensibility, referencing etc. can be found in tables module within this system definition as we discussed before. Table relationships There are several ways in which tables can be related with each other. First is extensions.

Extending the table means including all fields from the parent into the child table, along with its own additional fields. Example, table bicycle may have generic information regarding all bicycles such as speed, gear, etc. This table shall be extended by a specific bicycle table such as mountain bike, which will have fields from the parent table, along with its own features like seat height, suspension, brakes, etc. Next is one too many. A table can hold reference to fields of other tables. This can be done in three separate ways.

First, a user may use reference fields to select record from a specific table. Example, color field used in the incident table refer to a single record within the users table right. Next, a user can be allowed to select multiple records from a table using glide list. For example, in any incident form notes tab, like shown in here will have watch list field where any number of records can be selected from the user table. And finally, a table may incorporate document ID. This field is where records from any table can be selected.

Example, translated text table has document ID field, where user inputs the table name along with the record from that table. Many too many tables are not always unidirectional. That is they can be bi directional relationship between the table which signifies that the common fields can be accessed within records of both tables. A quick example would be the relationship between student In some classes, students can enroll in many classes and classes can be enjoyed by many students. views. Views are the virtual database tables joined together consisting of relevant fields needed by the user.

Database views plugin is required to implement this functionality, and is mostly used for reporting purposes. Table hierarchy. It is worth noting that all extended tables are simply an enhancement to the parent class. they inherit fields from the core tables which exist in ServiceNow instance form the blade base class tables, which are extended to form its subsequent child class tables. An example is shown in here, where the task table is the base class which extends to create parent class tables such as incidents and change requests. These parent class tables further extend and form child class tables.

Which provides specialized fields and values catering to specific user requirements. To perform extension, we simply select the table name within the extents table field, within current table record. Note for an extended table, a differential table, table name other than the system name can be defined within system definition, application and language file module within it. Samples use case 3.1. In previous sample use cases, we have created groups and incidents. In this section, we'll create a new table to track progress of new RV robots.

Right I'm making this up and create a new table and extend it from the core gas table. We have to go to System definition application. And within it, we have the tables module. So right here, and in here, we create a new table and we provide some details. Let's say the label is the RPA pro to type, the name will be automatically filled once I click outside, right, and we want to extend the table gas table. I'm going to search for the table, I'm going to select it and right so this is how the table new table creation form looks like.

And we made sure that we want to create a module for it and a mobile module as well for mobile applications. And add module to the menu create new which is there by default, and we also provide a new menu name which is same as the label. Right? So we have this information we can also change the name out of what we have for the default value, which was automatic. Quickly populated, but for this particular case, let's let it remain as is. So now we click Submit.

And detailing along with the module has been created successfully to verify. Let's go to z RP prototype and you can see that we also have a module called z RP prototype. Right. Now, an additional information since the task table was extended in previous step, its fields all the fields which are there in the core task table are also visible in this VRP right module, like the number priority state you can see that right. So that's the benefit of having the extent right if you have extended a table inheritance capabilities plus In addition, we can have its own specific fields or properties as well. So one The module has been created and accessed, let us design and customize the form for the same.

For this, we are going to click the New button within this content frame. Here, right, and in here you see a few fields right, and we have to configure this, we have to configure the form. So we go to the context menu, we go to configure, and this time, we're going to choose forum design. So it redirects us to a separate tab, where we have like, you know, a feature available to drag and drop all the required fields we want. So first, we have like the whole screen divided into two separate sections. One is this section and the other one is this section.

The first section has two columns in it, and the second one has only one column. So if you want to delete a complete section, all you have to do is choose this cross button on the right within this gray bar. Right we can delete the whole sexual Let's read the second, the second call Section all together, right. And similarly, if you want to delete particular fields, all you have to do is click on those cross buttons next to each field. And those fields will be taken out, just like this, you're going to delete every field so that we can, like, you know, build our complete form right from scratch. Right.

So currently, we got two columns and no fields as such to display to, you know, work upon. So, to choose the fields, we should go to field types. So field types are gonna describe what type of data we want our field to store, right? The nature of data, it could be like, you know, a string type, a numeric type, is it a data type or a decimal number, etc, etc, right? So these fees that you're going to add these are going to cater to our specific use case requirements. Right?

So, in here, we're gonna first take, let's say, our type string, we're gonna drag and drop it to the first area, and we get a new string here, right? We want to give it a name something which makes more sense. So we're gonna go to this system gear icon. And over there, we get the properties of the new field that has been added. And we're going to add the name, let's say prototype number, because we're working with RPA for right right. So, if you know based on my requirements, product number is something like p r o t 001, then having a string type is is going to make much more sense, right?

If it is just numeric, you can definitely use a number as well. And we have to make sure that you know there are no preceding zeros in the number otherwise they might be, you know, truncated, like 001 in numeric form would be simply just one right? So mean, these are like a few things you might want to remember. So we don't have a Save button, we just graphs and we get the product number. So similarly, we are going to add more fields, right? I'm going to have more string fields, because that's a most common one.

I'm going to add bought ID, right? And we're gonna add another field below the prototype number. We're gonna call it a system name. And last, I'm gonna take a reference type field. So if you remember, just now when we were extending the task table, we clicked on that reference icon, the lookup icon. And what it did was it was referring to the records of like different tables available within the ServiceNow instance.

Right? So that's what a survey Reference Guide does. So let's see. Want to know who is the creator of the bot? Right? So guess which table it should be referring to?

Right? It's going to make more logical sense. By simply realizing the fact that a creator would be a user within the ServiceNow instance, right, it's gonna be a person. So we're simply gonna use sis underscore user. Right there. Okay, you're gonna close it, and we have the form all set, you're going to hit save.

And you can see the progress bar shows that it has been saved. You can also close this now if you want. And if you go to z RP prototypes and click New, you will see those four fields are now available to you. Right, so that's another way of beautiful way to design the forums specific to what you need to do. Right. So I'm going to stop here.

And I'm going to ask everybody to try out an exercise, which is going to be to create four more fields into this form. And I'm going to give the details, we also have this exercise to try out in as a separate attachment to this tutorial. So please feel free to check that out as well, too, but I can also describe it here. So you have to create four different fields into this form. The first field, we're going to name it as status, it's going to be of type integer, right. And then the next field is going to be named as assignment group, which is going to be of reference type.

And the table that it will be referencing to is going to be sis underscore user underscore group. That means all the user groups, right, the third field we're going to add is going to be called as demo location, which is again going to be a reference type and it's going to refer to c m and underscore location table. All look Have edibles within the ServiceNow instance. And last is going to be a nurse field. And this notes field is going to be of type journal. Right?

So add these. And once you're done, jolly, what I'm going to show in a minute, like how your form looks like versus how the form that is currently being displayed to you is, right, okay. Okay, so this is how the form is going to look like after you make those changes. I'm sure it should be pretty straightforward. So, you know, let me know if you have any problems or if you're not able to do it, but we have to follow the same steps as we did for the first four fields. Right.

Okay. So now, let's change the title of the application. Right? From z RP products because we have the same application name and the same module Emma's fault, right? We we sort of don't like it. So let's change the title of this.

Application from CRP prototypes to something more specific, say SAP prototype. Right, I'm just in the hypothetical situation here I'm considering that we are working on SAP RPA prototypes, right. So alongside, we'll also add a hint to it, right so that any other user can get a glimpse of the usage of this particular application. So for this, what we're going to do is we're going to right click on the application and we're going to choose this edit application menu. Right, and in here, we can change the title, two Sep product type. And we also have a hint feed in here.

So this is where we provide the link data which is going to be displayed SAP RPA bots or anything and why unless we've added these two details, all we have to do is simply hit update. So now if we are gonna look into so it took a few minutes to get a few seconds to get refreshed. But if you go and check the sap bird I RBA products, you'll see that the application name has changed to SAP prototype. And once you hover over it, you can see display SAP RP bots is the INT that is being displayed. Right. Now on scrolling down we can see that there are modules like these are the modules which are available within this particular application.

Right. And this way, the user gets the ability to add new modules as well within a particular application. So we're gonna hit New and we are going to add some details. So the form has been displayed to add a new module, we are going to make a lot provide the name as the RPA demos or something like that. Right, and it's a part of the Sep prototype that's already been shown. And once we have entered the title here, we can click on the link type, which is, which is sort of mandatory here.

And in here, the link type is going to be, let's say, like the what type of link you want to have for this particular module. So we can choose like, new record, we want to create a new record right from scratch. Right? Because we don't have an existing or we don't just want to make it a course new, we want to have like, for the CRP emos module that we'll be creating within the Asian product application. building that we want to create should be a new record. This is happening like within like the table structure of the entire app, the application and the module itself.

So those levels We want to have a new record. And once we do that, we have to select the table as well. So, if you remember, we had the RPA prototype one, right? You have to make sure if you have another one, then Which one did you choose? Initially right? I made the change, which is going to be this one every prototype Africa table, but like the automatic name that was that came up initially, right?

Because I have worked on this instance for a while. But if you don't, then make sure that you choose only that particular table where which you want to link to this particular module that you're creating now. Right. And once you have added this link, the mandatory field table has been also provided with the value all you have to do is hit Submit Once submitted the application menu Also got refreshed. And now if you put in SAP prototype, you see there are two separate models zerp, demos and CRP prototypes, right. So this is how we can work into the application and the module level to create custom modules specific to you know, your company or your firm or yourself that you're working on.

After use case 3.1 now we're going to talk about involves s. What is an import set. And important is the tool used to import data from external sources into ServiceNow. The data gets stored in tables, and admin users have the authorization to manage them. In this case, the data is already present in ServiceNow. They enforce it we'll skip that record from external source and import rest of the non duplicate records. Several external data sources are supported by Forbes s. The process of importing data into import set table, transforming it into ServiceNow readable format, and then subsequently transferring it to the ServiceNow table is described in here.

Importing data from an external resource requires the directory location of the file, along with the proper authentication credentials. External Data sources are broadly classified into file sources and network sources. So file sources include data from documents like Excel, CSV, XML, etc. And the network sources on the other hand, include data retrieval from online things like HTTP FTP, JDBC, and so on. Data from external sources is added to the import set of tables as you can see right here, which acts as the staging area. From here on, the data is moved into the production environment via transit.

Format. Transformation maps link the source fields to the destination fields, making data insertion process correct and reliable. mapping of fields can be accomplished by automatic matching performed by the ServiceNow or by implementing advanced logics and scripting languages. Transformation maps are reusable destination tables within ServiceNow where data shall be inserted from import set tables is defined within the transformation maps module of system import sets application. It is worth noting that a single field from an import set table can be mapped into multiple fields at the destination and recommended practices. Although data migration from external sources into ServiceNow instance has been highly simplified.

There are a few tapes that must be kept in mind at all times. First, check the data and cleanse it thoroughly before putting it into service. Now, loading incorrect data and then remediating it takes a lot of time and effort. Secondly, dedicate an adequate amount of time to plan execute. Make sure the data migration doesn't affect usual ServiceNow operations, and that plenty amount of proper time is scheduled to complete the data import legibly. And finally, load a few records initially before performing the whole load in a single goal.

This makes sure that the data transformation has successfully mapped into relevant destination fields and the data is going into system error free. Steps to use import sets and transform maps. There are three major steps that are carried out to us import sets and migrate data from external sources into ServiceNow these are in this particular sequence load data create transformer and run the transform load data. To load data we go to load data module within the system import sets application suite select the CREATE TABLE checkbox and add name of the import set within the label text box. The external file with data to be imported is browse within the file field the option provided. As you can see on the right, the header and sheet number options provide a means to identify the arrow and worksheet number for specific data extraction.

All submission of this the progress form is displayed with information like stay the completion code and progress. Create Transform, transform link see importing data from feeds into target fields of tables like users, change requests, etc. And for this, we'll click on the link create transform map within the progress form. In the subsequent screen, table transform map is displayed, which shows the form to select target table, Provide a name to the Transform, map and raise other options. Under the Related Links title. There are two utility options that are provided to users to perform the mapping operations.

Here are those are the matching fields in the simplest mapping technique, where the import data set fields are automatically mapped to the fields of destination tables based on their names and thus data is transformed. Before submission. The map fields are displayed to confirm it. In case of any discrepancies the mapping can be modified using mapping Assess utility. Once mapping is all set, simply hit transform to initiate the transformation. Next is mapping assess.

This utility provides a graphical interface to specify the mapping between the input set fields and destination table fields. Using this option, a user may match the single import set field to multiple production table fields, and same data would appear across multiple columns of the destination table. We'll be discussing these options in greater detail in our sample use case. Once the transformer map has been provided a name and a target table. You can click on the auto map utility to see how current mapping looks like. This is how it may look like as shown on the right.

Right and it may be different based on the fields that you may have. And, if needed, they can be modified using the Martinez is also an additional information, we can see on the right that there is a wireless field. This wireless field is used to uniquely identify the records and serve as their primary key. Thus, if new data is imported with the same wireless cw, the record instead of being duplicated or ignored gets replaced with the updated information. Run transformer once the field mapping is confirmed, click transform within Related Links section of table transformer and the subsequent screen confirming the import map will be transformed is displayed. In case multiple transform maps exist, they all can be transformed in a single go using the slash Bakit.

The selected maps can also be selected and not transform the data. Finally, whether the require matter insert into the selected maps been the hit the transform button. The next screen will display successful completion of transformation along with the relevant message. Note, the transformation operation can also be scheduled to run at a later time interval instead of the immediate run. Sample use case three point children. Let's take two Excel files we are going to name them as RPS sample one in our case number two, with some data and a data we are importing to z RP prototype table which we created in the last sample use case.

So these are the contents and for the first file, we have prototypes 001002 all the way to 05 with their bot ID, system name, status and notes. And for the second file we have from 006 to 009 and user two again. So it is worth noting that this last row in here, it's gonna provide an updated version of the data right when we will be importing it into the ServiceNow instance all this all this data. So next, we have these files already set up. So now we'll modify the list layout of VRP prototype module, which is within our SAP product application to cater to our data load we will be performing very soon. So let's go to see our prototypes module within the Sq Burton application.

And in here we go any column control icon which was same as context menu, but next to each and every like header, any header. So we go to the control menu, and we go to configure and we choose less layout. Now we are provided with a slash buckets where we'll be choosing or we'll make sure that we select only or at least all those fields which are available as errors in these Sample Files that we just took the Excel files, right. So we're gonna take these out you can see we are deflecting them or putting them in the available pane and we want to try a number. So, for that, we go to if we can also just press P again and again we can find those we need bought it as well, right and we need system name. So we go there, then next was status.

And finally we had enough right? So this way, the data will be mapped correctly. And will be visible to us in the content frame itself. Any additional fields that we may have in the selected pane can be there in the list as long as they are not mandatory. Right, so we hit save. And we can see that our live changes that we just configured have been updated successfully.

Now we create a new import set to upload the data from the external resource into our ServiceNow instance for transformation and insertion into the relevant table. So for this, we go to low data module within the system import sets application, and in here we are choosing to create a table. Right We are gonna provide a label to the import set, and we choose the file that needs to be uploaded. So let's provide the name as let's say RPA sample one and File we're going to choose is available I put it on the desktop sample one and now all we have to do is hit submit. So, this next screen the progress stage, the screen confirms whether the operation was successful or not right. So, we have the completion quarter successful in the status complete.

So, we can always you know, perform this to see how the current state of data load is we can also choose the loaded data option in here in the next steps option in the next step is label and an overview of imported records which currently will be in pending state can be seen these records are the ones which will now be transformed for insertion within the relevant table. Right So, the green transform whether you Choose the Create transform link, which was below the loaded data option. As we can see just now, the Create transform option is there, right? Or we can simply go to System import sets and create a transform, which is like a separate module altogether. So let's click here. And in the in this table transform, we provide a name to the transformation to be performed.

So make sure that the source table is the one provided in the data stream before if you remember when we showed that, like the CREATE TABLE option, so let's do it like this. Let's Provide a name which is going to be our VA underscore sample one. And do we have the source table from business rules? No entry fields or require and you have to choose the target table. So the RPA in prototype, this is my table where I want to perform the transformation. Okay, so it can be seen that the current table for the page displayed on the content frame gets the name of the transformer added to it.

So now we're gonna go and choose the automatic matching fields option and automatically the mapping will be done. There it is. So you bought ID notes for that number and status. So it can be seen that only four fields got automatic. While we have five fields in total. Just we will be using the mapping assist within directory links to map the remaining one field manually.

Right so in here you can see more ID is mapped notes is macro type numbers map and status map. So which one is left let's open the file system name. Right. So in there in that case, we'll sit down we'll take system name, we'll add it here and in the target CRP prototype, we have to choose where system name is. There it is. So we go there and we put it there.

So, using this add and remove buttons, we can you know, a minute maintain the connections between the sample file and the target between the source and the target the sample file and DC RP type module. Right now we are going to hit save. And on saving we are redirected to the table transformer area with the correct mapping dislike. It is also worth noting that field ordering during the mapping process right where the bot ID is First off, notice first, it doesn't make a difference in the overall data load process. Once it has been validated, all you have to do is click transform again within the Related Links label. The subsequent window shows the available and selected maps that need to be transformed by the user.

Make sure that the import map that needs to be run is available within the selected panel. And once it is selected, able to transform the progress page will display the status of data transformation operation to verify the data has been loaded successfully. We'll go back to the SMP prototype, the Z RP prototype application, the module and in there, you can confirm that Recent data load has been successfully done. Now, in the next section of this use case, we'll be loading the second sample file where instead of creating a new import set, we'll be using the existing one that we just created. So for this, we again go back to the load data module within the system, import sets application, and instead of CREATE TABLE we'll choose the existing table this time. And if you remember the name that we gave was RP, sample one.

So this is the table that we are gonna be using the same rules and operations and everything. And in this time, we'll be taking the file as our example to file. Right, and all we do is hit submit. And in the progress page, we can see the record their status and completion code. If it is successful, that means you know that everything has processed successfully, there could have been other statuses as well, in case there is something wrong, then we may have to check the file and see if there's some erroneous character or that has not being, you know, read by the ServiceNow application or could have been any other users law, they might have been some connectivity issue or something. So you can see there five inserts and five updates and, like, five inserts and five have been processed, so no updates, no errors, everything seems.

Right. Since we have the transform map already in place. Now this time, we'll go to transform maps module. So transform maps module is within the system, import sets and the administration. Right here we have a transformer. In here a list of all of our Transformers So within the ServiceNow instance are displayed, choose the one we created for first Excel file, we should remember that our sample one, and we're gonna get it here.

We can also confirm the field mapping, which was shown earlier is still as it is. Now in the two Excel files with data, one of the bots have the same for a number. Let's go and check that out again, the prototypes use you have to in the sample file one and in the sample file to the product user two, but there might be some other changes let's say you know the system name is doing the first one but over there is production. So the data is different but the product number is the same. So what we are going to do is in this case, we are going to go here and with the prototype number of fields. We're gonna send the koalas to Which means project number will be working as the primary key for for the Excel file that will be transforming and putting loading the data for in the ServiceNow instance.

Right, so to change it to change the value, simply double click, and we get this quick add in menu and we choose the value to true and we hit save and enter the green sign. We are all right, and you can see that this has been updated and all we have to do is hit update on this form. Now the new setting is also been saved successfully. Now to initiate transformation, we click on the transform within the Related Links. So we also get this option Carla's field is not indexed. So indexing is mostly used for performance, right?

If we have an index field, then we can click OK, which means it would make the performance much better. But for five records, I mean, we don't need it. Still, it's good to have so that's totally fine. And we can put upon completion or we can just cancel this one because that way we need some authorization we may need to provide an email address where any changes that we are going to make will be notified to the system administrator as well. Okay, so in the Related Links, we hit the transform button. And in here, we get the selected or the available maps that we that the user has to run is the RP sample one.

And in there we have the Excel file to all set. So we have made sure that this one is selected and all we do is in the transform The completion message has been shown and we can see that you know, we have an import set to and we can also verify if the data has been loaded successfully or not. So, for that, we are going to go to the RPA prototype module and we have 2009 and the appropriate user to the system name has been updated to production, right. So, this means the data load was successful and the coalesce field that we did set out which was perfect number was also able to identify existing record and updated fields instead of creating an additional one. The bot ID is also changed, right? So, anytime that information in case there is a field called copy empty fields with when we were dealing with paper transform laughs in case that actually does check existing data from the table would be wiped out.

And since it was unchecked, in our case, the initial data, which was from the previous load from the Excel, the sample file, one, it remained intact in our system in our application, right. So you can definitely check that out if you want to wipe everything off and let's say like you loaded information about like employees of your form. And now you have updated information for like pretty much every employee, right? Let's say everybody seemed like a change and a few other details change everybody there was a reshuffling of within the departments and everything. So you want to get the whole data into the system again. So instead of doing two separate operations of deleting and putting the data again, all you have to do is check that checkmark box in a copy empty fields and the previous data will be wiped out and only the new updated data will be available in your ServiceNow instance.

Finally, once the import sets have been you Using data has been loaded, we making up the import set to remove any additional or duplicate or less unnecessary data. So, to perform cleaner, we can go to this cleaner option which is right in the system import steps imports the tables and the cleaner right and in there because we have worked with the inputs as in as much as we wanted it, so we simply choose whichever table she wanted to lead to we complete the transform maps or doing the data table structure will be saved, that's totally up to you and simply hit the rutina and the cleanup mirror verification message will be displayed confirming that the cleaner has been done successfully. configuration items to CMDB CMDB constitutes a series of tables and fields within these tables that provide a logical structure to the conflict. action items related to a company's infrastructure.

It reliably identifies controls maintains and verify their existence along with their attributes and interrelationships. Thus, a configuration item cir is any tangible or intangible device or application within CMDB configuration management database such as computers, network devices, Business Services, firewalls, email servers, etc. These API's help in delivering services for the company. VSM bsm stands for business service management. A PSM which is also called dependency view shows the upstream and downstream dependencies in between different configuration items. upstream Civ constitute the devices or applications that feed into the Cir.

We are looking at the map for the business service email ci, where you can see there are few cis and the downstream cis to downstream cis include set of devices or applications that are affected by the chosen ci which is as you can see business service email in this case, it is worth recalling that there are two base tables within ServiceNow the desk table and the configuration item table. Further more detail June major CMDB tables include goal configuration items, the CMDB ci table and the CI relationship which is CMDB underscore Arielle underscore ci table. The core table stores some basic attributes among all the i's while relationships table defines the relationships between the CIS So, this processes, processes related to delivery of services provided by a company such as incident logging, change management service requires etc are called service processes. All service processes make use of CMDB.

For effective CMDB implementation, a few points must be kept in mind at all times. First, review base instance tables make sure the table that needs to be created doesn't already exist within the ServiceNow instance. Second, prepare CMDB schema beforehand. This provides an overview of which all tables will be used and how do they relate among each other. For data must be kept current and periodic data refresh must be scheduled for data shall be managed efficiently By keeping in mind the people using this data processing is carried out and the technology being used. Last, only required data should be stored within the tables.

Any additional data or unused data fields should be scaled to keep the system clean and optimal at all times. CMDB implementation requires a serious commitment from the company. However, the benefits realization of having an effective CMD CMDB far outweighs the efforts needed to implement it. Some of these include maximized cost savings, quick impact analysis and reduce system downtime and efficient business processes and IT Service Management. As discussed before, we can look at the CMDB schema to analyze the details of tables and their relationships graphing this schema for computer looks somewhat like this as shown on the right hand side. Different relationship types can be seen within this figure.

This includes the image ID as well as interconnected configuration items with computer fields for parent table can be inherited by the child tables along with their unique fields. The table below in here shows the various relationship types, along with the color scheme used by ServiceNow to depict these relationships, referencing his orange reference by his red extending his blue and extended by his green as you can see right here. Parent Child relationships the phenomena of sharing the seeds from root table which is called the parent to its subsidiary tables, which are the children is called inheritance child tables. Hold share feeds along with their own unique fields serving a specific purpose. Configuration Item relationships, a separate table is maintained within ServiceNow to define the relationships between ci based classes and interdependent classes. These relationship rules are created and accessed in configuration application and under it the suggested relationships module.

Base table a table that is extended but itself doesn't derive from an extension is called a base class table. And bsm maps a business service management map graphically displays a CI supporting Business Services along with its status information. It can be accessed from the CI record or within an incident or problem forum when cis selected the VSM Map becomes visible as soon as the configuration item is selected in a forum, right as shown here. These maps provide useful information in further investigating and resolving an issue populating the CMDB we have discussed the way of inserting data into a CMDB using the import section for However, there are other ways as well that can be applied to populate a CMDB namely discovery which is an automated product provided by ServiceNow integration using the other external cmdbs. The web services using the API's Help Desk desk, it is provided by ServiceNow within the integrated backbone and manual which means the manual to do insertion of data.

This is discovery. Discovery is a product from ServiceNow which provides an extension to the platform by automating the data population in CMDB. Its uses and mid management instrumentation and discovery server, which is installed on a network to enable sensors and probes and collect information on that network such as hardware or software running on that hardware and relationships between all the founders. This information is then transmitted back to ServiceNow instance and correspondingly CMDB is populated. The figure here shows the setup of a hosted agentless discovery configuration. Under the help desk, help the help desk with the tool integrated within the ServiceNow platform that populates CMDB with information about the Windows system.

In other words, it only works on Windows machines. I'd provide information catering to hardware and software only. It is not extensible to identify other servers, unless discovery is also executing on that particular instance. Sample use case 3.3. We'll continue our previous example and set up two servers, namely MSM, the most secure module and a backup directly linked to the MSM server that stores all important information catering to RP for these servers will be added manually to the CMDB. So to add a server we go to, if you choose configuration, and configuration, we have servers and here we have all like all the servers available The application is taking probably some time to open up.

Okay, so we see all of the servers now and we're going to add a new server. Alright, let's add, like the following details z MSM 012. The first one if you're adding right and we can we can just select the model or we can add a manufacturer also whatever this server is about like so. I mean, we have some pre configured models. I want to have it as a level right? Computer server level, you see automatically the manufacturers are selected, but what you could have done is you could have selected the manufacturer and selected the models available by that particular manufacturer.

So why do we Stop. This is actually a very good example of data integrity to it makes sure that whichever model it is selected, automatically the corresponding manufacturer is selected as well. Right. Now, once we have provided this detail, let's add some configuration details as well. So operating system let us say put it as Linux cetera. Okay, iOS version, put it in February 28th.

And who is the CPU manufacturer? Go to das Intel. Okay, and then we can have some CPU time what type of CPU is there? I'm gonna make it a Celeron CPU. Right? These are the details that must be provided to you beforehand and like, you know, you can configure that as specifically your new server that you're putting in your ServiceNow instance.

All those details are correspondingly added here. So the MSM, see what I'm putting our description, most module active server. So this is the first one right? And I'm gonna hit save for now, because I want to see this particular instance and now I'm going to add another one. So if you remember, we also discussed about insert and say, which means it's going to insert this record the Z m is m 01. And it will also provide us an option to save another like server or any other details which You know, we might not have to duplicate all the stuff that we're putting together.

So if you remember initially we discussed if you're gonna put up the, you know, a backup server to someone name it as dm, sm 02. All the configuration is gonna remain the same, except for the description most secure model, this module backup server, I'm just adding a new record right? And again, inserted state. So if you go to all servers, you can always check that out. The MSM 0101 got added twice. So what you may want to do is you may either want to delete it, or Okay, so now you have z m is m 01, and z m is m zero, right?

Because I did Save and insert in the state twice. So I should have chosen certain state right in the first step. So, right just wanted to show you the difference between the Save and insensitive because we discussed about these, which we never got the chance to work on this. Right. So now we have the records and everything. Now we adding the relationships between the two items.

Right? So these two servers, we have to relate them with one another. And to do this, we'll open this E sm 02 record, right and if we scroll down, we have a bladed items in the tabs in here right and we click the plus button to add the CI relationship between the MSM 02 server and MSM 01. And we scroll down see if you're going to use this one which is going to be used by child because MSN Jude is going to be acting as the child for the MSM grms m 01 will be the barrier right and you Which server Do we have to add MSM 01. So we're gonna run some filters I'm gonna take these out and probably name as starts with a C MSM and run filter. And you see down below we get the configuration items, which means there are filtering criteria and I'm going to select this one.

Now, we have selected the configuration item which needs to be for which m sm 02 would be the child and now we will be adding the relationship as well. So for this we have this relationships tab and we click on the plus file where we add this right and once we did that, you can see that it has been successfully added which means there are some 01 is the parent MSM 02 is the child right based on whatever parameters we set up before everything the relationship is between say, now I mean has been created. To save if we simply click on Save, there will be, you know, changes in the CMDB. Do you want to continue? Yes. Okay, so it has been saved and we haven't exited yet, we can now cancel it.

And it can be seen within the related items window tab that the relationship has been successfully. Right. We can also view the dependency view the bsm by clicking this link here, and it will show the relationship in a graphical format to the one that we also saw when we were going through the PowerPoint presentation. Right, fairly simple. So that's how we add the CIS and we create relationships between them and you know, something that is specific for the company that you're working on.