Pass Your Certification Exams on the First Try - Everytime!

Get instant access to 1,000+ certification exams & training resources for a fraction of the cost of an in-person course or bootcamp

lock Get Unlimited Access
  • badge All VCE Files
  • book All Study Guides
  • video All Video Training Courses
  • download Instant Downloads

Pass ServiceNow CAD Exam in First Attempt Easily

Latest ServiceNow CAD Practice Test Questions, Exam Dumps
Accurate & Verified Answers As Experienced in the Actual Test!

You save
$19.99
Save
Verified by experts
CAD Premium Bundle
Exam Code: CAD
Exam Name: ServiceNow Certified Application Developer
Certification Provider: ServiceNow
Bundle includes 2 products: Premium File, Training Course
Download Now
accept 80 downloads in the last 7 days

Check our Last Week Results!

trophy
Customers Passed the ServiceNow CAD exam
star
Average score during Real Exams at the Testing Centre
check
Of overall questions asked were word-to-word from this dump
CAD Premium Bundle
  • Premium File 151 Questions & Answers
    Last Update: Mar 19, 2024
  • Training Course 54 Lectures
Premium Bundle
Free VCE Files
Exam Info
FAQs
CAD Questions & Answers
CAD Premium File
151 Questions & Answers
Last Update: Mar 19, 2024
Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.
Download Demo
CAD Training Course
CAD Training Course
Duration: 8h 35m
Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.
Get Unlimited Access to All Premium Files
Details

Download Free ServiceNow CAD Exam Dumps, Practice Test

File Name Size Downloads  
servicenow.testking.cad.v2022-01-11.by.maisie.46q.vce 89.5 KB 867 Download
servicenow.braindumps.cad.v2021-07-27.by.marc.54q.vce 100.6 KB 1012 Download
servicenow.train4sure.cad.v2021-04-11.by.mohammed.28q.vce 67.9 KB 1108 Download
servicenow.passcertification.cad.v2020-09-22.by.harry.36q.vce 74.8 KB 1483 Download

Free VCE files for ServiceNow CAD certification practice test questions and answers, exam dumps are uploaded by real users who have taken the exam recently. Download the latest CAD ServiceNow Certified Application Developer certification exam practice test questions and answers and sign up for free on Exam-Labs.

ServiceNow CAD Practice Test Questions, ServiceNow CAD Exam dumps

Course Introduction

1. Course Overview

Hello and welcome back. In this video, we'll discuss the prerequisites for this course, and I'll provide an overview of the instance I'll be using. Okay, so this is not a beginner-level course. Having a solid understanding of ServiceNow is definitely recommended. It's even better if you have personal admin experience on the platform. Having a solid understanding of database concepts like tables, fields, and records will also help you with this course. I also recommend having a general understanding of how Web apps actually work over the Internet. Now, you don't have to be an expert in this field; just know the difference between client-side and server side.And finally, because this is a scripting course, JavaScript is a prerequisite. Unfortunately, due to the scope of this course, I will not be teaching you JavaScript. There are literally hundreds of thousands of other amazing courses, videos, and materials out there on the Internet. and I'll point you in the right direction. But just keep in mind that when we start coding in this course, I expect you to have a general understanding of JavaScript and some object-oriented programming concepts. All right? So what you will need is a computer with a modern web browser and an Internet connection; that's really all you need to watch the videos. Now, in addition to that, I highly recommend getting your own personal instance. You can do so by going to Developer.servicenow.com and signing up for a personal ServiceNow instance. If you follow along with a ServiceNow instance, I strongly advise you not to do so in a production instance. So if you work for a company and would like to follow along, I recommend either getting a personal instance or, at the very least, playing around in a dev instance. All right, so for the purposes of this course, I will be using my own personal developer instance. Keep in mind that this may differ slightly from the box or from the instance you are using.

I try to keep my instance as close to out of the box as possible, but I've had this instance for many years now, so keep in mind that there will be some differences here and there. I am running Istanbul on my personal instance, which is using UI 16 and Listb Three. Again, if you're using a different release of services now, that's perfectly okay. You don't need to be on this specific version or even be using UI 16 or List V 3. The core concepts that we discuss in this course are Release agnostic.So a business rule will always be a business rule within service. Now, whether you're on the Eureka release or the Jakarta release, Now, while there have been some big changes to the user interface and service now, and things might look a lot different under the hood, it's all just configurations stored as records and tables in a database. So if your instance does look different, try not to focus too much on the looks as opposed to the concepts that we're discussing. The user account I use in this video has the admin role and security. Admin role, and the browser I'll be using is the latest Mozilla Firefox release. Right now, let's discuss the text editor I'll be using. So, I just wanted to let you know right off the bat that a text editor is not required. ServiceNow has actually come a long way since the old days, where you were typing scripts into an input field. Now they have relatively modern and browser-based editors that you can use that are just as powerful as the text editors you run on your operating system. But for the purposes of this course and for your readability, I chose to go with the Adam text editor. One of the amazing things about Adam is that it's an open-source text editor by GitHub, and it's completely free. Here's a screenshot of the code we'll be writing within the upcoming videos within Adam and the majority of the videos. I'll write the code in the text editor, and then I'll copy and paste that code into Service Now just so it's easier to read for you guys.

