What is the term for the framework used to structure capabilities like properties and activities in Pega?

The term that describes the framework used to structure capabilities such as properties and activities in Pega is the concept of a class. In Pega's object-oriented approach, classes serve as the fundamental building blocks. They define the structure and behavior of various components or entities within the application. For instance, a class can encapsulate data and methods that represent specific properties and activities related to that entity, enabling better organization and reusability of these components.

Classes in Pega utilize the inheritance feature, allowing subclasses to inherit characteristics and behaviors from parent classes. This structure promotes a clear hierarchy and facilitates the management of business logic across different levels of the application. Consequently, it enhances maintainability and scalability of Pega applications as they grow over time.

Other terms, while relevant in their contexts, do not fit the specific role of establishing the framework for organizing properties and activities as effectively as classes do. The application serves as the overall project framework, modules are functional groupings that can encapsulate distinct sections, and layers often refer to the different levels of abstraction or implementation strategies within an application. However, it's the class that directly structures and encapsulates the capabilities leveraged in Pega's environment.