3.3 UI Design Patterns

This topic provides information about UI design patterns used to define reusable solutions for common user interface challenges.

OFS supports the following UI design patterns. Choose the pattern based on how the screen/component is intended to be used.

Standalone

Used to build an independent screen/component that can run on its own. Typically used for single-page experiences that do not require multi-step navigation.

Flow

Used to create a multi-step user journey (wizard-like navigation). Suitable when a process is broken into multiple screens/steps (for example, capture → review → confirm).

Widget

Used to create a small, embeddable UI component. Typically used for dashboard tiles, summary panels, or reusable visual blocks embedded within other pages.

Datasegment

Used to design a data-driven section of a maintenance screen, usually focused on capturing or displaying a related set of fields/records. Commonly used when a component represents a logical grouping of data that can be reused across screens.

Maintenance

Used for maintenance-style screens, typically aligned to create/view/update operations. Often used where you need structured layouts for summary/detail style interactions.