Which of the following cannot be made public in OutSystems?

In OutSystems, certain components and settings are designed with specific accessibility and security considerations in mind. Here, Site Properties and User exceptions cannot be made public, primarily due to the sensitive nature of the data they might hold and their impact on the application's behavior.

Site Properties typically contain configuration data that can vary between environments (like development, testing, or production) and may include sensitive information such as connection strings or API keys. Exposing such properties publicly could lead to security vulnerabilities or unintended application behavior if the properties are altered externally.

User exceptions, on the other hand, are used to manage and log errors that occur within the application. Making these exceptions public could compromise the application's error handling and provide insight into potential weaknesses or bugs in the system that an attacker could exploit.

In contrast, database entities, screens, and client actions can be made public as they typically represent the application's functionality that users interact with, and while care must be taken regarding what data is exposed, these components are designed to be part of the user experience.