Patent application number | Description | Published |
20090165001 | Timer Patterns For Process Models - The subject matter disclosed herein provides methods and apparatus, including computer program products, for providing timers for tasks of process models. In one aspect, an input representative of a temporal constraint for a task of a graph-process model may be received. The temporal constraint defines at least one of a delay or a deadline. The task may be associated with the temporal constraint created based on the received input. The temporal constraint defined to have a placement at the graph-process model based on the type of temporal constraint. The task and the temporal constraint may be provided to configure the process model. Related systems, apparatus, methods, and/or articles are described. | 06-25-2009 |
20100023339 | BUSINESS EVENT AGENTS - A system may include reception of a core event associated with a business object, evaluation of one or more rules based on the core event to identify a business event, construction of a message based on a mapping between the business object and an event interface, the mapping and the event interface associated with the business event and the business object; and publication of the message. | 01-28-2010 |
20100057771 | DYNAMIC NODE EXTENSIONS AND EXTENSION FIELDS FOR BUSINESS OBJECTS - A system may include generation of extension metadata defining an extension node associated with a core node of a business object and extension fields associated with the extension node, and generation of a runtime metadata buffer comprising enhanced metadata, the enhanced metadata based on core metadata of the business object and the extension metadata. In some aspects, a service request associated with the business object is received, it is determined whether the service request is associated with the extension node, an extension service associated with the extension node is provided if it is determined that the service request is associated with the extension node, and a core service associated with core data of the business object is provided if it is determined that the service request is not associated with the extension node. | 03-04-2010 |
20100057776 | DYNAMIC EXTENSION FIELDS FOR BUSINESS OBJECTS - A system may include generation of extension metadata defining an extension field of a core node of a business object, and generation of a runtime metadata buffer comprising enhanced metadata, the enhanced metadata based on core metadata of the business object and the extension metadata. In some aspects, a service request associated with the business object is received, it is determined whether the service request is associated with the extension field, an extension service associated with a dynamic data type is provided if it is determined that the service request is associated with the extension field, wherein the dynamic data type is associated with extension data of the extension field and core data of the business object, and a core service associated with an original data type is provided if it is determined that the service request is not associated with the extension field, wherein the original data type associated with the core data of the business object. | 03-04-2010 |
20100161648 | FLEXIBLE MULTI-TENANT SUPPORT OF METADATA EXTENSION - A system may include reception, from a client, of a request for access to an instance of an object model, identification of extension metadata associated with the object model and associated with the client in a metadata repository, identification of client-independent metadata of the object model in the metadata repository, merging of the client-independent metadata and the extension metadata associated with the client to create a merged object model, and access of the instance based on the merged object model. | 06-24-2010 |
20100161675 | PUBLIC SOLUTION MODEL IN AN ENTERPRISE SERVICE ARCHITECTURE - A computer-implemented system may include an application platform comprising a platform model of a plurality of business objects, each of the business objects comprising a model of data and associated logic, and a public solution model comprising a subset of the platform model. The system may also include a business application, wherein a data model and access logic of the business application are defined based on the public solution model, and wherein the application platform is to provide services to the business application based on the data model, the access logic and the platform model. | 06-24-2010 |
20100162147 | UI-DRIVEN BINDING OF EXTENSION FIELDS TO BUSINESS OBJECTS - A system may include presentation of a user interface including fields associated with a business object, reception, via the user interface, of an instruction to add an extension field to the business object, reception, via the user interface, of an indication of a reference field of the business object, determination of a binding of the reference field to the business object, and binding of the extension field to the business object based on the determined binding of the reference field to the business object. | 06-24-2010 |
20120005179 | EXTENSIBILITY OF METAOBJECTS - A system may include acquisition of metadata defining a first object model including extensible entities, the first object model comprising an instance of a metaobject, acquisition of metadata defining an extension object model, the extension object model to extend at least one of the extensible entities of the first object model, and merging of the object model and the extension object to create metadata defining an extended object model, the extended object model comprising an instance of the metaobject. | 01-05-2012 |
20120016910 | FIELD EXTENSIBILITY USING GENERIC BOXED COMPONENTS - A system may include reception of a definition of an extension field to be added to a business object node, generation of metadata for a data type enhancement object associated with the extension field, and generation of an ABAP dictionary proxy object based on the data type enhancement object, wherein the ABAP dictionary proxy object describes the extension field in a sub-structure of a first field of the ABAP dictionary proxy object. | 01-19-2012 |
20120023445 | MANAGING EXTENSION PROJECTS WITH REPOSITORY BASED TAGGING - According to some embodiments, information about a delta change package may be received. The delta change package may be, for example, associated with a customer extension project to be applied to content from a business service provider. A description tag for the delta change package may be received from a user, and the delta change package may be associated with the description tag in a repository of the business service provider. | 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 |
20120030581 | Mashup Component Framework for Business Enterprise User Interfaces - According to some embodiments, a business user interface page associated with a business service provider may be established. The user interface page may have, for example, at least one in-port to receive data from components and at least one out-port to provide data to components. A mashup component may be embedded within the business user interface page, and may also have at least one out-port to provide data to components. A display of the user interface page to a client may then be facilitated, including the embedded mashup component, wherein the mashup component combines and displays data received from a plurality of external data sources. | 02-02-2012 |
20140164411 | EXTENSIBILITY OF METAOBJECTS - A system may include acquisition of metadata defining a first object model including extensible entities, the first object model comprising an instance of a metaobject, acquisition of metadata defining an extension object model, the extension object model to extend at least one of the extensible entities of the first object model, and merging of the object model and the extension object to create metadata defining an extended object model, the extended object model comprising an instance of the metaobject. | 06-12-2014 |