How to make the property available for exposing
-
Declaring property as Exposed Property
-
By changing at DB
-
Property column visibility as Required
-
Not possible
A property is made available for exposing by setting its column visibility to Required. This configuration makes the property visible and accessible for external systems or reporting. Declaring as an Exposed Property is not the correct mechanism, and direct database changes are not recommended. The column visibility setting is the proper way to control property exposure.
This is Pega (PRPC) terminology. "Exposing" a property means making it a dedicated, optimized database column (via the Property Optimization wizard / Column Inspector) so it can be used in reporting and filtering. Before a property can be optimized/exposed it must satisfy the platform's column-mapping requirements (it must be a single-value scalar reachable on the class's page, with its column visibility/mapping set appropriately). Of the four options, only "Property column visibility as Required" reflects a genuine configuration step; "By changing at DB" (manual DB edits are not the supported path), "Not possible", and "Declaring property as Exposed Property" (there is no such declarative property flag) are not correct. The wording is a paraphrase of platform documentation and is awkward, so confidence is limited, but the marked answer is the most defensible.