ServiceNow
Workflows

IT Workflows
Employee Workflows
Customer Workflows
Creator Workflows

IT Workflows
We offer workflows that can transform IT into a fully-fledged growth engine. Take advantage of the benefits of operational flexibility by increasing workforce adaptability...
Read More

Employee Workflows
Make employee experiences more integrated and engaging with ServiceNow Employee Workflows. Motivate your staff by making it simple for them to obtain what they require when they require it...
Read More

Customer Workflows
We connect clients, front-line agents, middle and back-office staff on a single ServiceNow platform with ServiceNow Customer Workflows using digital processes to scale customer operations...
Read More

Creator Workflows
With a low-code platform, you can quickly create digital workflow apps. Scale quickly across the organization to build natural, linked experiences that users enjoy...
Read More

Solutions
ServiceNow Solutions

IT Service Management
IT Operations Management
IT Asset Management
Governance, Risk, and Compliance
Security Operations

HR Service Delivery
Customer Service Management
Field Service Management
Integration Hub

IT Service Management
IT service management includes all the ServiceNow services and processes that ensure end to end...
Read More

IT Operations Management
ServiceNow ITOM consists of a set of modules in ServiceNow to manage the operations...
Read More

IT Asset Management
It is the set of business practices to manage the lifecycle of various assets in IT like software assets...
Read More

Governance, Risk, and Compliance
Almost every aspect of the business is driven by governance, risk, and compliance...
Read More

Security Operation
To minimize risk, ServiceNow SecOps allows you to immediately identify, prioritize, and respond to threats...
Read More

HR Service Delivery
With ServiceNow HRSD, you can increase company productivity and provide your employees...
Read More

Customer Service Management
Proactively solve problems and take actions to rectify common requests more efficiently with ServiceNow...
Read More

Field Service Management
ServiceNow Field Service Management enables you to efficiently and safely manage field service activity...
Read More

Integration Hub
For the fastest time to value, lowest TCO, and ease of use with zero learning curve for all ServiceNow developers...
Read More

Digital Transformation
Digital Transformation

DevOps
Robotic process automation
User Experience Design

DevOps
Devops includes the set of practices that automates the IT operations and accelerate the delivery...
Read More

Robotic process automationt
We help organizations to integrate different techniques like machine learning and artificial...
Read More

User Experience Design
User experience design is the creation of the effective flow between users and software...
Read More

Product Engineering
Product Engineering

IT Consulting
New Application development
Product testing & QA
Re-engineering & Migration
Support & maintenance

IT Consulting
We help Companies to Better their IT infrastructure and to Implement various IT strategies. Alignment of all the services to boost the overall performance...
Read More

New Application development
We are an IT service provider company using high-value business processes and technical stacks to build digital products...
Read More

Product testing & QA
We help clients to deliver quality products and services. Skilled Quality Assurance Team to perform a series...
Read More

Re-engineering & Migration
Re-Engineering and Migration is the concept of Comparing the Existing business model to the desired model...
Read More

Support & maintenance
We provide a range of support and maintenance services to our clients in the form of version upgrades, post-project support...
Read More

,

A Mini Guide To Remote Tables – ServiceNow

  • By Balakrishna Mukka
  • August 17, 2020
  • 945 Views

Remote tables are another component that permits you to characterize a table inside ServiceNow. It also helps to interface it to an outer information source.

ServiceNow gets its records from running a related content against the outside information source.

These records live in memory, which implies they are clean after you leave the rundown/structure.

Before we go in detail with the remote tables. Let’s start with :

Why do we require remote tables?

Let’s try to see some usual challenges in data on Service-Now

  1. Complications to collaborate data distributed among various tables interrelated.

Usually we create a table, use Business Rules or scheduled jobs to maintain this data.

This approach has one big con which is small changes require modifications on multiple configurations such as data for an additional column.

  1. Handling of rarely utilized data from external sources.

Creating a table use schedule jobs to maintain these data and purge them on a regular basis or requirement. Con on this method is  inefficiency of data and API calls.

  1. Database views

They are use to combine two tables and have limitations such as advance conditions, access on records and much more.

Remote tables are the right solution for use cases mentioned above.

How do remote tables differ from regular tables?

  • Remote tables have a suffix “st” with their name using this we can differentiate a remote table and usual table.
  • Data for remote tables is cache and not store permanently. Using remote tables you are not utilizing your database storage rather data is cache in db to provide TTL.
  • Data can be generated when you are querying through scripts or viewing the table. No storage for data or handling of data for insertion and deletion.
  • Conditional based data generation.
  • Their details are store in Tables(sys_db_object) with Remote table check.
  • Values for Sys_id not generated by ServiceNow. It should generate logically.

Most important part is they support GlideRecord and ACLs like regular tables.

Requirements for using the tables?

Simply the below “plugin” is require and it comes to activate from Orlando.

Remote table

How to create it?

Remote Tables —-> Tables. 

OOTB remote tables
  1. Click on “New”.
  2. Provide Label name is automatically set to populate.
  3. Save the record.
 

You might have observed that once you save the file. The record.Sys fields are missing??

For remote tables sys_id is the only sys field we have and it’s not auto populate.

 

T new

  1. Create a definition.

Let’s try to have a look at the definitions.

Here is an example.
Remote Tables — > Definition.

In this definition it tries to pull interaction records with details such as portal source, language, device and application.

Here it just pulls data only when queries through a script which we “get” from a GlideRecord.

  1. Name: Name of your table/ details of the definition could be helpful.
  1. Table: Remote table name the definition applies to. One remote table can have only certain definition.
  1. Active: To stop/ run definition.
  1. Advanced: Advanced will provide a section to provide input for TTL.
  1. Script: Two parameters v_table & v_query.

Below is the sample definition create to show some data with a record that relates list of user groups and user.

v_table.addRow is use to create a record where object keys are field names and values are the values for records that will generate.

There is a catch here you cannot view this record as this data does not have any unique identifier. ServiceNow does not generate sys_id’s. You can provide unique identifiers (sys_id) of any value (not alphanumeric).

After modifying the definition with sys_id. You can even use sys_id of any existing data it should not lead to any database error as they are not store directly.

Working:

Remote tables require definitions to populate records. Definitions are scripts you can call an API or query tables to create JSON added as records.

How can we use remote tables?

v_query: API functions are as below:

 v_query.getEncodedQuery() – returns encoded query string example as below.

 v_query.getCondition(field) – returns encoded query string for the given field (includes field name, operator, and value)

 v_query.getParameter(field) – returns parameter for the given field (only includes value for equality conditions)

v_query.isGet() – returns whether the query is a single get by sys_id

v_query.getSysId() – returns parameter for sys_id field

 v_query.isTextSearch() – returns whether the query contains a text query parameter

 v_query.getTextSearch() – returns text search query parameter (internal field name 123TEXTQUERY321)

 v_query.getFirstRowWanted() – returns the first row to include

 v_query.getLastRowWanted() – returns the last row to include