Using tenants

Connection points can also be created during the modeling of a document flow as part of the details of the document flow elements. The Connection Points created during the modeling of a flow are automatically added to the shared list of connection points and can be reused.

A tenant is an isolated container of data. Tenants can be used to separate data from multiple customers in a SaaS (Software as a Service) or cloud environment. Tenants can also be used to separate data for a single customer, for example, separating data for a test environment from data from the production environment.

You can bridge the tenant container and allow sending and receiving agreed documents between two tenants.

For each connection point you can specify a tenant. If you only use the default tenant ( ' infor ' ) you do not have to specify this in your connection points.

The tenant becomes relevant in these situations:

• To use multiple tenants in an on-premises situation, for example for production data and test data, specify the corresponding tenants in the connection points. Mixing up data from these tenants is avoided.
• One tenant can be used per connection point. Additionally, all connection points in a document flow must have the same tenant.
• The tenant ID as specified in ION Desk is not validated. The ION Desk cannot check whether the tenant ID is specified correctly. For example, whether the tenant ID matches the tenant ID as used in the involved application.
• No specific codes or log settings can be used per tenant.
• Infor Application connection points do not change the tenant for messages that are retrieved from the outbox. The originating application is responsible for delivering the message in the context of the tenant of that connection point.
• For database, message queue, web service and file connection points, the tenant is specified in the produced messages. When the complete message is read from a message queue, the tenant defined inside that message is not changed.