S e r v i c e N o w: Oversimplification
Neeraj Mishra

Neeraj Mishra @syncrofosatron

About: I wanna be the Gandalf of Coмpuтers!

Location:
India
Joined:
Feb 27, 2021

S e r v i c e N o w: Oversimplification

Publish Date: Aug 5
0 0

Tables Records Fields |   

No no, there isn't an embed error in this article, I'm just trying to give an abstract depiction of how I see ServiceNow, fundamentally (and it probably is this way).
Everything is an object, within another object, within another... Well, as long as it needs to be.

We can say that a Table is the biggest object there is, or like a container then we have records within it, which are like sub-containers, and finally, even more containers within those sub-containers.

A very simple analogy, now let's take a look from programming perspective.

Suppose we have a table for video games. Then we have all the video game records, each of which contains various records.

const video_game = {
    id: "some 32-character hex string", // very important identifier
    created: "date/time",
    created_by: "someone",
    // and so on...
    video_game_records : [
       {
            id: "i am unique 32-character hex id for identification",
            name: "Prince of Persia: The Warrior Within",
            released: "2004",
            rating: "M",
            // ...
        },
        {
            id: "i am unique 32-character hex id for identification",
            name: "The Witcher 3: Wild Hunt",
            released: "2015",
            rating: "18+",
            // ...
        },
        // ...
    ]
};
Enter fullscreen mode Exit fullscreen mode

See?
The various key-value pairs within video_game_records and video_game_records sits within video_games.
Nested objects.

And if we try to visualize how this would look in ServiceNow, well, no need to visualize, as here are the visuals:

The key-value pairs (id, name, released, rating) function as Field on a web-page; together, they make up a Record and all of these are stored in a Table.
And, we can have many such tables—for books, movies, toys, electronics—and we have ways to reference them from one table to another.
However, modifying records in another table is protected: you would need additional permissions to do so.

I hope this helps you simplify your understanding.
And what we learn from all this? Well, it is that how something—though it may appear grand in scope—is fundamentally based on these simple concepts.

Comments 0 total

    Add comment