Developing a User Interface code for common actions is an exhaustive and repetitive task. FlexiCore Automatic UI provides out of the box Angular components making this task effortless. These components need to be embedded in your front-end code. Plugins and code for non-Angular front-end technologies will be provided in the future.
The key for Flexicore UI extensions is Dynamic Invokers. These back-end defined objects are instrumental in Flexicore supported UI technologies. More information on Invokers, Filters, and DyamnicExecutions is available on our support web site.
Using Dynamic Invokers and the related API’s Flexicore Grid, Tree, and dashboard presets can be used to show and edit data associated with any application domain without any front-end coding.
What is Automatic UI?
Automatic UI is a set of UI components and server-side services that enable user interface developers to present, edit, and create server-side objects without writing a single line of UI code.
Why use Automatic UI?
Automatic UI saves development time and is extremely well suited for plugin-based systems, where the implementations of a certain service may change at any point of time.
Automatic UI with FlexiCore
FlexiCore provides out of the box data-aware user interfaces (grid, dashboard, and tree) that can be associated with server-side data. FlexiCore allows adding custom actions and filters which results and rich domain-specific UI.
The lately added Flexicore support for UI side plugins brings modularity to front-end development in Angular.
The server provides the required APIs for maintaining existing and new UI side plugins at the back-end. This a fully generic User Interface can be customized to provide a modular context-specific user interface.
FlexiCore generic approach.
When a new set of plugins is developed to cover a specific application domain, developers can opt to expose its functionality through the usual REST API FlexiCore plugins support.
In addition, developers can define invokers and methods (see: search for Dynamic Invokers in the documentation)
Once invokers and their methods, filters are defined, a generic UI interface can create new data bounded widgets without any front end coding. Still, non-generic UI can be implemented using the API Flexicore and plugins expose. A generic User Interface can be customized using UI plugins filtered by context or by the class they are designed to handle.
When a generic approach is in use, changes in the back-end such as new workflows, entities, and functions are exposed at the front-end without a single change!
Ready to get started?