BaaS connection point

Use the BaaS connection point to integrate user-defined BaaS services with ION. It supports secure, automated message exchange in both directions with limited manual configuration.

The BaaS connector establishes a standardized, secure, and reusable bridge between ION and BaaS services.

The connector enables secure, automated message exchange between platforms in both directions: from BaaS to ION and from ION to BaaS.

All configuration for the connector is defined in the BaaS service manifest. The connector minimizes manual configuration in ION.

Only one connection point is allowed for each service and instance combination. This restriction ensures that each connection point has a unique logical ID.

The BaaS connector is useful when integrating ION with cloud-native, BaaS-hosted services. The connector avoids the need to build or maintain low-level API integrations directly in ION.

Note: Backend as a Service (BaaS) is a licensed add-on feature that requires a separate license in addition to the Infor OS core license. Access to BaaS requires the appropriate entitlements and security roles and must be explicitly enabled for each tenant.

The BaaS connection point is available only in tenants where BaaS has been provisioned.

Creating a BaaS connection point

When creating the connection point, the UI displays the available BaaS services and their instances. Select the required service and instance.

You can specify these connection point properties.

Select Connect > Connection Point.
Click Add new connection point and add a BaaS connection point.
Specify this information:

Connection Point Name

User-defined name for the connection point.

Global Package Namespace

Select a namespace if it is relevant for the integration.
On the Configuration tab, specify this information:

Service Name

Select the BaaS service from the list of services deployed to the tenant.

Instance Name

Select the instance of the selected service. Multiple instances might be available.

Logical ID

Automatically generated from the service and instance names. Ensures uniqueness and restricts to one active connection point per combination.

Document properties

Documents are automatically populated from the BaaS service definition.

Documents are read-only in ION.

Documents are refreshed from the BaaS service definition when the list is refreshed.

Note: Documents, including webhooks, APIs, and functions, are managed in the BaaS service. If documents are not listed automatically, refresh the list.