ServiceNow Training

Upon the successful completion of the ServiceNow course you will be able to:

• Develop modules and tables in the ServiceNow 
• Able to handle the data import and export tasks in ServiceNow 
• Learn Integration of ServiceNow with multiple web services. 
• Install and test MID Server.
• Understand the process to develop pages and sites. 

To take up this course you need to have a basic working knowledge of database, Javascript and cloud computing.

This ServiceNow training can be learnt by the professionals or aspirants who have a basic knowledge of Cloud computing.

• ServiceNow is one of the widely acce[pted ITSM tools by the organizations across the globe. 
• There has been a drastic growth in the number of job opportunities available in this ServiceNow domain. 
• According to payscale.com the average salary received by a ServiceNow professional is $111371 per annum. 

Yes, upon the successful completion of the ServiceNow training you will receive the course completion certificate from SK Trainings. This certificate is valid across all the top MNCs and simplifies your job search process.

Yes, you will get all assistance from the ServiceNow experts to clear your certification exam. Moreover you will be provided with the experts designed ServiceNow course material to clear your certification exam.

• Type of users
• User interface
  • Banner frame,

  Content and understanding of terms.

  • Application navigator

  Modules and Applications, searching.

  • content frame

  Welcome page, homepage, service catalog

• Form header, fields, sections
• List title bar, breadcrumbs, column heading, fields
• Searching tools

List, Global text search, knowledge base, navigator filter

• Self-Service
• Knowledge management

Roles, concept

• Reports

• Design a service catalog
• Understanding different fields concept
• Creating variable.
• Different types of variables.
• Understanding of order, mandatory, default value
• Create a reference field.

• Understanding difference between client script and business rule
• g_form concept
• get and set values.
• Making a field readonly, mandatory, visible
• Concept of UI Policy
• Designing UI policy and client script
• Difference between UI policy and client script

• Gliderecord understanding.
• Table hierarchy
• Sys id concept
• Understanding business rule

• Cockpit Basics
• Product Cockpit
• WCMS Cockpit
• Smart Edit
• Customer Service Cockpit
• Import Cockpit

• Understanding display business rule
• Debug business rule(addInfoMessage and logs)
• Script includes
• Async and sync difference

• Notification
• Events and queue
• Email templates

• Sent/outbox
• Received/inbox
• Inbound email actions
• Dot walking concept

• Number maintenance
• List of records
• Update set(creating and migrating)
• Understanding XML concepts
• UI Macro

• HTML concept
• UI Page
• Using UI page in a service Catalog.
• Container concept in service catalog.

• UI action
• Table creation and extension
• List view of records
• OOB fields and “u_” concept

• Display field concept
• SLA
• Schedule and business day concept

• Workflow

• Survey
• Data source
• Transform map
• Coalesce concept

• Localization concept
• Enable plugins
• Concept of web service

• Web service
• SOAP
• Scripted web service

• Data Policy
• Difference between Data and UI policy
• Debuggers

• Delegate
• Views
• Relationships

• Order guide
• Record producer

• Discovery and CMDB
• JSON and Jelly
• REST web service

• Cloning
• Resource management

• Interview Preparation
• Certification preparation

CMDB stands for Configuration Management Database. CMDB is a repository. It acts as a data warehouse for information technology installations. It holds data related to a collection of IT assets, and descriptive relationships between such assets.

Data lookup and record matching feature helps to set a field value based on some condition instead of writing scripts. For example: On Incident forms, the priority lookup rules sample data automatically. Then, set the incident Priority based on the incident Impact and Urgency values. Data lookup rules allow to specify the conditions and fields where they want data lookup to occur.

Following steps will help you do the same:

• Navigate to “Application Menus” module
• Open the respective application.
• Set value for active as ‘true’ to enable it or set it to ‘false’ to disable it.

An ACL is access control list that defines what data users can access and how they can access it in ServiceNow.

Dictionary overrides provide the ability to define a field on an extended table differently from the field on the parent table. For example, for a field on the Task [task] table, a dictionary override can change the default value on the Incident [incident] table without affecting the default value on Task [task] or Change [change].

UI policies dynamically change information on a form and control custom process flows for tasks. UI policies are alternative to client scripts. You can use UI policies to set mandatory fields,which are read only and visible on a form. You can also use UI policy for dynamically changing a field on a form.

UI policies dynamically change information on a form and control custom process flows for tasks. UI policies are alternative to client scripts. You can use UI policies to set mandatory fields,which are read only and visible on a form. You can also use UI policy for dynamically changing a field on a form. Client script sits on the client side(the browser) and runs on client side only.Following are the types of client script:

• OnLoad()
• OnSubmit()
• OnChange()
• OncellEdit()

Business rule is a server side script. It executes each time a record is inserted, updated, deleted, displayed or queried. The key thing to note while creating a business rule is, when and on what action it has to be executed. The business can be run or executed for following states

• Display
• Before
• After

The Task table is the parent table of Incident, Problem & Change. It makes sure any fields, or configurations defined on the parent table automatically apply to the child tables.

Glide record is a java class. It is used for performing database operations instead of writing SQL queries.

A transform map transforms the record imported into ServiceNow import set table to the target table. It also determines the relationships between fields displaying in an Import Set table and fields in a target table.

When an import makes a change to a table that is not the target table for that import, this is when we say foreign record insert occurs. This happens when updating a reference field on a table.

It is used to enhance the system logs. It provides more information on the duration of transactions between the client and the server.

Domain separation is a way to separate data into logically-defined domains. For example a client ABC has two businesses and they are using ServiceNow single instance. They do not want users from one business to see data of other business. Here we can configure domain separation to isolate the records from both business.

The HTML Sanitizer is used to automatically clean up HTML markup in HTML fields and removes unwanted code and protect against security concerns such as cross-site scripting attacks. The HTML sanitizer is active for all instances starting with the Eureka release.

A gauge is visible on a ServiceNow homepage and can contain up-to-the-minute information about current status of records that exists on ServiceNow tables. A gauge can be based on a report. It can be put on a homepage or a content page.

Each update set is stored in the Update Set [sys_update_set] table. The customizations that are associated with the update set, are stored in [sys_update_xml] table.

Homepages and content pages don’t get added to ‘update sets’ by default. You need to manually add pages to the current ‘update sets’ by unloading them.

Performance Analytics is an additional application in ServiceNow that allows customers to take a snapshot of data at regular intervals and create time series for any Key Performance Indicator (KPI) in the organization.

It is a unique 32-character GUID that identifies each record created in each table in ServiceNow.

Performance Analytics is an additional application in ServiceNow that allows customers to take a snapshot of data at regular intervals and create time series for any key performance indicator (KPI) in the organisation.

You can, but there is no guarantee of sequencing. You cannot predict what order your event handlers will run.

next() method is responsible to move to the next record in GlideRecord. _next() provides the same functionality as next(), intended to be used in cases when we query the table having a column name as next.

Applications in ServiceNow represent packaged solutions for delivering services and managing business processes. In simple words it is a group of modules which provides information related to those modules. For example Incident application will provide information related to Incident Management process.