Abstract: A testing framework extension may be provided. An application comprising a form may be created within a modeling framework. A variable associated with the form may be defined and an application programming interface (API) may be created according to the form. A test case may be efficiently executed without rendering a physical UI using the variable by making at least one call to the API thus exercising (at least one part of) the form logic and a result of executing the test case may be reported to a user.

Abstract: A data access request for data that is provided from a data provider corresponding to an external data source. The data access request is transformed into a call supported by the external computing system. Data that is responsive to the call is received in a form provided by the external computing system, and the data is transformed into a form expected by the native system. The transformed data is returned to the requestor through the API.

Abstract: A cache manager application provides a data caching policy in a multiple tenant enterprise resource planning (ERP) system. The cache manager application manages multiple tenant caches in a single process. The application applies the caching policy. The caching policy optimizes system performance compared to local cache optimization. As a result, tenants with high cache consumption receive a larger portion of caching resources.

Abstract: A computer-implemented method of modifying execution behavior of a programmatic unit of source code is provided. The method includes loading the programmatic unit of source code and determining whether at least one customization is defined for the programmatic unit. The at least one customization is selectively executed based on whether a prerequisite of the customization is satisfied.

Abstract: An enterprise resource planning (ERP) system provides efficient maintenance and upgrade of tenant databases utilizing shared schema. A schema change is propagated from a master to tenants. Support is provided for tenants to be offline. The schema changes are applied at a mount time. Server load associated with the ERP database is distributed when tenant databases are updated with new schema changes. Changes to the application metadata (table schemas) is detected and applied to multiple tenants at a runtime.

Abstract: A cache manager application provides a data caching policy in a multiple tenant enterprise resource planning (ERP) system. The cache manager application manages multiple tenant caches in a single process. The application applies the caching policy. The caching policy optimizes system performance compared to local cache optimization. As a result, tenants with high cache consumption receive a larger portion of caching resources.

Abstract: Modeled Types allow a developer to define attributes and/or code when defining a new type. When the Modeled Type is used, specific values may be assigned to the attributes. The consumer of the values of the attributes can be the type itself by executing the logic during application execution, or the consumer may be the runtime framework or the application using the values by querying the meta-data of the Modeled Type. Modeled Type Aliasing defines a Modeled Type based on another Modeled Type allowing both a new unique name but at the same time optionally supplying specific values to one or more of the attributes of the base Modeled Type. Context-aware Modeled Types provide a description of how to determine the value for the attribute.

Abstract: A reusable ERP data retrieval object, in particular, a wide application query object provides a systematic and standardized approach to data retrieval. In one embodiment, the wide application query object is an encapsulated query object in that multiple queries are aggregated into one master query object (i.e., the wide application query object) that can, but does not necessarily have to, span multiple disparate data sources. In another embodiment, data retrieved in accordance with the wide application query logic is manipulated by code in any of a variety of different ways using a trigger model and specialized constructs. In still another embodiment, public parameters are utilized to trigger functions that impact the substance and layout of the query output.

Abstract: A testing framework extension may be provided. An application comprising a form may be created within a modeling framework. A variable associated with the form may be defined and an application programming interface (API) may be created according to the form. A test case may be efficiently executed without rendering a physical UI using the variable by making at least one call to the API thus exercising (at least one part of) the form logic and a result of executing the test case may be reported to a user.

Abstract: A system and method directed to capturing the structure of data models using entity patterns is provided wherein an entity pattern is an abstraction, for example in the MICROSOFT BUSINESS FRAMEWORK® (MBF), that surfaces in the model editor of the framework at the root level and consists of one or more entity roles that together define a structural pattern of a model. The entity pattern may be considered as an über-model, or a model template for a model. Prescriptive rules are added to the design of entities, required properties and relations to other entities (entity roles). Applications of the entity patterns are validated at design time. The runtime framework supports any applied pattern and invokes the pattern specific code. It is a general advantage that the runtime operation is model driven and interprets the model data at runtime. The application and usage of a pattern is part of the model of the application/software program.

Abstract: A system and method directed to capturing the structure of data models using entity patterns is provided wherein an entity pattern is an abstraction, for example in the MICROSOFT BUSINESS FRAMEWORK®(MBF), that surfaces in the model editor of the framework at the root level and consists of one or more entity roles that together define a structural pattern of a model. The entity pattern may be considered as an über-model, or a model template for a model. Prescriptive rules are added to the design of entities, required properties and relations to other entities (entity roles). Applications of the entity patterns are validated at design time. The runtime framework supports any applied pattern and invokes the pattern specific code. It is a general advantage that the runtime operation is model driven and interprets the model data at runtime. The application and usage of a pattern is part of the model of the application/software program.

Abstract: Modeled Types allow a developer to define attributes and/or code when defining a new type. When the Modeled Type is used, specific values may be assigned to the attributes. The consumer of the values of the attributes can be the type itself by executing the logic during application execution, or the consumer may be the runtime framework or the application using the values by querying the meta-data of the Modeled Type. Modeled Type Aliasing defines a Modeled Type based on another Modeled Type allowing both a new unique name but at the same time optionally supplying specific values to one or more of the attributes of the base Modeled Type. Context-aware Modeled Types provide a description of how to determine the value for the attribute.