In Pega, how does an embedded property differ from a top-level property?

An embedded property refers to a data element that is nested within another property, typically associated with a data model that captures more complex information structures. This contrasts with a top-level property, which stands alone and is directly accessible at the root of an object or case type.

In the context of user interfaces, embedded properties do not have a direct representation in user forms or displays. Instead, they are often used within a context or related structures that are brought together in a UI layout. This makes them less visible and directly manipulated by users compared to top-level properties, which are readily accessible and interactable in the UI.

The nature of embedded properties is essential for organizing data and defining relationships, but it inherently limits their visibility until introduced through parent objects or structures, thus explaining why the answer regarding their invisibility to the user interface is accurate.