All right, now let's discuss some of the core goals I wanted this course to have. So, the ServiceNow platform is huge, and with every release, it continues to grow, introducing new tables, new business rules, new client scripts, etc. And as someone learning the platform and being introduced to this for the first time, it can be extremely overwhelming. So I asked myself, with such an overwhelming number of places to script and ServiceNow, how could I fit this into a course that actually makes sense? Well, in this course, I've decided to focus on the what and how rather than the where. So instead of breaking the course up into sections that cover where to script, Instead. Each section will cover more of the what and how. And then you can apply that to the specific locations within ServiceNow now. In section three, I'll still cover probably 95% of the scripting locations you'll use as a Service Now developer. But I'm focusing more on the what and how, specifically on the Service Now APIs. And then, once you have an understanding of how the APIs work within ServiceNow, it doesn't matter where you apply those, whether it's a business rule or a script include. Now, at the end of every section where I introduce a new ServiceNow API, I will tell you where the specific API can be used, whether it's client side or server side. Now, while I've tried my best to cover all of the most important scripting concepts in Service Now, this course does not cover every single scripting component. So this course shouldn't take you all the way there, but in order to understand the entire platform, you'll still need to read the Service Now documentation.

Hide

Development Overview

1. ServiceNow Basics

Hello and welcome to Section Two. In this section, I'll provide an introduction to ServiceNow as well as an introduction to development inside ServiceNow. We'll start this section by first covering some ServiceNow basics. We'll discuss important topics like releases, environments, and update sets. We'll also discuss the ServiceNow stack, or group of technologies, that comprise ServiceNow. Then we'll go over some important concepts like tables and their relationships, fields, and field types. inside of ServiceNow records and reference fields. We'll then jump into Service Now, where I'll show you how reference fields work. Once we've covered those core concepts, we'll be ready to jump into ServiceNow development, where I'll provide a brief introduction. We'll then discuss when scripting is and isn't necessary, and after that we'll discuss JavaScript and the scripting environment within ServiceNow.

We'll end the section by covering background scripts, the ServiceNow Studio, and some additional resources that will be beneficial to you. So let's get started with some basics. Note that if you've recently watched my ServiceNow101 course or feel like you have a solid understanding of the following topics, feel free to skip to the next video. So what is ServiceNow? Well, ServiceNow is a software-as-a-service platform. ServiceNow uses a subscription model, so customers subscribe or purchase licences for a given set of users. If someone at an organisation says they have service now, they don't physically own the source code or have it installed somewhere. They simply have a ServiceNow subscription or group of subscriptions. ServiceNow started in the IT service management space, where it quickly grew and almost monopolised the industry. But it didn't stop there. ServiceNow currently has a presence in It.service management, IT operations management, IT business management, application development, security, operations, human resources, and much, much more. If you want to learn more about what ServiceNow can do, I recommend visiting ServiceNow.com for a complete list of all products. So what do you get when you purchase a subscription? ServiceNow will give you an instance, which represents a few things. An instance represents a specific URL through which you access your instance through.It also represents the instance data that is stored in the hosted database servers, any application logic, and any custom components. We'll discuss the ServiceNow stack in a bit,but for now, just know that ServiceNowusesa MySQL database on the back end. Due to this, almost everything in ServiceNow is stored as a record in a table. Within an instance database, an incident is stored as a record in the incident table. A business rule is stored as a record in the business rules table, and so on. Whenever you hear the phrase "Out-of-Box" and the "ServiceNow world," this refers to the state of an instance when ServiceNow first spins it up. So what comes with the core platform, or what is loaded out of the box?

A lot of Service Now best practises represent the idea of maintaining an instance that is as close out of the box" as possible. If you have an instance and you have tonnes and tonnes of customizations and complex things going on, it can make it much more difficult for upgrades and maintainability. Over the years, ServiceNow has made a lot of changes to their IT service management processes within the tool based on customer feedback. So if you think of it as the ServiceNow tool, such as Incident, Problem, and Change, representing industry best practices, and you want to make some complex configurations and customizations to it, then you should really be asking yourself: Is my process that much different than the hundreds or even thousands of other customers out there? If ServiceNow in its "Out of the Box" state represents an industry best practise and follows ITIL best practices, should I be changing my process? And as a consultant, a lot of the time it's my job to provide the customer with this insight. I've seen this time and time again, where a customer's complex configurations and customizations come back later only to bite them in the bum when they look to upgrade or use new tools or applications like the new Service Portal. So while you, the developer, are capable of creating some very complex customizations and changing the service now to do anything you want, it's not always recommended. Right now, let's talk a little bit about releases. So, just like any other application you've used, ServiceNow uses what they call releases to group together a number of changes to the core platform. ServiceNow is on an approximate twelve-month feature release cycle. At the time of this recording, Istanbul is the current General Availability release. This means that new customers will receive instances in the Istanbul release. The feature releases are named after cities around the world. So to the right is a list of past and future releases, along with their release year. The ServiceNow release schedule is composed of feature releases, which contain new features and new applications; patch releases, which contain a collection of problem fixes; and finally, hot fixes, which are usually fixes for specific problems that are implemented very, very quickly. A patch release may contain many hot fixes.

