About Oracle Cloud Applications BOSS REST Services

Learn about REST Data Source support for Oracle Cloud Applications BOSS REST Services.

Determining the REST Data Source Type

The URL of the Fusion Applications service you want to work with identifies which type of REST Service you want to create.

For example, if the Fusion Applications REST API you want to work with contains /api/boss/, you would create a REST Data Source with a Type of Oracle Cloud Applications (BOSS) REST Service.

In contrast, if the URL contains RestApi/resources/, you would create a REST Data Source with a Type of Oracle Cloud Applications (SaaS) REST Service. Consider the following examples: /hcmRestApi/resources/, /fscmRestApi/resources/, or /crmRestApi/resources/.

About BOSS REST Services

To build Oracle APEX apps that query, insert, update, and delete data from Business Object Spectra Service (BOSS) REST endpoints, create a new REST Data Source with a Type of Oracle Cloud Applications (BOSS) REST Service. Oracle APEX supports key BOSS features including:

• Business object endpoints (both top-level and nested child collections related by composition)

• Custom business object view endpoints

• Search view endpoints for optimized full-text searching

• Extraction view endpoints with optional bind parameters

In addition, this REST Data Source type supports BOSS endpoints that use:

• Restriction types

• Enumeration types

• Composite types

• Polymorphic results

The goal of this REST Data Sources type makes using APEX against a BOSS endpoint as easy as working with a local table while delegating a maximal amount of functionality for filtering, sorting, attribute selection, and pagination to the BOSS backend.