Which three statements are true about activities?

The assertion that limiting activities to fewer than 25 steps is true is rooted in best practices for maintaining code clarity and efficiency within Pega applications. Activities with excessively many steps can become unwieldy, difficult to understand, and challenging to maintain. Keeping the number of steps to a manageable limit helps ensure that the logic is more transparent, which in turn supports easier debugging and future modifications. This guideline encourages developers to break down complex processes into smaller, more manageable pieces, facilitating better organization and reuse of logic.

The idea that one should use standard activities whenever appropriate is also a good practice. Standard activities are built-in and designed to handle common tasks, which helps in leveraging existing functionality and minimizing the need to recreate already available methods. This not only streamlines development but also ensures compatibility and support across Pega versions since standard activities are often maintained and updated by Pega.

While the use of the Log-Message method is indeed useful for logging purposes, there are various methods available within Pega for different scenarios and using this method specifically is not necessarily a standard requirement for activities. Similarly, the suggestion to always use custom methods does not align with best practices as well. Utilizing built-in features enhances reusability and consistency, whereas over-reliance on custom