Unlimited Applications, Unlimited Vendors
OpenDash360™ gives users access to an unlimited number of applications created by an unlimited number of vendors while still maintaining a similar user interface for easy interaction on both the backend and frontend.
To do this, OpenDash360™ takes custom web elements that have been generated by individual monolithic frontend applications and breaks them into microapplications/widgets that are then accessible for users.
Within OpenDash360™ multiple microapplications/widgets can run together seamlessly regardless of the language or framework they were created in.Visit OpenDash360.com
Within the context of OpenDash360™, individual custom elements take the form of either a MicroApplication or a Widget. The primary difference is presentation. Only one microapplication can be loaded and consumed by a user at any point, similar to how a Single-page Application (SPA) would function. Only one instance of any microapplication executes at any given time. Widgets, however, are presented globally. Several instances of the same widget or multiple instances of different widgets can be consumed simultaneously. Widgets can remain open during navigation events and are only unloaded when the user decides to close them.
In OpenDash360™, an Application is the “container” for a single microapplication, its supporting widgets, and any supportive assets. Applications are described by a project manifest. When an application is deployed to OpenDash360™, it is backed by an auto-generated SSO client containing developer-defined client roles. These client-roles provide a singular security context for all elements (its microapplication and widgets) of the Application. These client roles are mapped to realm-level roles as composites, which are in turn mapped to specific users. This allows application developers to only check for client roles within their application's respective client for the purpose of role-based security.
Within an Application, a Microapplication is the primary component. All primary
functionality and features should reside in the Microapplication. A microapplication
is a customized application built to let users perform a specific function
instantly. Unlike a traditional application, which is packed with multiple options
and a maze of functions, a microapplication is small in size and customer oriented,
built to provide specific functionality, has a simple user interface, and loads
dynamically bypassing app stores.
Widgets are simplistic and designed to provide a narrow, focused view of a subset of
a microapplication's features. Widgets are supportive content and should provide
OpenDash360™ also allows the creation of widgets to complement the existing functionality of microapplications. Widgets are essentially small, targeted applications that are tied to microapplication.
Users can view widgets while navigating any page in OpenDash360™ by floating them on their screen or by embedding them in their “Customizable Dashboard”.