Abstract: Disclosed herein are system, method, and computer program product embodiments for creating and utilizing configuration providers for layered repository facilities. An embodiment operates by creating or loading a custom data structure for a software application, retrieving configuration information from at least one configuration provider, storing the retrieved configuration information in the custom data structure, and associating the custom data structure with the application and a specific layer of a layered repository facility.

Abstract: Disclosed herein are system, method, and computer program product embodiments for managing and accessing variants of applications. In an embodiment, a request for an application including one or more contextual parameters may be received. A base user interface configuration corresponding to the application may first be retrieved. One or more interface configuration files corresponding to the one or more contextual parameters may then be retrieved from a layered repository. The layered repository may be partitioned into organizational layers that store a plurality of interface configuration files associated with the application. The retrieved interface configuration files may be merged with the base user interface configuration to generate a composite interface configuration, and the composite interface configuration may be applied to the application at runtime.

Abstract: Disclosed herein are system, method, and computer program product embodiments for creating and utilizing configuration providers for layered repository facilities. An embodiment operates by creating or loading a custom data structure for a software application, retrieving configuration information from at least one configuration provider, storing the retrieved configuration information in the custom data structure, and associating the custom data structure with the application and a specific layer of a layered repository facility.

Abstract: Disclosed herein are system, method, and computer program product embodiments for managing and accessing variants of applications. In an embodiment, a request for an application including one or more contextual parameters may be received. A base user interface configuration corresponding to the application may first be retrieved. One or more interface configuration files corresponding to the one or more contextual parameters may then be retrieved from a layered repository. The layered repository may be partitioned into organizational layers that store a plurality of interface configuration files associated with the application. The retrieved interface configuration files may be merged with the base user interface configuration to generate a composite interface configuration, and the composite interface configuration may be applied to the application at runtime.

Abstract: A system facilitates modification or adaptation of a software object or platform, developed by a software developer, by a plurality of entities, each entity is assigned a hierarchical level, the lowest hierarchical level being assigned to a software developer and the highest hierarchical level being assigned to an end-user. At each level, when a modification or adaptation is implemented, a separate layer file or layer of a layer file is created and stored in a database. Subsequently, the changes of the respective layers are implemented in sequence according to the hierarchy, so that a higher hierarchical level's modifications that are in conflict with a setting of a lower hierarchical level replace the implementation of the lower hierarchical level's setting during runtime.

Abstract: A system includes execution of a software application based on metadata defining a first plurality of software components, reception of second metadata defining the first plurality of software components, determination, based on the second metadata, of a second plurality of the first plurality of software components for which the second metadata is different from the first metadata, and for which the second metadata is associated with elements of the software application, and generation of the elements of the software application based on the second metadata of the second plurality of software components.

Abstract: A plurality of registrations corresponding to a user interface component can be stored. Based on at least one of a layer of a software architecture to which a specific user of a user interface has authorized access, an assignment of a work center view to the user, and business data, it can be determined that the user interface presented to the user should include a navigation target to the user interface component. At run time, a navigation link to the user interface component can be dynamically generated according to a relevant registration selected from the plurality of registrations. The user interface incorporating the navigation link to the user interface component can be displayed. Related systems, articles of manufacture, and computer-implemented methods are described.

Abstract: A computer system includes a UI designer client that runs on a client device and is configured to enable creation of UI models. A client engine runs on a client device and is configured to initiate requests for the UI models, receive the UI models in response to the requests and interpret and render the UI models at runtime. A UI runtime server client is located on a server and is configured to interface with the client engine to receive and process the requests for the UI models from the client engine. A repository is located on the server and is configured to interface with the UI designer client and store the UI models as created using the UI designer client and interface with the UI runtime server client to deliver requested UI models to the UI runtime server client for interpretation and rendering by the client engine.

Abstract: All metadata relevant to user interface functionality needed to provide a specific unit of business functionality can be stored in one of a plurality of autonomous metadata containers retained on at least one data storage device. After a subset of available business functionality to be provided to a user is determined, a set of the plurality of autonomous metadata containers required to provide the subset of available business functions can be identified. A user interface view can be generated to present a view associated with each of the set of the plurality of autonomous metadata containers, and the generated user interface view can be provided for display to the user. Related systems, articles of manufacture, and computer-implemented methods are described.

Abstract: Upon receiving a request for a user interface view from a user interface, a user identity and a user authorization class for a user of the user interface can be checked against a user registry and an authorization class registry, respectively. A user interface view component can be retrieved according to the user identity and the user authorization class. The user interface view can be generated by aggregating the retrieved user interface view component with at least one other user interface view component consistent with the user identity and user authorization class, and the generated user interface view can be returned for display to the user via the user interface. Related systems, articles of manufacture, and computer-implemented methods are described.

