Differences in naming between App Studio and Dev Studio
When you create resources in App Studio, Pega Platform creates one or more rules and potentially classes. Dev Studio provides visibility into all the created records while App Studio usually exposes only objects with less complex configurations. In some cases, App Studio and Dev Studio refer to the same resource, but use different terms. By understanding the differences, you can better understand how Dev Studio stores the elements of your application that you create in App Studio.
The following table lists App Studio and Dev Studio terms with additional information, where applicable:
| App Studio term | Dev Studio term | Additional information |
| Data object | Data type | In Dev Studio, you work directly with data
types. For more information, see Creating a data object and Creating a data type in Dev Studio. |
| Field | Property | In App Studio, you add fields to data models and
views. The system creates a corresponding property that you can modify
in Dev Studio. For more information, see Configuring a data model for a case. |
| Landing page | Harness | For more information, see Harnesses. |
| New user | New operator ID | When you invite users to your application, Dev Studio creates a new operator ID and adds it to
an access group based on the developer role or persona that you specify
when you invite the user. For more information, see Inviting collaborators to your application. |
| People, users | Operators | In App Studio, both peopleand usersrefer to the actual end users of an application. |
| Persona | Access group | When you create a persona in App Studio, Dev Studio automatically creates a corresponding
access group. However, not all access groups in Dev Studio have corresponding personas in App Studio. For more information, see Learning about access groups and Managing access roles. |
| Single record data or case reference | Page property | You create data and case references when you create fields. This
complex field type uses a Page property to call a data page to source
either case or data references. Page properties must reference a data
type that defines the structure or the list of grouped fields. For more information, see Creating fields for capturing data. |
| Multiple data or case references (list of records) | Page List property | You create data and case references when you create fields. This
complex field type uses a Page List property to call a data page to
source either case or data references. Page List properties must
reference a data type that defines the structure or the list of grouped
fields. For more information, see Creating fields for capturing data. |
| Single record query | Page property | You create queries when you create fields. This complex field type
uses a Page property to call any desired data page accessible to your
application to source data. For more information, see Creating fields for capturing data. |
| Multiple queries (list of records) | Page List property | You create queries when you create fields. This complex field type
uses a Page List property to call any desired data page accessible to
your application to source data. For more information, see Creating fields for capturing data. |
| Single record embedded data | Page property | You embed data in a case when you create fields. This complex field
type uses a Page property without referencing any external data
sourcing. For more information, see Embedding data in a case. |
| Multiple records embedded data | Page List property | You embed data in a case when you create fields. This complex field
type uses a Page List property without referencing any external data
sourcing. For more information, see Embedding data in a case. |
| Team | Work group | In App Studio, you create teams in user interface
portals that include the My Teams widget. For more information, see Creating a team. |
| Work queue | Workbasket | Workbasket is a deprecated name for a work queue. You can still
encounter workbasket in Dev Studio in places such as out-of-the-box rule
names. For more information, see Defining work routing settings for an operator. |
Previous topic Defining application behavior