4.1 Datasegment Screen

This topic provides information about the Data Segment screen used to view, manage, and configure data segment details within a system.

A Data Segment is a reusable, data-focused section of a maintenance RSO. It represents a logical group of fields or a small data capture/display area that can be embedded into maintenance screens.

1. Step 1: Component Creation

   Creates the base definition of the data segment.

   What you do on this screen:

   • Select pattern type as Data Segment.
   • Extended data segment: choose Yes/No (based on requirement and what your configuration supports).
   • Select product type.
   • Enter name and label.

   Figure 4-1 Component Creation

   
   

   
   Description of "Figure 4-1 Component Creation"

   
   
2. Step 2: Endpoint Configuration

   Links the data segment to runtime data and defines binding-related settings.

   What you typically configure:

   • Endpoint selection which has been created in the Service creation step.
   • DTO/object mapping or binding configuration.
   • The selected Endpoint will be used for data persistence.

   Figure 4-2 Endpoint Configuration

   
   

   
   Description of "Figure 4-2 Endpoint Configuration"

   
   
3. Step 3: Template Design
   Designs the reusable UI block in the designer.

   Figure 4-3 Template Design

   
   

   
   Description of "Figure 4-3 Template Design"

   
   

   What you typically do in the designer

   • Add fields and controls relevant to the data block.
   • Configure display behaviour and validations.
   • Map UI elements to Service DTO Fields.
   This page is the UI design workspace in OFS where you create or update a screen. You build the screen by dragging components from the left panel onto the central canvas and then configure each selected component using the settings panel on the right. It is mainly used to assemble the screen layout, set component properties (such as text, behaviour, and validations), and save the design so it can be published later. All database entries for the generated component are automatically added to the required tables after the user saves a component.

   Figure 4-4 Datasegment Component Summary

   
   

   
   Description of "Figure 4-4 Datasegment Component Summary"