Features and Enhancements

Service API Creation & Management

Standardized API generation for multiple component categories including Data Segment, Individual, and Maintenance components, supporting consistent backend integration with UI screens.
Supported DTO field types: String, Number and Date (mapped to corresponding Java types and UI input controls).
Data Segment service creation: Generates services with base path /extensions/<service_name>, supports optional OBMA Rule Engine validation codes and auto-creates required database entries.
Individual component service creation: Generates services with base path /extensions/<service_name>, supports optional validations and auto-creates required database entries.
Maintenance summary component service creation: generates services with base path /<service_name>, supports optional validations, allows multiple DTOs (one per maintenance step) via Add New Business Object and auto-creates required database entries including Summary/Maintenance CCA names.
Import services: Upload a ZIP package of service artifacts from the Services screen to register services in the application.
Download services: Export one or more services as a single ZIP for storage/sharing/migration.
Edit services: Update an existing service by adding new fields. Existing fields cannot be modified (for example, one cannot change the data type of an existing field).
Delete services: Removes the service and all associated entries/records.

UI Designs (User Interface Designs)

Central module to create, import, edit, manage versions and publish UI design artifacts (Navigation: Dashboard → User Interface Designs).
List-page controls: Filter, Refresh, Import Screens and Create New Design.
Supported UI design patterns: Standalone, Flow, Widget, Data segment and Maintenance.
Edit Component: Select an artifact version, edit in designer, then save and republish.
Publish Component: Publish a selected design version to make it the published runtime version.

UI Pattern Creation (Key Workflows)

Data segment pattern: Create component → configure endpoint/DTO binding → design template by mapping UI elements to DTO fields. The required DB entries are added on save.
Process Flow Data segment: Flow-focused reusable data segment. Uses the same designer editor with pattern-specific initialization (init function).
Standalone screen: Create component → configure endpoint/data source (including hosted swagger mapping) → design UI layout and actions. Optional init function generation based on configured paths/parameters.
Maintenance Summary screen: Guided creation with endpoint and maintenance component/DTO configuration, step-wise template design and final summary review (including required query params and optional filter config).
Import Screens: Import UI designs via drag-and-drop package/file and refresh list to confirm availability.

Audit Logs

Centralized auditing of all API activity for OFS-generated components (including calls from OFS and App Shell).
Tabular view: Timestamp, method, endpoint, response status, origin (App Shell/OFS), duration and details including request/response payloads and exceptions. Supports filtering as well.
Visual overview: Top 10 most hit APIs, method distribution, common status codes and top 5 slowest APIs.

Integrated AI Assistant

AI features to reduce manual effort, improve standardization and enable automatic mapping between UI fields and service parameters/DTO fields.
Chat-based UI design generation: Generate UI templates from natural-language prompts (currently limited to a set of form-oriented OJET components), user then focuses primarily on mapping.
Chat-based UI + service workflow configuration: Conversationally define service and DTO fields. AI generates service artifacts, creates aligned UI inputs and performs automatic field-to-DTO mapping for persistence.

OBMA App Shell Integration

Published OFS components become consumable in the OBMA App Shell, enabling reuse of UI templates, bindings and persistence behavior within end-to-end application flows.
Supports extending existing Maintenance flows by plugging new Data Segments backed by mapped services for persistence.

2 Features and Enhancements