4.3 Standalone Screen

This topic provides information about the standalone screen used to independently display and manage specific functionalities or data within the system without dependency on other interface components.

A standalone screen is a single, independent UI page/component. It is used when the user can complete the task in one view without navigating through multiple steps.

1. Step 1: Component Creation

   What you do on this screen:

   • Select pattern type as Standalone.
   • Select product type (module context).
   • Enter name (technical identifier) and label (display name shown in the UI).

   Figure 4-8 Component Creation

   
   

   
   Description of "Figure 4-8 Component Creation"

   
   
2. Step 2: Endpoint Configuration

   Captures runtime configuration needed for the screen to work with data and behave correctly.

   What you typically configure (based on what is enabled in your OFS setup):

   • Endpoint or data source selection (where the screen reads/writes data).
   • Add a hosted swagger for endpoint mapping.

   Figure 4-9 Endpoint Configuration

   
   

   
   Description of "Figure 4-9 Endpoint Configuration"

   
   
   For each endpoint, add the required and optional parameters for each path in their swagger.

   Figure 4-10 Edit API Parameters

   
   

   
   Description of "Figure 4-10 Edit API Parameters"

   
   
   The user can then optionally choose to generate the init function based on the configured path and parameters.
3. Step 3: Template Design

   Builds the actual UI layout using the designer editor.

   What you do on this screen:

   • Add containers/sections to define structure.
   • Add fields and controls for data capture/display.
   • Add tables/grids.
   • Configure buttons/actions (for example submit, cancel, next).
   • Set properties for each selected component in the right panel (text, behaviour, validations, display options).