To check the release version of an instance, simply type Stats followed by the enter key in the Application Navigator. This will bring you to a page which shows you all kinds of useful information about a given instance. although it depends on your licence contract. Customers typically receive three environments from ServiceNow. They'll receive a production instance, a test instance, and a development instance. The reason for these three instances is so administrators and developers can customise and develop on the platform without jeopardising production data. Typically, development is performed in the development environment. Once work is complete there, it is pushed to the test instance, where users go through a user acceptance testing phase. Once testing is complete, the changes are then pushed to production. As an admin, you have the ability to clone instances. So for example, if the development instance starts to drift far from the production instance, and by that I mean the processes and configurations and customizations in the development instance are not representing the current processes and configurations in the production instance, then you may request the development instance be cloned from the production or test instance. So you would essentially be taking the mirror image of your production instance and cloning that down to development. So then development would mirror the production instance. At that point in time, it's best practise to keep all instances as similar as possible, especially the test and production instances, since when you test new updates, you want to be testing those updates in an instance that is as similar to the production instance, if not identical to the production instance, as possible. All right, now let's talk about update sets. So you might be asking, "How do I push changes from dev to test or prod?" Well, this is accomplished via update sets. Update sets are used to record most customizations and configurations, with most being the keyword here. If you are ever in doubt, I highly recommend going to ServiceNow documentation to verify what gets captured and what doesn't get captured. Almost everything inside of Service Now is stored as a record in a table. If you modify a business rule or client script, you are really modifying the business rule or client script record in their respective tables. Update sets are XML snapshots of the last record modified.

So if you were modifying a business rule, the update set would just contain the most recently modified business rule record in XML format. Update sets also have versions, and you can merge two or more update sets into one. If two update sets have modified the same record and you merge those two update sets, the merged update set will contain the last modified record. When you load an update set, say to a production instance, you can preview the update set before committing the update set.This will catch the majority of compatibility issues if they arise. Now, let's quickly discuss what's captured and what's not captured in update sets. Customizations like client scripts, business rules, and UI policies are captured in update sets. Tables and fields are captured, reports and workflows are captured, and forms and form modifications are captured. So what is not captured? Well, data is not captured, such as new records in an incident table or a change table. So new incidents, new problems, new users, new groups—all of these are not captured. New CIS are not captured in the CMDB, and schedules are not captured either. Again, if you are ever hesitant about what is captured or not, I recommend reviewing the ServiceNow documentation. Also, just because something is not captured in an update set doesn't mean that you can't still import it into another instance. There are methods like exporting the XML record and then importing it into another instance. In the instance, this is commonly done with groups. All right. And finally, we'll end this video by discussing the Service.Now stack.

So the ServiceNow stack or group of technologies that comprise ServiceNow consists of Apache Tomcat webservers, J, two EE application servers, MySQL databases, and the Mozilla Rhino JavaScript engine. This is not an exhaustive list, but it should give you a general understanding of the platform and core technologies that ServiceNow was built on. The ServiceNow data centres consist of thousands of servers that take on the roles of load balancers, web servers, application servers, database servers, and much, much more. The general flow of traffic when, say, a client wants to access a specific incident would be that their request goes over the Internet and finally lands in the ServiceNow data center. The first thing their request might hit is a load balancer, which determines which servers have extra resources to allocate to process this request. Once a load balancer finds an idle web server, it will send the request to the web server. The Web server would do some processing and send the request to an application server. The application server is what would do a lot of the core logic and generate the SQL to then be passed to the database server, where a specific incident would be queried in the incident table. Then the database server would hand the application server that information. The application server might hand that response to the web server, where it's packaged up and finally sent back through the Internet to the client. Again, there are probably hundreds of tech technologies involved with ServiceNow since it's such a huge platform, but this group of technologies here represents the core systems used.

2. Tables

Hello and welcome back. In this video, we'll take a look at tables, their relationships, and then we'll dip into service. I'll now show you a few tips on table management. So let's get started. Each ServiceNow instance includes more than 20 Out-of-the-Box tables. The majority of these tables relate directly to the applications inside of ServiceNow. Each application has one or more tables. For example, there is an incident table for the incident application, and there are hundreds of CMDB tables for the CMDB or configuration application. Each table contains many fields, which we'll go over in the next video. Tables can extend other tables as well. We'll discuss table extensions here in the next few slides. There is also a naming convention used for the tables and ServiceNow. All table names are lowercase and use underscores instead of spaces. However, tables do have human-readable labels, which may contain capitalizations and spaces. If a developer creates a table, it will be prefixed with an underscore and then the name of the table. With an admin role, we can create and modify existing tables. So here at the bottom we can see my custom table. On the left is the table label. The actual table name, however, is youunderscore my underscore custom underscore table. Table names are important when scripting, as we'll see within the next few sections. Now let's discuss table relationships. So in this diagram, we have a person table, a student table, and a faculty table. The person table is extended by the faculty and student tables.

