When is it appropriate to use page defined as a property for section include page context?

Using a page defined as a property for a section include page context is particularly appropriate when you want to read from embedded page properties. This means that the section can access and display values from a specific page that contains data structured in a particular way. When a section is included in a main page context and that section has been given its own page context property, it allows for effective encapsulation of the data related to that section, facilitating modularity and reusability in the UI design.

This approach effectively leverages the hierarchical structure of clipboard pages in Pega, where a parent page can contain embedded pages (child pages). By defining a section to use a page context property, you can target and read properties specifically from these child pages, improving data organization and reducing complexity when presenting or processing data in the application.

In contrast, reading from external APIs typically requires a more direct integration approach rather than through an embedded page structure. While local clipboard reads are common, the question specifically emphasizes the context of using nested pages in a section. Finally, while new properties can be created, the context of the question focuses more on accessing existing properties rather than property creation.