Construction Kit for Digital Business

A12 follows a modular approach when it comes to creating business applications. While business logic, validation rules and the structural layouts of user interfaces are encapsulated in models, the following building blocks are responsible for bringing the A12 applications and their models to life.

A12 Client

Model driven components in the center of the client side application enabling declaration of core application aspects, modules, navigation, screens and major interaction patterns.
They take care of request handling, data retrieval and processing, state management and orchestration of lower level components like UI engines.

A12 Engines

Model driven UI components based on Plasma UI/UX concept and the Widget library implemented in Typescript and React. This covers currently forms and overview, require configuration by models but also provide a programming API in Typescript.
Read more…

Widgets

Widgets are reusable, lower level UI components like grids, trees or datepickers that follow the Plasma Design conventions and UX concepts.
Read more…

A12 Kernel

Definition of documents and document models along with modeling tools.
A domain specific language for model based computation and validation incl. parser, runtime components and a programming API in various languages.

A12 Services

Service API and implementations to deal with models and documents supporting creation, retrieval, update, deletion and querying.
This is provided in Typescript for the client side and Java for client and server side.
It comes along with client/server communication, authentication, authorization, computation, validation, persistence, indexing, versioning and locking.

A12 Workflows

A12 Workflows provides a lightweight service, which integrates Business Process Model and Notation (BPMN) modeling capabilities into A12, enabling graphical modeling of server-side workflows and their execution.
The A12 Workflows service can be enabled as an addition to other A12 products and integrates seamlessly into the A12 architecture.
In this way, documents may serve as input and output for an A12 workflow and the UI for user tasks can be modeled using the existing A12 modeling approach.

Wenn Sie auf der Seite weitersurfen, stimmen Sie der Cookie-Nutzung zu.
If you continue to visit the site, you agree to the use of cookies.
Privacy Policy / Cookie Policy

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close