We can also say that the person table is the parent table, and the student and faculty tables are the child tables. So why do we need a persontable at all? Why not just have a student and faculty table? Well, we could, but it would cause unnecessary redundancies. Since each student has a first name and last name, and each faculty member has a first name and last name as well, we can put those common fields in a parent table and inherit them. The person table can now hold all of the information that is shared by students and faculty. While the student table has fields that are specific to students only, and the faculty table has fields that are specific to only the faculty, An example for faculty-only fields would be something like salary. Extended tables also have the option to add dictionary overrides to their fields. Let's say the person table contains a userID field, which the student table inherits. However, when we refer to students in the student table, we would like the user ID field to actually be called the student ID. We can do this with a dictionary override, which overrides the person's user ID label with "student ID" only for student records. So faculty records would still have the inherited user ID label. Dictionary overrides are commonly used in the "out of the box" system with the task table and the task tables. such as incident, problem, change, request, et cetera Table relationships are critical in the CMDB. The CMDB application consists of hundreds of different tables, which are all related to one another. This allows ServiceNow to create what are called Business Service Maps.

So if a physical server goes down, we can see all of the other software and hardware that is dependent on that one server, such as an Exchange server. Due to table relationships defined in the CMDB, relationships can be either one to many, which is most common, or even many to many. An example of one-to-many relationships would be that every table has one or more fields. Every field belongs to only one table. An example of a many-to-many relationship would be that each user can have many groups, and each group can have many users. Now let's take a look at an example of table relationships within the CMDB. The majority of CI class tables extend the CMDB underscore CI table. For example, at the bottom of the diagram we have a Windows Server and Linux Server CI class table. Its parent table is more generally called cmdbci server or the server class. At the bottom right, we have a web application whose parent is a general application. Now let's quickly go over some of the most common tables and their names in ServiceNow. It's important to note that there are thousands of tables in service now, so it's not realistic to cover them all, nor are you required to memorise them for any particular reason. So first we have the Task table, which is the parent table for a number of tables such as the Incident table, the Problem table, and the Change Request table. The Task table stores common information such as a number field, a short description field assigned to a field, and assignment group fields.

Then the Incident, Problem, and Change Request tables all inherit these fields since they are children of the test table. We then have the Sys User table, which is where service now users are stored, and the SIS User Group table, where the groups in service now are stored. The SIS User Role Table stores all of the roles in ServiceNow. We also have a CNN underscore Location table, which stores all of the platform's locations. The platform's core company table is used to store companies or organizations. We then have our knowledge management tables. So we have KB underscore Knowledge, which stores the actual knowledge articles, KB underscore Category, which stores the knowledge categories, and KB stands for Knowledge Base, which stores the knowledge base records. Then we have some of the core service catalogue tables, such as SC request for the requests, Secreck item for the request items, and SC Task for the catalogue tasks. We also have SC catalogues for the service catalogues and SCC items to store the actual catalogue items. Then I have two CMDB tables, the Cmdbci, which is an apparent table to many other tables, and the Cmdbci Server table, which is both a child of the Cmdbci table and a parent to many of the child server tables. This isn't an exhaustive list by any means, but just a short list of what I consider to be some of the core services. In reality, there are many other service catalogue tables, a part of the service catalogue application, and knowledge management tables, a part of the knowledge management application.

The Tables and Columns module can be a great one-stop shop for information about a particular table. The list on the left shows all tables within the system ordered by their label. The list in the middle shows all fields on a specific table. Finally, the list on the right shows attributes for a specific field. It also allows you to launch the schema map of a particular table. The Schema Map is a visual diagram that shows table relationships. We can focus on a table, and the schema map will show all tables that extend or are extended by the focus table as well as referenced tables. In the image, we can see the focus table, Incident, which has a relationship to Incident, Task, Sys, User, and a number of other tables. Now let's take a look at these modules within ServiceNow. So to start with, we'll go to the Tables and Columns module, and here on the left we can see a list of all of the tables in the system. So we'll scroll down and select Incident, and the middle column shows us all of the fields on the Incident table. When we select a field or column name, the column attributes are displayed on the right side. So all of the attributes associated with this specific field can also be added to reference fields. So, for example, the company field here is a reference field. So if we click the plus button, we can directly access all of the related fields on that reference table. If I click the Schema Map button, this will load the Schema Map with the Incident table as its focus. So here on the left, we can see all the tables that are referencing the incident table. And on the right, we can see all the reference tables in the Incident table. We can also expand the columns on the incident table and even expand the task columns. Since the Incident table extends the Task table, we can also focus on another table by right clicking and selecting Focus on this table. Now this has the Task table as the focus table, and we can see here that there are many tables that are related to and referenced by the Task table.

3. Fields

Hello and welcome back. In this video we'll talk about records and fields in ServiceNow. Before we get into records and fields, I'd first like to talk about an important concept in ServiceNow, and that's the globally unique identifier. The ServiceNow wiki states each record in ServiceNow is identified by a unique 32-character globally unique ID called a sys ID. In software development, we often need a way to reference an exact record or data structure. And in order to reference an exact record, we must need some type of unique identifier. This is commonly referred to as a globally unique identifier. However, in the service now offered, this is referred to by the SIS ID. An example of a sys ID is as follows: it looks a little bizarre at first because it's a 32-character hexadecimal string. So in this example we have EF 4225, a 40, etc. For SIS. IDs are used all throughout the system and are very common in scripting within ServiceNow. If you are referencing a specific incident in a script and you need a way to reference that again and maybe another script or just another function, you can do so by using the SysID to point to that exact incident. SYSIDS are commonly paired with a tablename to locate a specific record. So for example, if you have the system ID of a record in addition to the table name in which that record is stored, you can use these two values to quickly find that specific record.

