A new visual vocabulary
Each demo runs in its own iframe, as WebI does with HTML Custom Elements. Sample data is fictional. The controls inside the demos affect only that element.
What is actually feasible in WebI?
SAP already provides gradients, layout positioning and formula-based hiding for standard report objects. Custom HTML5 is a separate framed render—so we distinguish native controls from what happens inside our own element.
Premium 2.5D, not cluttered 3D
Layered gradients, subtle glass materials, crisp SVG icons, animated heights and hover depth without sacrificing legibility.
Rules inside a frame
A WebI measure can determine which sub-panels, recommendations, alerts or microvisuals the same Custom Element displays.
Reusable components
One SDK service can expose many visualization types with WebI format properties. Icon Atlas exposes many icons as one visual, not 24 separate entries.
A real service-shaped proof of concept
These endpoints follow SAP's Custom Element discovery, feeds, settings and HTML render request pattern. They have not been validated in a customer's CMC/WebI runtime yet.
Discovery: GET /api/visualizations
Formats: GET /api/formats
Element settings: GET /api/visualizations/icon-library/settings
WebI render: POST /api/visualizations/{id}/render (Accept: text/html)
For WebI pilot: configure an isolated Custom Elements service, test trusted HTTPS access, map real measures, verify iframe animation/security, and add a proper server-side PNG fallback for exports.