Which of the following rules are not typically created or modified when creating a draft UI?

When creating a draft user interface (UI) in Pega Rules Process Commander (PRPC), it is common practice to focus on certain elements that directly impact the presentation and user experience. Among the types of rules mentioned, portals typically involve broader configurations that integrate multiple aspects of an application, including navigation, security, and layout for a suite of applications. They are not usually modified just for the sake of creating a draft UI.

Sections, harnesses, and flow actions, on the other hand, are specifically designed to structure the user interface and control interactions within the user experience. Sections are used to group UI elements, harnesses define the layout and functionality for those sections, and flow actions dictate what actions can occur when users interact with the UI. Therefore, these are often directly created or adapted when refining or developing a draft UI to ensure it meets the application's user interaction requirements.

In contrast, changes to portals are less common in the early stages of UI drafts, as they serve more as overarching frameworks for how applications are accessed rather than specific UIs detailing interactions or data presentation. This distinction makes portals an answer that aligns well with the question regarding which rules are not typically modified in the context of crafting a draft UI.