So for example, if you wanted to reference a specific incident and you had that SysID, you could use the SysID plus the table name, in this case incident, to quickly query and locate that incident. Now, in theory, because sys IDs are unique, you could find that record just by using the sys ID. But it turns out that it's much more efficient and quicker to find that record by adding the name of the table. All right, now let's discuss databases, tables, and fields. So a database contains many tables, and a table contains many fields. So the incident table might have the field's number for the incident, the caller's number for the caller associated with that incident, and a short description for the short description for that incident. So the incident table contains many fields. In the fields I just listed, records are stored in tables. So in the screenshot below, we have a list of records that are stored within the Incident table. The columns in this screenshot represent the fields on the incident table. So by looking at this list, we can see that the incident table has the fields created number, short description, category, and opened by. So if we use the analogy of a spreadsheet, we could say that the rows from a spreadsheet translate to the records in a table and the columns of the spreadsheet translate to the fields on the table. So an individual cell refers to a specific record field value. So, for example, the second record in this list is Inc. So again, records are stored in database tables. Records represent a single entity defined by a table's fields. So, what makes a specific record unique are the field values associated with that specific record. Each record has a unique key, the Sys ID.

So if you wanted to reference this Incident Record, you could do so in a script by referencing the SysID, which is this EF 4225 A, et cetera. Hexadecimal street. Now let's talk about fuel types in ServiceNow. ServiceNow has many different field types. We can leverage and use string field types, date field types, time field types, choice field types, true and false field types, list field types, HTML field types, and even scripting field types in custom applications and reference field types. There are other field types within the platform, but this is a list of the more commonly used field types. So what are "reference fields"? Well, the ServiceNow docs state reference fields store a reference to a specific row in another table, similar to foreign keys and SQL. So if you're ever looking at a form of a specific record and you see the magnifying glass shown on the right by the caller field and the location field, these represent reference fields in ServiceNow. So in this screenshot, you can see that we're on the Incidents form view. However, there's a field on the incident table called Caller that's actually referencing the SysUser table. When I begin typing a name here, it retrieves a list of records from another table in the Sys user table. Same for location. It turns out these reference fields are a fundamental building block for applications within ServiceNow. These reference fields give us the flexibility to create relationships between records. So, for example, if the Location field was just a plain text field, a string field, then we wouldn't have consistent data because maybe every help desk technician has a different way of entering a location. Maybe some people use all caps or all lowercase, some people wouldn't put a comma after the city, maybe some people wouldn't even add the state at the end, et cetera. However, if we create a reference to the location table, and as long as the location table is already populated, then within the incident's record, we're actually storing a reference to that specific location. So then we have the integrity of that data. In every field, popular reference tables are the user table, location table, and CI tables. However, any table may be referenced by another table.

References are everywhere in the platform, and it turns out that the Sys ID is stored in the referenced field. So again, if we're using the example of an incident record, that incident record has a field called Caller ID, which references the Sys user table. Well, if I have Mark Miller as the caller ID, it's Mark Miller's SysID that's actually being stored in that referenced field. Even though it uses the display value of Mark Miller, it's the actual Sys ID that's being stored there. Reference fields must match an exact record. If you're ever typing in a reference field and you get the red background shown in the screenshot here, that means that there is no exact match for the text in that field. So this would imply that there's no user in the SIS user table that has the name of Jane. Finally, if we want to filter the referenced records, we can do so by using reference qualifiers. So maybe in the Caller field we only wanted to pull active users from the SIS user table. If a user is marked inactive, maybe they've retired or something like that, then we don't want to give the user the ability to reference those records. All right, now let's quickly take a look at reference fields and ServiceNow. So if I go to the Incident table, we'll go to Open Incidents and navigate into a specific incident. We can see that there are magnifying glasses next to the Caller field, the Location field, the configuration item field, as well as the Open by Assignment group and assign two fields.

So if I right-click on Caller and click on Show Caller ID, I can see information about this specific reference field. I can see that the field name is "Caller ID" and that it's a type reference, and it references the Sys user table. If I show the Location field, we can see that this is a type reference, and it references the CMD underscore Location table. If I click the information icon next to Location, I'll be taken into this related record. So here I am on the CNN Location Table, viewing the Columbus, Ohio location record. I'll go back to the incident, and now I'll go to the Configure table and I'll search for the column Caller. So if I go into the dictionary entry for the Caller field on the incident table, we can see that I have a reference field where we specify the user table and that we can apply reference qualifier conditions. So, if we only wanted to see Active users, we could set Active to True and then add any other filters to the user table. If we go to the top, we can see that this is of type reference.

4. Development Introduction