Abstract: A system includes execution of a software application based on metadata defining a first plurality of software components, reception of second metadata defining the first plurality of software components, determination, based on the second metadata, of a second plurality of the first plurality of software components for which the second metadata is different from the first metadata, and for which the second metadata is associated with elements of the software application, and generation of the elements of the software application based on the second metadata of the second plurality of software components.

Abstract: Various embodiments of systems and methods for integrated metadata and nested authorizations in a user interface framework are described herein. User interface components metadata and authorization metadata are stored in one integrated entity. The primary user interface application components have authorization metadata and are checked at runtime for accessibility to the user interface application for a given user. The user interface framework ensures the security of the embedded user interface components via nested authorizations using metadata relations. The metadata relations are used for runtime authorization and policy generation. Generic user interface components are aggregated at runtime.

Abstract: All metadata relevant to user interface functionality needed to provide a specific unit of business functionality can be stored in one of a plurality of autonomous metadata containers retained on at least one data storage device. After a subset of available business functionality to be provided to a user is determined, a set of the plurality of autonomous metadata containers required to provide the subset of available business functions can be identified. A user interface view can be generated to present a view associated with each of the set of the plurality of autonomous metadata containers, and the generated user interface view can be provided for display to the user. Related systems, articles of manufacture, and computer-implemented methods are described.

Abstract: A plurality of registrations corresponding to a user interface component can be stored. Based on at least one of a layer of a software architecture to which a specific user of a user interface has authorized access, an assignment of a work center view to the user, and business data, it can be determined that the user interface presented to the user should include a navigation target to the user interface component. At run time, a navigation link to the user interface component can be dynamically generated according to a relevant registration selected from the plurality of registrations. The user interface incorporating the navigation link to the user interface component can be displayed. Related systems, articles of manufacture, and computer-implemented methods are described.

Abstract: Upon receiving a request for a user interface view from a user interface, a user identity and a user authorization class for a user of the user interface can be checked against a user registry and an authorization class registry, respectively. A user interface view component can be retrieved according to the user identity and the user authorization class. The user interface view can be generated by aggregating the retrieved user interface view component with at least one other user interface view component consistent with the user identity and user authorization class, and the generated user interface view can be returned for display to the user via the user interface. Related systems, articles of manufacture, and computer-implemented methods are described.

Abstract: A computer system includes a UI designer client that runs on a client device and is configured to enable creation of UI models. A client engine runs on a client device and is configured to initiate requests for the UI models, receive the UI models in response to the requests and interpret and render the UI models at runtime. A UI runtime server client is located on a server and is configured to interface with the client engine to receive and process the requests for the UI models from the client engine. A repository is located on the server and is configured to interface with the UI designer client and store the UI models as created using the UI designer client and interface with the UI runtime server client to deliver requested UI models to the UI runtime server client for interpretation and rendering by the client engine.

Abstract: A system and method for message lifetime management. According to an embodiment of the invention, a front-end application process identifies during a user interface interaction cycle of the front-end application process at least one stateful message reported to the front-end application process by a back-end service process during a prior user interface interaction cycle of the front-end application process, the at least one stateful message having been stored in a message buffer by the front-end application process, queries the back-end service process to determine whether the at least one stateful message is currently valid, and removes the at least one stateful message from the message buffer if it is determined not to be currently valid.

Abstract: Generally, systems and methods permit customized delivery of messages to a user depending on the specific requirements of a user interface. A processing layer between a business object and a user interface may determine, for a received message, an appropriate rule for the target user interface. The message rule may be applied, and depending on the rule, the message may be delivered to the user.

Abstract: A system and method are provided for handling a notification message in an enterprise services framework, including in response to the saving of a transaction, sending a notification message to the enterprise system framework, the notification message containing an associated message class including information of message severity and message symptom. The framework includes a controller layer situated between a service management layer and a business object layer, the controller layer maintaining a message registry database which collects and stores the notification message and the information of message severity, message symptom, and message identification. A system and method is provided for the hierarchical handling of software objects, including providing software objects, each associated with a user interface message, hierarchically associating the user interface messages, and displaying those messages in a tree structure in association with each of the software objects.

Abstract: A method and system are provided for providing a user-interface. The method may include receiving a request to render a business portal at a browser. The method may further include responsive to the request, determining a set of work lists to be rendered on the business portal. The method may further include retrieving a set of quick links corresponding to the set of work lists, wherein each quick link is associated with a work list; transmitting the set of quick links to the browser. The method may further include rendering the set of quick links at the browser to the user on a first screen.