The API Annexes are accessible through Industries Framework. An API Annex can be used as extension to the existing API. For a single API there can be multiple API Annexes.

The API resource lets you to define APIs that are accessible through Industries Framework. An API can be used to configure an adapter for a service that implements the API. An API can also be used to configure a listener for API events.

The Connection Descriptors resource lets you create, view, update and delete connection descriptors.

Export is used to move configuration data between different clusters.

Secrets API helps Tenant to store non public information like UserName, Password ..etc securely to the CXIF Vault.

The Feature Flags resource lets you view and update feature flags.

The operations from the Administration/Gatekeeping Rule Annexes category.

The Gatekeeping Rules resource lets you view gatekeeping rules and update them.

The exported configurable configurations can be imported into another cluster.

Captures the operations that create or update a routing interaction context. Such a context is a short-lived map of information that is retained in an in-memory cache as part of the Industries Framework. In case a routing target specifies that it requires the publishing of a key/value pair on the context, Industries Framework automatically extracts the relevant information from the request and response and either creates or updates such an interaction context. The call to the request source is then receiving the ID of the interaction context via the ORA-INTERACTION-CTX custom HTTP header.

The Listener Registrations resource lets you create, view, update and delete listener registrations.

List of the OpenID Connect servers that Industries Framework will interact with. This document appears both globally and on a per-workspace basis. Global documents are stored within the on-cluster control plane to describe for example the OIDC server that Fabric is secured with itself. Per-workspace servers are stored in a single respective document per namespace.

RoutingCriteria is a collection of different Criterias used by different end systems for routing. Will be used in RoutingMS to evaluate the criteria based on Incoming call.

The Stock Responses provide a static responses for the APIs. This resource lets you view, create, update, and delete stock responses.

The System Descriptors resource lets you create, view, update and delete system descriptors.

The Tenant Configurations resource lets you view and update tenant configuration. A tenant configuration object includes all configurations of a tenant or workspace.

The Utility Configurations resource lets you view and update utility configurations.

This document type describes the lookup of client application specific OAuth/OpenID Connect secrets that identify the client application on the various different AuthZ servers. It also references the secrets that are needed to sign OIDC token assertions.

Workspace is a collection of Industries Framework configurations. Will be used in identifying the workspace to which the Microservice needs the call to be routed to.

Each BLE can be triggered based on combination of an entity action (Create, Modify, Deleteetc.) and conditions that are provided by tenants or SI. Some of the examples- * Perform address validation when contact is created for a Party Account.
* Based on the Cart price, call a promotion calculation system like Pega and get available promotional discounts for the cart. Based on the discount Cart prices is updated..
* Shipping address is added to the header or items. As the address is added, tax needs to be calculated from an external system based on the address.
* A device is added to the cart. As a result there is a check required to an external (external to shopping cart) inventory to check if there is stock.
* An offer is added to the cart item with a base price. A call to the external system is made to get the price for specific account or account type to get the discounted price and update cart with the new price.
* When a customer is deemed as blacklisted, then an external system validated if such customers are eligible for the offers/plans added to the cart.

Defines Routing Status API for Industries Framework Routing service.

The Event Subscriptions resource lets you view, create, update, and delete event subscription records. An event subscription is a registration indicating that a particular event is significant to a particular system and specifying the processing to perform when the triggering event occurs.

The Individuals resource lets you view, create, update, and delete individual records. Individual is a person who has any kind of relation with the organization.

The Notification Listeners resource lets you view, create, update, and delete notification listener records. A notification listener is a class that listens to notifications and responds appropriately.

The Organizations resource lets you view, create, update, and delete organization records.

The User Management API lets you to create users in identity management systems that are compliant to SCIM 2.0. The API supports customization of the requested user to be created in the sense of custom attribute mapping and group allocation, based on the requested user profile and destination identity management system.