Patent application number | Description | Published |
20090150900 | WORKFLOW TASK RE-EVALUATION - An occurrence of a workflow re-evaluation event during execution of tasks in a workflow is identified. In response to the workflow re-evaluation event, it is determined for each task previously executed in the workflow whether such task needs to be executed again. Those tasks in the workflow for which it was determined that the corresponding task needs to be executed again are executed again, while the tasks in the workflow that were previously executed and for which it was not determined that the corresponding task needs to be executed again are skipped. Related apparatus, systems, techniques and articles are also described. | 06-11-2009 |
20090281777 | Workflow Modeling With Flexible Blocks - Disclosed is a method that includes providing tasks associated with a process, one or more of the tasks having a corresponding undetermined inter-dependency between the one or more of the tasks and other of the tasks, associating with the process one or more constraints specifying requirements regarding use of at least one of the tasks, the one or more constraints having corresponding graphical representations, and generating an instance of the process based on the one or more constraints to determine the corresponding undetermined inter-dependency between at least one of the one or more of the tasks and the other tasks. | 11-12-2009 |
20110029983 | SYSTEMS AND METHODS FOR DATA AWARE WORKFLOW CHANGE MANAGEMENT - A method includes providing a baseline workflow as an electronic representation of an actual workflow, the baseline workflow including baseline tasks, data items, and baseline data scopes, and providing a fragment workflow as an electronic representation of an actual fragment workflow, the fragment workflow including at least one fragment task, and at least one fragment data scope. A baseline data scope is identified as an affected data scope based on a structural change operation, the baseline workflow and the fragment workflow, and the affected data scope is compared to the at least one fragment data scope to identify at least one change operation. The fragment and baseline workflows are integrated based on the structural change operation to provide an integrated workflow, and the at least one data scope change operation is executed to provide at least one integrated data scope in the integrated workflow. | 02-03-2011 |
20110154253 | PROCESS FIELD EXTENSIBILITY FOR BUSINESS OBJECTS - A system and method for creating extension fields for business objects are described. In various embodiments, a system includes modules to display business processes and business objects thereof in graphical user interface screens. In various embodiments, the system propagates created extension fields to other business objects via metadata derived from selections in the graphical user interface. In various embodiments, a method for propagating extension fields from one business object to another business object via a data flow between the two business objects is presented. In various embodiments, the method receives instructions from a graphical user interface for the propagation of an extension field and sends instructions to a backend module to propagate the extension field from the source business object to the other business object. | 06-23-2011 |
20120030312 | TRANSPORT OF CUSTOMER FLEXIBILITY CHANGES IN A MULTI-TENANT ENVIRONMENT - Transporting of flexibility changes of customer content between tenants in a multi-tenant computing system can be performed by exporting customer content from a first tenant of the multi-tenant computing system, transporting the customer content exported from the first tenant to a second tenant of the multi-tenant computing system, importing the customer content into a staging area in the second tenant to enable a user associated with second tenant to access the customer content via the staging area based on a content extraction trigger, and activating selected customer content from the staging area in a productive component of the second tenant. The content extraction trigger can characterize an extraction of at least some of the customer content from the staging area. Related methods, systems, and articles of manufacture are also disclosed. | 02-02-2012 |
20120166928 | FIELD EXTENSIBILITY IN SERVICE INTERFACES AND FORMS MESSAGE TYPES - 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. | 06-28-2012 |
20130014080 | BULK ACCESS TO METADATA IN A SERVICE-ORIENTED BUSINESS FRAMEWORK - A bulk service interface can be instantiated for each of at least one service provider providing a plurality of business objects using a stored definition of a plurality of metadata properties relating to generation of a user interface that incorporates content of a plurality of business objects. The bulk service interface can query the stored definition and access, in a bulk metadata access process, dynamic metadata required for instantiation of the plurality of business objects. If the stored definition has not previously been received, a default bulk services access process that queries an existing dynamic metadata access interface of each of the plurality of business objects can be initiated to retrieve the dynamic metadata from each of the plurality of business objects. An instance of the user interface can be generated using dynamic metadata accessed by the bulk service interface and/or the retrieved by the default bulk services access process. | 01-10-2013 |
20130046894 | MODEL-DRIVEN REST CONSUMPTION FRAMEWORK - The present disclosure describes methods, systems, and computer program products for implementing web services. One method includes identifying a REST service for integration with a business application, identifying a set of metadata associated with the REST service, and generating a REST client proxy object associated with the REST service for use in consuming the REST service with the business application, where an instantiation of the REST client proxy object is consumable via the business application. In some instances, the method may include consuming the REST service using an instantiation of the generated REST client proxy object associated with the REST service. Further, the identified set of metadata associated with the REST service may include a service structure document and a metadata document. Generating the REST client proxy object may include generating at least one business configuration object and/or at least one authentication proxy artifact associated with the REST service. | 02-21-2013 |
20130086174 | SYSTEMS AND METHODS FOR SENDING AND RECEIVING COMMUNICATIONS - A computer system includes instructions recorded on a computer-readable storage medium and executable by at least one processor. The computer system includes a process component of a first deployment unit and a component module. The process component has a handling module and an object module. The handling module is operatively coupled to the object module. The handling module is operatively coupled to the component module. The handling module is configured to receive a message from a second deployment unit. | 04-04-2013 |
20140019934 | GENERATION FRAMEWORK FOR MAPPING OF OBJECT MODELS IN A DEVELOPMENT ENVIRONMENT - A delta handler can allow calculation of difference between an already generated set of backend entities and a set of new entities necessary to support a primary object affected by a change made in a development environment supporting extensions to a backend model of a software architecture. Improved stability and robustness can be provided via an approach in which a target list of activities relating to creating, changing, or deleting of entities in backend repositories necessary to support the affected primary object is created and a sequence for performance of the activities in the target list is determined in a manner that can allow handling of such activities in a unified manner rather than on a per object type basis. Related methods, systems, articles of manufacture, and the like are described. | 01-16-2014 |
20140026114 | LAYERING OF BUSINESS OBJECT MODELS VIA EXTENSION TECHNIQUES - An extension node can be defined in a second layer of a software architecture for a first business object existing in a first layer and originally having an association with a second business object that is also in the first layer. The extension node can be defined to have an association with the second business object existing in a second layer of the software architecture. The association of the second business object can be altered from the first business object to the extension node so that at run time, metadata defining one or more nodes of the first business object and the extension node can be read from a metadata repository and a run time version of the first business object can be constructed at run time in a run time business object load based on the metadata. | 01-23-2014 |
20140047412 | ADAPTABLE BUSINESS OBJECTS - An adaptable business object can include a generic, content-free, and meaning-free skeleton business object, which can be used to create a new business object without requiring that a user be proficient in a development environment such as a software development kit (SDK). Definitions of a first field to be added to a header of the adaptable business object and a second field to be added to an item node of the adaptable business object can be received via a field extensibility tool, and a terminology tool can adapt the adaptable business object by storing metadata relating to the terminology of the business object in a metadata repository such that screen and section titles for at least one user interface screen supported by the new business object can be presented at runtime using the stored metadata. | 02-13-2014 |
20140053133 | NAMING ALGORITHM FOR EXTENSION FIELDS IN DE-NORMALIZED VIEWS - An extension naming approach for avoiding naming collisions in de-normalized view on a business object can include accessing a reference field bundle, which includes reference field(s) corresponding to a core business object defined in a core software platform of a software architecture, from a metadata repository. A user can define an extension to the business object based on the core business object, for example via a development environment. The reference field(s) can include a defined path from a node in a peripheral object to a corresponding node in the core business object. A unique and reproducible name for the extension field can be generated based on the reference field, and the extension field with the unique and reproducible name can be added to the business object and to a data model of the peripheral object. | 02-20-2014 |
20140122411 | SINGLE PERSISTENCE IMPLEMENTATION OF BUSINESS OBJECTS - Business objects can be implemented in a single persistence scenario that supports both online transaction processing (OLTP) and online analytical processing (OLAP). A consumption-centric approach can use a same business object attribute data format model for consumption and persistence. Also, a singular model can be implemented in different layers of a system processing business objects. Extra software layers can be avoided. A business-objects-based system can take advantage of the technologies to provide greater flexibility, ease of extensibility, and performance improvements. | 05-01-2014 |