1 Overview

This topic provides information on OBX and OFS.

This document provides a feature-by-feature comparison between OBX and OFS to clarify functional parity, highlight improvements, and document how OBX capabilities are being implemented in OFS. For each feature we outline the equivalent capability in OFS and the current implementation status along with any known limitations or planned enhancements.

Table 1-1 Enhancements or Limitations

Sr. No.	OBX	Oracle Financial Studio
1.	Standalone Component	Standalone components, widgets, virtual pages are supported. These components are generally used within other components which acts like screens or as standalone screens. For detailed explanation of how to create standalone components, refer to Section 4.3
2.	Maintenance Screens	OFS supports Maintenance screens to address specialized business use cases by building them as a combination of two web components: Summary screen and Maintenance screens of all steps. Standard framework features such as audit information and built-in menu actions (for example, New, Copy, Unlock, etc.) are available by default. In OFS, both Summary and Detail components can be created quickly using the guided component and UI generation flow, with straightforward endpoint mapping for data persistence, making Maintenance flows easy to develop and consistent with OBMA standards. Refer to Section 4.4
3.	Data Segments	Each step in a maintenance screen is a Data Segment. New Data Segment UI be created and attached to existing Maintenance screens. Refer to Section 4.1
4.	Standalone Service	In OFS, service creation is achieved through a UI-driven creation flow. Users can select Standalone Component – Service Creation and provide the required object and field details directly in the UI. OFS then generates the complete service artifacts following the OBMA architecture. Refer to Section 2.2
5.	Maintenance Service	Maintenance Services are used for Maintenance Screens with multiple Data Segments. Multiple business objects can be created based on the number of Data segments in the Maintenance. Each Data Segment will then have its own service. Refer to Section 2.3
6.	Data Segment Service	Data Segment services are used to plug new Data Segments into already existing Maintenance Screens. Data Persistence of that Data Segment is done through the mapped Service. Refer to Section 2.1
7.	Creation of Child Data-segment (Resource Segment) and Configuring in existing data-segment flow using screen-class maintenance	This feature enables the creation of a Data Segment to capture and persist data for a specific stage within a Maintenance screen flow. The Data Segment is implemented as an independent unit with its own data source and backing service, ensuring clear separation of concerns and easier maintenance. Once created, the Data Segment’s UI and service are integrated and plugged into an existing Maintenance screen, allowing the Maintenance flow to be extended without requiring changes to the core screen structure. Refer to Section 7
8.	Changes in Generated Components	Users can edit components that were previously created using OFS. OFS supports updating key aspects of an existing component, including labels, data bindings, layout configuration, and other component-level properties, enabling teams to refine the UI and behaviour as requirements evolve. Refer to Section 4.6
9.	Batch Extensibility	Not Supported
10.	Validation/ Processing Logic Extensibility	Not Supported
11.	Extending the common UI infra methods using Pre post hooks	Not Supported
12.	Overriding base endpoint with custom endpoint	Not Supported
13.	Extending base labels	Not Supported
14.	Support for addition of custom columns and custom filters in Task based screens	Not Supported
15.	Dynamic data configure feature for LOV	Not Supported
16.	Process Workbench - For extending kernel conductor based workflows/ Creation of custom workflows	NA
17.	UDF - (Additional Attribute Services)	Not Supported