Hello and welcome back. In this video, we'll finally go over an introduction to scripting and ServiceNow. So, scripting in the service now is extremely powerful. We can actually leverage existing APIs, so we don't have to reinvent the wheel. Now, we'll explore APIs in the next section, but for now, you can think of APIs as an abstraction to do a common task. So a lot of the time we want to access a specific record in a table and make an update to that record as the developer, instead of writing out that entire process in JavaScript and then writing the SQL to make the initial queries and then the SQL to make the updates, etc., etc. Like, it turns out that there is an API, or application programming interface, available to us to make that job much, much easier since it's such a common task to perform. These existing APIs and ServiceNow are grouped into glide classes. Scripting in ServiceNow is very flexible. There's really little you cannot customize, as the ServiceNow wiki states. The ServiceNowglide classes expose JavaScript APIs that enable you to conveniently work with tables using scripts. Using the Glide APIs, you can perform database operations without writing SQL queries, display UI pages, and define UI actions. So you can think of these APIs as building blocks. They provide a blueprint to do a common task. Again, we'll talk more about APIs in the following sections within this course, but for now, just be aware that they provide a framework to do common tasks.

So when is scripting necessary? While ServiceNow gives us the flexibility to customise just about anything via scripting, it's not always necessary. Usually, configurations and customizations can be done without any scripting at all. It turns out it's actually best practise to avoid scripting when not required. For example, if you would like to show or hide a field on a form depending on whether or not another field is populated, you could do this by scripting a client script. However, it's best practise to do this via a UI policy. So generally, the 80/20 rule applies to scripting and ServiceNow. 80% of the time, you can accomplish what you are trying to do without scripting, and roughly 20% of the time scripting is required. Depending on what you're doing, this may be closer to 60 40, 70 30, or even 90 10. If you are building a lot of custom applications and/or integrations, you may be closer to 60 40.However, if your organisation is trying to followas closely to out of the box aspossible, it may be closer to 90 ten. So customising without scripting includes UI policies, workflows without scripting activities, creating new tables, and creating new fields. Scripting is necessary when you need to do more complex things like creating integrations, creating complex business rules or client scripts, creating UI actions or complex transform apps, or creating service portal widgets or custom applications. One of the reasons ServiceNow has been so successful is due to just how easy it is to configure and customise the platform. ServiceNow is constantly evolving the platform, and there are a lot of configurations and customizations that can be applied without any scripting at all. So again, if you can achieve a configuration without scripting, that's generally considered best practice. Now, I'd like to quickly cover the differences between client-side and server-side scripting. If you took my ServiceNow 101 course, then the slide will look quite familiar.

So this is an important concept, not just for ServiceNow, but really for any web application. Web applications are very different than your standard desktop applications, such as Microsoft Excel or a photo editor such as Photoshop. Desktop applications store the application data, such as a spreadsheet or a photo, locally on your computer's hard drive and are processed using your computer's CPU as opposed to web applications, where the data and processing happen in a data centre throughout this section and the rest of the course. When I talk about client side, I'm referring to the browser you, the user, use to access services. Now, whether it be your desktop, laptop, phone, or tablet, When I talk about server side, I'm referring toServiceNows data centres where the application servers and databaseservers are located and instance data is stored. Anytime you want to access data in ServiceNow, the client or browser makes a request to the servers in the ServiceNow data centre over the Internet. The application server receives the request and communicates to the database server, where the data is stored. Once the application server receives the data from the database, the server will package it up in an HTTP response and send it back to your browser via the Internet. Your browser then processes this data and renders it on the screen. Now, let's take a look at an example. Let's say we are viewing a single incident record. The client side has limited access to instance data. For example, because we requested information about a specific incident, the server sends us a response with only data related to that specific incident. If we wanted to view or access more instance data, such as another incident, a request to and from the servers would be required. So this is what I mean when I say that on the client side, we have limited access to data. We only have access to the data that is sent back to us from the servers by the service.

Data centers, or server-side computing, are now extremely powerful, but data transfer requires network activity. This naturally takes a bit of time to travel over the Internet. The time it takes for a packet to leave your computer, reach ServiceNow's data center, and then return back to your computer is called the roundtrip time and can be important when troubleshooting network issues. Keep in mind that no matter how fast your Internetis, there will always be a slight delay due tothe round trip time on the client side, we haveaccess to the current form fields and values, UI elementsor the Dom, the Document Object model, and any clientside APIs on the server side. We have access to the database-server-side APIs and script includes. All right, now let's talk about the programming language we, as a developer, use in ServiceNow. So one of the awesome things about service now is that there's one language we use, JavaScript, on the client side as well as the server side. This makes it very easy for the developer. Wikipedia states JavaScript is a high-level, dynamic, untyped, and interpreted runtime language. JavaScript is prototype-based with first-class functions, making it a multiparadigm language supporting object-oriented imperative and functional programming styles. Now, that's quite a mouthful, and a lot of these keywords are out of the scope of this course. But just know that it's an object-oriented programming language and is interpreted as opposed to being compiled. JavaScript is not Java. They are two completely different programming languages. There's actually a really interesting history to JavaScript, and the creators wanted to piggyback off of the popularity of Java at the time, which is why they used the word Java in JavaScript.

