DM Viewing The Data Model
DM Viewing The Data Model
LESSON
• Comprehensive view
• Displays data objects,
case types and data
types.
• Create data objects
• Access data objects
• Update data objects
• Fields
– Properties that store and format the data in
your application.
• Data sources
– Resources, which can be real or simulated, that
host the data.
• Field mappings
– Logic that links or transforms the fields in a
data source to the fields in an application.
Data objects
• The center of the diagram
displays the data objects in
your application. Click a data
object to display the Data
model tab of the Data Designer.
• For example, Address, Car,
Client and Person are data
objects.
Data objects
• Each row represents a data object, also referred to as a data type,
that defines and holds data for the application. Click a data object
to display the Data model tab of the Data Designer.
• For example, Address, Car, Client and Person.
Referenced by
• The Referenced By column
displays the case types and
data objects that reference the
data object.
• For example, the Client
reference the Car Insurance.
System of record
• The Systems of record column shows the system
or systems of record the data object uses. A
system of record is an internal or external system
that sources the data. The systems of record
referenced in the application are also displayed at
the top of the Integration Designer landing page.
• For example, the VehicleDetailsAPI system of
record sources the Car data object.
© 2022 Pegasystems Classroom Experience Training Materials 23
Action menu
Implementation
Actions menu
Delete data objects from the Actions menu.
Add a field
• Click the Plus icon to add a
field or data reference to a
case type or data object.
• For example, if the Car
Insurance case type is
selected, clicking
the Plus icon adds a field to
the Car Insurance case type.
11001010101110001
© 2022 Pegasystems Classroom Experience Training Materials 33
Best Practices
• Reuse data objects by promoting a built-on data object or copying the assets from a standard Data-
class.
• If your data source is unavailable, connect your data objects to simulated data in local storage.
• Repurpose data views instead of creating new ones when your system of record changes.
• Update data sources created in App Studio in Dev Studio only when necessary because some
changes made in Dev Studio make the rules un-editable in App Studio.
• Actively remove the data objects and fields that you do not use.
• Provide transformations to automate post-import changes to your data.
• Maintain separate environments for development, staging, production, and testing.
• Save import settings as a template to avoid manually mapping fields during future data imports.
Understand:
– the data model
– the relationships between data
objects, cases, and systems of
record
– how to view the data model
– the Integration Designer
– how to view the integration
landscape
– navigating the Integration Designer