Cloud UI in Your Environment
What is a Cloud UI Application?
enosix Cloud UI is built around the concept of individual applications — each one purpose-built to surface a specific SAP process inside your host environment. For example, the Variant Configuration UI (VC UI) provides a guided interface for configuring complex products using SAP Variant Configuration, while the Sales Document UI (SalesDoc UI) enables users to create and manage SAP sales orders and quotes without leaving their host application.
Each Cloud UI application is independent and focused on a single area of your SAP workflow. Applications are designed so that introducing a new one — or updating an existing one — has no effect on the others. As enosix grows the platform, new applications become available to you without any changes to your existing deployment.
From a user's perspective, all applications share a consistent look and feel. From an implementer's perspective, they all follow the same deployment model and configuration pattern, so experience with one application transfers directly to the next.
How Applications Load
Cloud UI applications are loaded on demand. The host application specifies which Cloud UI application to load by passing a query parameter in the iframe URL. Cloud UI reads this value on startup and fetches only the code for that application — the rest of the platform is not downloaded until it is needed.
This means the initial load is fast and consistent regardless of how many applications are available. If a user never opens the SalesDoc UI during a session, it has no impact on performance. If they do open it, it appears quickly with a brief loading indicator before rendering.
As enosix adds new applications to the platform, your deployment does not grow heavier over time.
How Applications Communicate
Cloud UI applications run inside an iframe embedded within your host application (such as Salesforce or ServiceNow). Since the iframe and the host page are separate browser contexts, they communicate through a secure, structured message channel — a browser-native mechanism for passing information between isolated windows without exposing either side to the other's internals.
When the embedded application loads, it establishes a dedicated message channel with the host page. From that point on, the host can send data to the application (such as a document number or user settings), and the application can send results back (such as a completed configuration or an updated order).
This architecture means your host application remains in control. It decides when to open the Cloud UI application, what context to provide, and how to handle the results — while the Cloud UI application handles all SAP interaction internally.