But keep in mind that these are two completely different languages. It just so happens that ServiceNow is written in Java. So JavaScript was originally developed to be a client-side scripting language, and because of this, it's supported in every modern browser. Usually when you hear the phrase JavaScript on the server side, you'll come across NodeJS, which is a relatively new runtime environment for executing JavaScript on the server side. However, in the world of ServiceNow, they use MozillaRhino as a runtime environment for executing JavaScript. JavaScript has seen a lot of growth over the past few years due to Node JS and its relatively easy learning curve. It's actually one of the most popular programming languages in the world, and it's the most popular on GitHub. However, it's also one of the most misunderstood languages. If you would like to know more about this, I highly recommend checking out the book JavaScript the Good Parts by Douglas Crockford. All right, so now let's talk about the scripting environment and ServiceNow. So again, anytime we're writing server-side JavaScript, it's being executed in the Mozilla Rhino runtime environment. With the version of Mozilla Rhino that ServiceNow is using, we can use ECMAScript Five features. However, we cannot use the latest ECMAScript Six or even Seven features. So keep that in mind when writing JavaScript code. within the scripting environment. We have access to the ServiceNow API as well as any third-party libraries. So if we're writing client-side code, we have access to Angular JQuery and other libraries as well. Now, let's quickly discuss background scripts. Background scripts are a location in ServiceNow where we can run server-side code on demand. It's similar to a browser's console, and it's a great place to experiment. And it turns out we'll actually be using background scripts for a lot of the serverside code we write in this course. Within a background script, we have access to the service now via APIs. It's important to note that background scripts should be used with extreme caution due to performance impacts and possible data loss. If you are ever deleting records through background scripts, I highly recommend first logging those records to the screen before issuing the delete command to verify that you're deleting the correct records. The ServiceNow Studio is an integrated development environment, or IDE for short. You can think of it as a one-stop shop for all configuration records that makes development and service much easier. However, Studio is only available for scoped applications and cannot be used on the global scope, so it can only be used when creating custom applications. Because of this reason, we'll only use ServiceNow, Studio, and Section Ten when we create our custom application.

Now, there are a few important concepts that I want to go over before we end this section. Number one is the variable naming conventions. Within ServiceNow, it's common to use underscores. In vanilla, an example of a variable Hello World would be Hello World all lowercase. Camel case is typically used in JavaScript, so hello capital W World. Now, you can use either or, but generally, if I create a new variable in a script, I'll use the Camel case convention, and if I'm referencing an existing variable in ServiceNow, I'll use the underscore convention. Another important concept is the SysID, and although we've already covered this, I just want to reiterate that it's a 32-character, globally unique identifier, and every record in the system has one. So every table, every field, et cetera, has a system ID. The last important concept I want to discuss now is the difference between a field display value and the actual field value. Most fields are actually objects, not strings. So, for example, in the screenshot to the right, we have a variable field, which is a JavaScript object. The variable field has two properties: value (help underscore Disk) and Displayvalue (help space Deskor the display value for this field).

So if we want to access the display value for a given field, we can actually use the Get Display Value method. Now, we'll cover this in much more depth within the following sections, but I just want to bring it to your attention that there is a difference between the field display value, which is generally user-friendly and consists of spaces and capitalizations, and the field value, which should not contain spaces. Finally, we'll end the section with additional resources. Because JavaScript is a prerequisite for this course and, unfortunately, is beyond the scope of this course, I highly recommend the following resources if you are unfamiliar with it or need a quick refresher: JavaScriptresourcesCodecademy is a great free resource, and CodeSchool is a great paid resource. There's also JS Ben or JS Fiddle for testing your JavaScript logic within the browser, and two amazing books I highly recommend any JavaScript developer to read, the first one being JavaScript The first is Douglas Crockford'sThe Good Parts, and the second is Eloquent JavaScript. There's actually a free version of Eloquent JavaScript online, so definitely check out the link provided here. In addition to JavaScript resources, there are also a number of amazing services now available. There's the ServiceNow YouTube channel, the API documentation website, the JavaScript Primer PDF, which is linked here, and many other third-party websites. Throughout this course, I'll list additional resources, and I'll have an iPad Additional Resources PDF available at the end of this course, which aggregates all of the additional resources listed in this course.

Hide

ServiceNow CAD Exam Dumps, ServiceNow CAD Practice Test Questions and Answers

Do you have questions about our CAD ServiceNow Certified Application Developer practice test questions and answers or any of our products? If you are not clear about our ServiceNow CAD exam practice test questions, you can read the FAQ below.

Help
Total Cost:
$84.98
Bundle Price:
$64.99
Download Now
accept 80 downloads in the last 7 days

Purchase ServiceNow CAD Exam Training Products Individually

CAD Questions & Answers
Premium File
151 Questions & Answers
Last Update: Mar 19, 2024
$59.99
CAD Training Course
54 Lectures
Duration: 8h 35m
$24.99

Why customers love us?

90%
reported career promotions
92%
reported with an average salary hike of 53%
94%
quoted that the mockup was as good as the actual test
98%
quoted that they would recommend examlabs to their colleagues
Download Now
accept 80 downloads in the last 7 days
What exactly is CAD Premium File?

