In Pega, what is a named business object used to define behavior called?

In Pega, a named business object used to define behavior is referred to as a rule. Rules in Pega are the building blocks of applications and represent established guidelines or parameters that govern the application's functionality. They define how various elements interact and behave within the system.

This includes configuring properties, processes, user interfaces, and many other aspects of the application. Each rule can be tailored to meet specific business needs, and rules can be reused and overridden based on the application design. As such, rules are essential for instilling business logic and flow into Pega applications, allowing developers to create responsive, versatile systems that align closely with business objectives.

The term "Instance" refers to a specific occurrence of a class or a specialized version of a rule, while "Class" is a blueprint from which instances or rules can be created. "Case" typically describes a specific scenario or instance of work that needs to be processed in Pega, focusing on work items rather than the rules that govern behaviors. Thus, the terminology in Pega has precise definitions, and understanding the role of rules is vital for effectively utilizing the platform.