Where should a section rule for a dashboard widget be saved?

Saving a section rule for a dashboard widget in the same class as the harness of the portal is important because it ensures that the section can be effectively accessed and utilized within the specific context of the portal. This approach allows for better organization and encapsulation of related functions and UI elements, promoting code reuse and maintainability.

When section rules are placed in the same class as the harness, it allows for straightforward access to the data context related to the dashboard. It also helps in leveraging class inheritance and the ruleset's structure, ensuring that the dashboard widget behaves as intended without running into issues related to class resolution or data access.

This method supports the Pega design principles of keeping related functionality together, optimizing performance, and maintaining clarity in the application architecture. Sections intended for dashboards are meant to be closely tied to the user interface's presentation, and placing them alongside the harness helps to facilitate this alignment.