Which component is required to expose a service in Pega?

To expose a service in Pega, a service rule is mandatory. The service rule defines the specifics of the service, such as the service type (like SOAP, REST, etc.), endpoints, and associated parameters. This rule provides the framework and configuration needed for Pega to handle incoming requests and to process the associated business logic.

Service rules also contain definitions for how the service interacts with external systems, allowing for the integration of data and processes across different platforms. By implementing a service rule, developers can ensure that services are set up to meet the expected communication protocols and that they correctly map to the corresponding data and operations within the Pega application.

While data pages, activities, and connectors are essential in the context of a Pega application, they do not serve the same function as service rules. Data pages are used for accessing data, activities are processes that can perform a series of steps, and connectors facilitate communication to external systems. However, none of these components alone can establish a service for exposing functionality in Pega, which is where the service rule becomes crucial.