Field: In the context of Pega's App Studio, a field represents an individual data element that can be placed on a user interface. In Dev Studio, the corresponding rule type for a field is a Property rule, which defines the characteristics and behavior of a single piece of data that can be used in various parts of the application, such as forms, data objects, or calculations.
Goal and deadline: This term in App Studio refers to the objectives and time frames associated with a task or a case. The counterpart in Dev Studio is a Service-level agreement (SLA) rule. An SLA rule in Pega defines the time goals for the assignment, stages, and processes in a case, including the deadlines and what actions should be taken if those are not met.
User: In App Studio, the term user typically refers to the human end-user interacting with the application, often associated with a specific role or set of permissions. In Dev Studio, a Operator rule is used to define the characteristics of a user, including their credentials, roles, skills, preferences, and the access group(s) they belong to.
Persona: A persona in App Studio is a semi-fictional character created to represent different user types that might use a service, product, site, or brand in a similar way. When translating this to Dev Studio, it aligns with an Access group rule. An access group in Pega is a rule that defines a set of application roles, permissions, and other settings that correspond to the needs and permissions of a particular type of user or persona.
