�ݺ�ߣ

<Application> Data Model
Updated: September 2023
Asset number: 0001407
Speaker Name

© 2023 ServiceNow, Inc. All Rights Reserved. 2
User instructions
• Who: This deck is built for delivery of a ServiceNow product/capability. The delivery of this deck may be undertaken
by Customers, ServiceNow Partners and ServiceNow Expert Services. Assigned Business Process Analysts and/or
Technical Consultants will normally be responsible for its delivery.
• Why: We want to make it easier for you by spending more time on the implementation and build, not creating
workshop materials. The purpose of this presentation is to outline the baseline process explaining the configurable
options with the objective of determining the to-be process and corresponding configuration requirements, usually in
the form of user stories
PLEASE REMOVE THIS SLIDE BEFORE PRESENTING

User instructions
• How:
– Customers (self–implementation) – use the deck as it is or add to your corporate template. Alternatively, utilize
individual slides to enhance your internal communications
– Partner or Co-Delivery implementations - use the deck and add your logo, following the instructions on a
following slide.
– ServiceNow Expert Services
– Remove the PartnerLogo using the �ݺ�ߣ Master (View > �ݺ�ߣ Master > select the vertical line and the
PartnerLogo at the bottom of the Master �ݺ�ߣ and delete. If you see any other instances of PartnerLogo just
follow the same process from that slide). If you have any issues, please contact the Now Create Team via the
Teams channel
– Tailor the presentation for the needs of your specific implementation

FAQs
• How can I provide feedback on this asset or other parts of Now Create? Now Create has several feedback buttons
throughout the portal, using the thumbs up/thumbs down buttons. Click on those icons and a small form will appear
for you to leave specific feedback regarding the asset you are accessing.
• If we use this deck, or slides from this deck, are we breaking any copyright? No. We designed this deck to be used by
our whole ecosystem.
• What should I do if I don’t need all of the content contained within this, or other assets? You can either hide or delete
the slide(s). You may also want to move the slide(s) to the end of the presentation, review it when you have finished
updating the asset for your own use, and then deleting any content you don’t need. Remember to regularly check
Now Create to make sure you have the most up-to-date asset.

Adding or deleting your Logo
To provide credibility to ServiceNow documents, the ServiceNow and
your logo should be visible, but not domineering.
Click View > �ݺ�ߣ Master > �ݺ�ߣ > Select Page 1
What to do:
• Download logos from the Brand Center site.
• Scale logos to an exact height of 0.45cm.
• Place your logos after the ServiceNow logo, divided by a grey bar.
• The same rule should be applied when more than one partner
logo is required.
What not to do:
• Do not scale logos beyond 0.45cm height
• Do not stack ServiceNow and Partner logos

Agenda

Agenda
Introductions
Data Modelling Introduction
Conceptual Data Model
• Create a Mindmap of ‘Objects’ and ‘Relationships’
Table Definition
• Building out the data model
Wrap-Up
• Review next steps
• Other outstanding topics

© 2023 ServiceNow, inc. All rights reserved. 8
Housekeeping

Housekeeping
• Start and finish on time
• Breaks will be taken as needed; approximately every two hours
• Return from breaks and lunch promptly. If late, catch-up during breaks or after Workshop
• Points needing greater detail will be recorded in a “Parking Lot” for later resolution
• All phones on vibrate. Please leave the room if you must take a call
• Avoid temptation to check Email. Please keep laptops closed unless taking notes or working on something for this
Workshop
• Active participation and passive listening
• Silence = ”I Agree”
• Everyone’s ideas are valued. There are no titles in this room
For in-person
workshops. Update
depending on your
location, e.g. you may
have to add fire exit
information

Introductions

Introductions
• Customer project team
– Name, Title
– Name, Title
• Partner project team
– Name, Title
– Name, Title
• ServiceNow project team
– Name, Title
– Name, Title

Introduction to Data
Modelling

Application Architecture
Under the Hood of an Application
Application
Presentation
Business Logic
Data

1. Define the Conceptual Data Model
2. Build out the Conceptual Model Objects & Relationships
3. Create the Logical Data Model
The Data Layer
Conceptual Data Model vs. Logical Data Model
Building the Data Model in 3 Steps

Conceptual Data Model
Using a Mindmap to create the Conceptual Data Model:
• Start with the core objective that the application is
facilitating
• Identify the objects and relationships that are linked
to
• Define the application as a network of Objects and
Relationships
Defining the conceptual data model
Event
User
Requester
Guest
Coordinator
Location
Is held at
Example: Event Management App

Building Out
Event User
Requester Coordinator
Location
Location the event is held at
Event Name
Event Number
Description
Date
Preparation State
Requester
Coordinator
Location
...
First Name
Last Name
Email
Department
Manager
...
Building
Street
City
Country
Manager
...

Building Out – Relationships
It is important to consider the relationships between 2 objects.
Cardinality  Cardinality refers to “the maximum number of times an instance of one object can relate to instances of
another object.“
Relationship Options:
Possible Relationship Scenarios:
1. One-to-Many
2. Many-to-One
3. One-to-One
4. Many-to-Many

Building Out – Fields
There are four categories of fields on a table:
1. Definition fields  Fields that are required to define the object itself
2. Reference fields  Fields that represent the links to other objects
3. Business Logic fields  These fields represent the business logic of the process
4. Reporting fields  These fields contain information and values that supports reporting
The initial focus during this workshop is on specifying the Definition and the Reference Fields.
Business Logic and Reporting fields are covered by following workshops.

The most common field types:
• Choice  Dropdown of choices
• String  Free Text field
• Integer  Numeric
• Reference  Link with another object
• Date  Date and Time
• Currency  Currency denoted according to system
settings
• True/False  Tickbox
• URL  Link to somewhere
• Journal  comments and notes

Most common field types
Choice
String
Integer
Date / Time

True/False
Journal
Currency URL

Reference

Building Out – Fields – Best Practices
Best Practices Considerations when selecting field types:
• Avoid unnecessary ‘Free Text’ fields and instead use Choice fields where possible in order to maintain the integrity of
data captured
• For relationships that are One-to-One, put the reference field on both ends
• Consider ‘hidden’ fields for storing relevant information that should not be visible

Application Data
Model

Draft the Data Model
Draft the data model in the two steps described:
Exercise 1: Draft the Conceptual Data Model
Exercise 2: Build out the Objects:
 Fields
 Values
 Relationships

It’s a wrap

Workshop Planning
Schedule for upcoming Feature Workshops:
• ….
• ….
• …
• …
Make sure the right participants are identified for each workshop!
Replace this slide with a
workshop schedule

Thank you!

App Engine - Data Model Workshop - Vancouver.pptx

�ݺ�ߣ

App Engine - Data Model Workshop - Vancouver.pptx

More Related Content

App Engine - Data Model Workshop - Vancouver.pptx

Editor's Notes