The CAD Premium File has been developed by industry professionals, who have been working with IT certifications for years and have close ties with IT certification vendors and holders - with most recent exam questions and valid answers.

CAD Premium File is presented in VCE format. VCE (Virtual CertExam) is a file format that realistically simulates CAD exam environment, allowing for the most convenient exam preparation you can get - in the convenience of your own home or on the go. If you have ever seen IT exam simulations, chances are, they were in the VCE format.

What is VCE?

VCE is a file format associated with Visual CertExam Software. This format and software are widely used for creating tests for IT certifications. To create and open VCE files, you will need to purchase, download and install VCE Exam Simulator on your computer.

Can I try it for free?

Yes, you can. Look through free VCE files section and download any file you choose absolutely free.

Where do I get VCE Exam Simulator?

VCE Exam Simulator can be purchased from its developer, https://www.avanset.com. Please note that Exam-Labs does not sell or support this software. Should you have any questions or concerns about using this product, please contact Avanset support team directly.

How are Premium VCE files different from Free VCE files?

Premium VCE files have been developed by industry professionals, who have been working with IT certifications for years and have close ties with IT certification vendors and holders - with most recent exam questions and some insider information.

Free VCE files All files are sent by Exam-labs community members. We encourage everyone who has recently taken an exam and/or has come across some braindumps that have turned out to be true to share this information with the community by creating and sending VCE files. We don't say that these free VCEs sent by our members aren't reliable (experience shows that they are). But you should use your critical thinking as to what you download and memorize.

How long will I receive updates for CAD Premium VCE File that I purchased?

Free updates are available during 30 days after you purchased Premium VCE file. After 30 days the file will become unavailable.

How can I get the products after purchase?

All products are available for download immediately from your Member's Area. Once you have made the payment, you will be transferred to Member's Area where you can login and download the products you have purchased to your PC or another device.

Will I be able to renew my products when they expire?

Yes, when the 30 days of your product validity are over, you have the option of renewing your expired products with a 30% discount. This can be done in your Member's Area.

Please note that you will not be able to use the product after it has expired if you don't renew it.

How often are the questions updated?

We always try to provide the latest pool of questions, Updates in the questions depend on the changes in actual pool of questions by different vendors. As soon as we know about the change in the exam question pool we try our best to update the products as fast as possible.

What is a Study Guide?

Study Guides available on Exam-Labs are built by industry professionals who have been working with IT certifications for years. Study Guides offer full coverage on exam objectives in a systematic approach. Study Guides are very useful for fresh applicants and provides background knowledge about preparation of exams.

How can I open a Study Guide?

Any study guide can be opened by an official Acrobat by Adobe or any other reader application you use.

What is a Training Course?

Training Courses we offer on Exam-Labs in video format are created and managed by IT professionals. The foundation of each course are its lectures, which can include videos, slides and text. In addition, authors can add resources and various types of practice activities, as a way to enhance the learning experience of students.

Enter Your Email Address to Proceed

Please fill out your email address below in order to purchase Certification/Exam.

A confirmation link will be sent to this email address to verify your login.

Make sure to enter correct email address.

Enter Your Email Address to Proceed

Please fill out your email address below in order to purchase Demo.

A confirmation link will be sent to this email address to verify your login.

Make sure to enter correct email address.

Still Not Convinced?

Download 12 Sample Questions that you Will see in your
ServiceNow CAD exam.

Download 12 Free Questions

or Guarantee your success by buying the full version which covers
the full latest pool of questions. (151 Questions, Last Updated on
Mar 19, 2024)

Try Our Special Offer for Premium CAD VCE File

Verified by experts
CAD Questions & Answers

CAD Premium File

  • Real Exam Questions
  • Last Update: Mar 19, 2024
  • 100% Accurate Answers
  • Fast Exam Update
$59.99
$65.99

Provide Your Email Address To Download VCE File

Please fill out your email address below in order to Download VCE files or view Training Courses.

img

Trusted By 1.2M IT Certification Candidates Every Month

img

VCE Files Simulate Real
exam environment

img

Instant download After Registration

Email*

Your Exam-Labs account will be associated with this email address.

Log into your Exam-Labs Account

Please Log in to download VCE file or view Training Course

How It Works

Download Exam
Step 1. Choose Exam
on Exam-Labs
Download IT Exams Questions & Answers
Download Avanset Simulator
Step 2. Open Exam with
Avanset Exam Simulator
Press here to download VCE Exam Simulator that simulates latest exam environment
Study
Step 3. Study
& Pass
IT Exams Anywhere, Anytime!

SPECIAL OFFER: GET 10% OFF. This is ONE TIME OFFER

You save
10%
Save
Exam-Labs Special Discount

Enter Your Email Address to Receive Your 10% Off Discount Code

A confirmation link will be sent to this email address to verify your login

* We value your privacy. We will not rent or sell your email address.

SPECIAL OFFER: GET 10% OFF

You save
10%
Save
Exam-Labs Special Discount

USE DISCOUNT CODE:

A confirmation link was sent to your email.

Please check your mailbox for a message from [email protected] and follow the directions.