Abstract: The present disclosure involves systems, software, and computer implemented methods for defining and using a system metamodel for an event-driven cluster of microservices. A deployment package that includes metadata definitions is received for a microservice. The metadata definitions include: a reference to a service; a reference to a resource entity served by the service; a reference to an event subscribed to by the service; a reference to a micro frontend that provides a user interface for the service; and a reference to an API for performing operations on the resource entity. The microservice is deployed, which includes including the metadata definitions in a system metamodel graph. The microservice is activated, including generating at least one event corresponding to including the metadata definitions in the system metamodel graph. In response to a request for metadata for the microservice, the system metamodel graph is traversed to retrieve the requested metadata.

Abstract: The present disclosure involves systems, software, and computer implemented methods for deploying micro frontends to different clusters from a single repository. One example method includes receiving, by a user interface (UI) deployment service running in a runtime cluster, a name and hash of a UI module to deploy. The module name and hash are used to update a shell service database used by a shell service serving applications for the runtime cluster. A manifest is generated for the runtime cluster using the updated shell service database. The UI deployment service stores the manifest in a manifest repository in a cluster-specific folder. A manifest location value in the shell service database is updated to refer to the cluster-specific folder, to enable the shell service, in response to an application request to load the UI module, to access the manifest to determine a UI bundle file name for loading the UI module.

Abstract: The present disclosure involves systems, software, and computer implemented methods for deploying micro frontends to different clusters from a single repository. One example method includes receiving, by a user interface (UI) deployment service running in a runtime cluster, a name and hash of a UI module to deploy. The module name and hash are used to update a shell service database used by a shell service serving applications for the runtime cluster. A manifest is generated for the runtime cluster using the updated shell service database. The UI deployment service stores the manifest in a manifest repository in a cluster-specific folder. A manifest location value in the shell service database is updated to refer to the cluster-specific folder, to enable the shell service, in response to an application request to load the UI module, to access the manifest to determine a UI bundle file name for loading the UI module.

Abstract: The present disclosure involves systems, software, and computer implemented methods for defining and using a system metamodel for an event-driven cluster of microservices. A deployment package that includes metadata definitions is received for a microservice. The metadata definitions include: a reference to a service; a reference to a resource entity served by the service; a reference to an event subscribed to by the service; a reference to a micro frontend that provides a user interface for the service; and a reference to an API for performing operations on the resource entity. The microservice is deployed, which includes including the metadata definitions in a system metamodel graph. The microservice is activated, including generating at least one event corresponding to including the metadata definitions in the system metamodel graph. In response to a request for metadata for the microservice, the system metamodel graph is traversed to retrieve the requested metadata.

Abstract: A computer-implemented system may include reception of a user interface package at a client device, the user interface package including layout information and a data model, the layout information conforming to a user interface model of a backend service provider and the data model conforming to a business object model of the backend service provider. The layout is rendered at the client device based on the user interface model, data input to the rendered layout at the client device is received, the data is stored at the client device in conformance with the business object model, and the data is transmitted from the client device to the backend service provider.

Abstract: A computer-implemented system may include reception of a user interface package at a client device, the user interface package including layout information and a data model, the layout information conforming to a user interface model of a backend service provider and the data model conforming to a business object model of the backend service provider. The layout is rendered at the client device based on the user interface model, data input to the rendered layout at the client device is received, the data is stored at the client device in conformance with the business object model, and the data is transmitted from the client device to the backend service provider.

Abstract: Disclosed are methods, systems and products, including a computer implemented method that includes obtaining by at least one of a plurality of entities at least one master template available to the plurality of entities to generate documents from the at least one master template. The at least one master template includes at least one template area, with each of the at least one template area being associated with a respective data type. The method also includes generating a document by the at least one of the plurality of entities based, at least in part, on the at least one master template using entity-specific data associated with the at least one of the plurality of entities for the data type associated with the at least one template area.

Abstract: A program and corresponding method allow for the enablement of customizable extension fields into a form template, independent of the field type of the extension field. New extension fields corresponding to section headers of the form template can be created and added to a user interface. A new extension field can drive the form template and be added to all applicable section headers in the form template from the user interface.

Abstract: A schema builder includes a read service for reading data from a multi-node hierarchical deep schema configured database and a write service for writing data to the multi-node hierarchical deep schema configured database. A transformation module transforms schemas between multi-node hierarchical deep schemas and a flat schema, and stores meta data to record a structure of the multi-node hierarchical deep schema.