Patent application number | Description | Published |
20100088391 | BACKEND SERVICE ADAPTATION - A request originating at a frontend server for data encapsulated in a plurality of business objects is received. The plurality of business objects are stored in a business object layer at the backend server remote from the frontend server. In addition, the request originates from a user interface layer is received at a controller layer. A controller object is instantiated in the controller layer at the backend server. Nodes of the controller object are mapped to nodes in the plurality of business objects so that the controller object encapsulates the request data. Thereafter, transmission of data response to the request encapsulated by the controller object to the frontend server is initiated. Related apparatus, systems, techniques and articles are also described. | 04-08-2010 |
20110161342 | BUSINESS OBJECT NODE ACCESS MANAGEMENT FOR SEARCH SERVICES IN A SERVICE-ORIENTED ARCHITECTURE - A system may include a database comprising stored data and a business process platform including business object metadata defining business objects representing the stored data. The business process platform may receive a query from a user to retrieve data from a first business object node of a business object, the business object representing stored data, determine whether the user is authorized to traverse all associations of a SELECT list of the query, determine whether the user is authorized to traverse all associations of a WHERE clause of the query, determine whether the user is authorized to retrieve any instances of each business object node of column specifications of the SELECT list of the query, and, if the determinations are affirmative, executing the query to retrieve a first result set. | 06-30-2011 |
20110161940 | MULTI-LANGUAGE SUPPORT FOR SERVICE ADAPTATION - A plurality of domain-specific service adaptation languages can be supported by a back-end service adaptation system to provide runtime access to a runtime instance of a data object comprising data stored in a repository. By defining a language-specific data access service and parser for each domain-specific service adaptation language, a single, service adaptation language-independent compiler and interpreter can prepare and execute a runtime load that includes an execution plan for retrieving and converting data from the repository for delivery in a data object according to a query request from a consumer runtime environment. A consumer using the consumer runtime environment can define the service adaptation language to be used and provide a parser and source code to enable access to business object data using the back-end service adaptation system. | 06-30-2011 |
20110161942 | SERVICE ADAPTATION DEFINITION LANGUAGE - A back-end service adaptation system provides access to normalized data in a data repository for a consumer runtime environment sending a query request for denormalized data. The back-end service adaptation system can include a data access service layer, a parser layer, and a back-end service adaptation runtime layer. The consumer runtime can use a service adaptation definition language (SADL), and the parser and data access service can be configured to convert and translate the SADL request for the back-end service adaptation runtime layer. | 06-30-2011 |
20120023154 | RAPID CLIENT-SIDE COMPONENT PROCESSING BASED ON COMPONENT RELATIONSHIPS - A client database manager can cause a memory of a client device on a client side of a network to store a first component, a second component, and a relationship value representing a dependent relationship between the first component and the second component. A client processing module can cause a processor to receive, after the storing, a request to process the first component at the client device. The client database manager can send to the server side of the network a request for an update of at least one of the first component or the second component. The client processing module can cause the processor to process at the client device, before receiving a response to the request for the update from the server side of the network, at least a portion of the first component and at least a portion of the second component based on the relationship value. | 01-26-2012 |
20120023421 | MODEL FOR EXTENSIONS TO SYSTEM PROVIDING USER INTERFACE APPLICATIONS - A customized application that is declared based on an abstract class definition derived from a declared host component model associated with a host software application implementing business processes and providing a graphical display associated with a user interface (UI) for a user in a client program executing on a client frontend device storing metadata associated with the UI for the client frontend device may be initiated, the metadata including a declaration of the declared host component model and a declaration of the abstract class definition. Access to data and functionality of the host software application may be obtained via the customized application. Customized output may be provided that is different from host output provided by the host software application, the customized output generated by accessing, via the abstract class definition, the declared host component model, for accessing the same data and functionality that is accessed by the host software application. | 01-26-2012 |
20120023484 | AUTOMATION OF TESTING FOR USER INTERFACE APPLICATIONS - A host software application implementing business processes and providing a graphical display associated with a user interface (UI) for a user in a client program executing on a client frontend device that is separate from a backend device storing metadata associated with the UI may be initiated. An automation graphical symbol may provide the user with an option to initiate a test on events of the host software application, during execution of the host software application. A request from the user may be received, to initiate a test on events of the host software application. Information may be received from the user indicating one or more selected specific events for performing the test. The test may be initiated on the selected specific events, based on a state of execution of the host software application at an initial time of the user indicating the selected specific events for performing the test. | 01-26-2012 |
20120030580 | Stable Anchors In User Interface to Support Life Cycle Extensions - According to some embodiments, a business service provider may define a stable user interface anchor entity associated with a business object data structure. A reference field may be associated with the stable user interface anchor, the reference field representing a path to a persistent node of the business object data structure. An end user adaptation to a user interface may then be applied in connection with the business object data structure, the adaptation referencing the stable user interface anchor entity. | 02-02-2012 |
20120030591 | LOGICAL DATA MODEL ABSTRACTION IN A PHYSICALLY DISTRIBUTED ENVIRONMENT - A component object binds business driven services to a graphical user interface (GUI). The object includes a data model, view model and controller. The view model graphically presents, and the controller manipulates data used by the object. The controller includes an event handler that respond to events generated within the GUI and binds data used by the object to a data source which can be another component object or a remotely located source. The event handler can call a local script to calculate the value of a data element within the object. The component object can be instantiated on a client, and can be configured to communicate with a corresponding component object on a server. The client and server component objects can exchange only that data that needs to be exchanged to maintain the current state of a user interface in the client computer. | 02-02-2012 |
20120030664 | PROCESSING OF SOFTWARE OBJECTS MOVED INTO A DROPZONE REGION OF AN APPLICATION - A non-transitory computer-readable storage medium storing code representing instructions that when executed are configured to cause a processor to perform a process. The code can comprise code to receive, on a client side of a network, an indicator that a first software object has been moved from a first application into a dropzone region of a second application. The code can include code to receive an indicator that a second software object has been moved into the dropzone region of the second application, and code to access a plurality of dropzone conditions. The code can include code to determine that a dropzone condition from the plurality of dropzone conditions has been satisfied based on the first software object and the second software object both being moved into the dropzone region, and code to send to a server side of a network an indicator that the dropzone condition has been satisfied. | 02-02-2012 |
20120102406 | COMPOSITION MODEL FOR COMPONENTS OF A USER INTERFACE FRAMEWORK FOR WEB APPLICATIONS - Various embodiments of systems and methods for a composition model for components of a user interface framework for Web applications are described. The methods include a loosely coupled method and a tightly coupled method for composing components in a UI framework. The loosely coupled method includes triggering a navigation pipe from an out-port of a first component to an in-port of a second component and defining a context mapping between a first set of parameters of the out-port of the first component and a second set of parameters of the in-port of the second component. The tightly coupled method includes exposing a binding reference from the first component to the second component and specifying a first data model entity from the first component to be bound to a second data model entity of the second component via a binding contract. | 04-26-2012 |
20120102414 | DISTRIBUTED CONTROLLER OF A USER INTERFACE FRAMEWORK FOR WEB APPLICATIONS - Various embodiments of systems and methods for improved user interface framework for Web applications are described herein. The UI framework is based on the MVC architectural pattern. An additional controller, a server controller, is included in the server part of the user interface framework runtime. A client controller is running at the client side of the user interface framework runtime. The client controller and the server controller form one logical synchronized controller. The server controller ensures that all needed controller calculations, which would lead to additional roundtrips between the client side and the server side, can be done on the server side. Thus, exact one roundtrip between client side and backend for every user interaction and transporting only the bare minimum of data needed to render the current UI state is achieved. | 04-26-2012 |
20120151439 | LIFECYCLE STABLE USER INTERFACE ADAPTATIONS - Various embodiments of systems and methods for lifecycle stable user interface adaptations are described herein. All adaptations done by partners/key users/end users to a user interface of a computer software application are preserved during the lifecycle of the application. In one aspect, the adaptations are persisted as additional metadata used for the generation of the user interface. In another aspect, the lifecycle stability is achieved by attaching the adaptations to semantically coherent set of fields placed in the UI that reappear in future releases of the computer software application. | 06-14-2012 |
20120166461 | LAYERING CONCEPT FOR A REPOSITORY OF A USER INTERFACE FRAMEWORK FOR WEB APPLICATIONS - Various embodiments of systems and methods for a layering concept for a repository of a user interface framework for Web applications are described herein. The content of a repository provided by different parties (e.g., vendor, partner, customer, user, etc.) is separated. The separation is achieved by assigning solutions to the parties that store content in the repository. Simplified access to the repository is achieved by layering the solutions in a stack and implementing a layer strategy for the layers and their order of access. | 06-28-2012 |
20120166977 | USER PROGRAMMING ACCESS TO DATA MODEL IN USER INTERFACE DESIGN - Various embodiments of systems and methods for user programming access to data model in user interface design are described herein. User interface modeling is merged with a scripting language for additional functionalities. In one aspect, scripting enhances the dynamic access to the whole user interface model. In another aspect, additional controller and navigation logic is exposed by means of script inputs. A user can model, bind and run advanced logic through runtime declaration. | 06-28-2012 |
20120166983 | INTEGRATED METADATA AND NESTED AUTHORIZATIONS IN A USER INTERFACE FRAMEWORK - 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. | 06-28-2012 |
20130159971 | PROCESSING CHANGED APPLICATION METADATA BASED ON RELEVANCE - 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. | 06-20-2013 |
20130167048 | CONTEXT DEPENDENT PERSONALIZATION OF REUSE COMPONENTS FOR A USER INTERFACE - According to some embodiments, a business service provider may associate a user interface floor plan with a plurality of reuse components, each reuse component being adapted to be used with multiple user interface floor plans. For example, a second reuse component may be embedded within a first reuse component. In this case, an end user adaptation to the second reuse component may be received and the system may automatically store, within the first reuse component, a context dependent reference to the second reuse component associated with the end user adaptation. | 06-27-2013 |