Microsoft Technology Licensing, LLC

Stuart Glasson

Mehmet Kerem Kiziltunc

Thomas Hejlsberg

Christian Olaf Abeln

Dean Charles McCrae

Jacob Winther Jespersen

Uffe Kjall

Gert Willem Robyns

Mostafa Balat

Marc Hansen

Cristian-Alexandru Chereches

Thomas Sondergaard Jensen

Chethan Thopaiah

Bogdan Sturzoiu

Esben Nyhuus Kristoffersen

Tsvi M Reiter

Uno Junghans

Palle D Larsen

Jesper Boelsmand

Workflow definitions are broken into a set of components. Each workflow component has an instance-specific workflow definition that it operates from. Different steps can be injected into different workflow instance-specific definitions, based upon a given state of each individual workflow instance.

Workflow generation and editing

A system for extending an enterprise resource planning application is provided. The system employs 'Add-ins' that each have a functional behavior that is independent of the client on which it executes and a user interface behavior that is dependent on the characteristics of the display, and other characteristics, of the client (i.e., a display target). When a user attempts to invoke an Add-in via the client runtime, the client runtime determines whether the Add-in is available at the user's computer. If not, the client runtime downloads the appropriate artifact for execution at the user's computer. In this environment, neither the client runtime nor the server-side business logic contains the logic used to implement a particular Add-in behavior on the supported display targets. Instead, this logic is contained within separate artifacts associated with a single Add-in having a particular behavior, each artifact implementing the behavior for a specific display target.

Add-ins dynamically extending display targets and business-logic programming model

A system to enables Rapid Application Development ('RAD') is provided. The system provides an object model of an ERP application, which enables software developers to customize the ERP applications. The object model provides a base class that is inherited by each object class. The base class provides an invoke function that is implemented by each object class. During compilation, the RAD system compiles each invocation of a function of an object into a call to a dynamic component passing an identifier of the object, an identifier of the function to be invoked, and the parameters to be passed to the function. The RAD system dynamically compiles, assembles, and instantiates object classes as needed. Because objects are bound at runtime, rather than at compile time, when the source code of an object is modified, the entire ERP application does not need to be recompiled into monolithic IL code and the compilation of object classes is deferred until an object of that class is needed during runtime. The object model thus significantly decreases the time required to customize and extend an ERP application according to the needs of an individual customer.

Rapid application development

A system and method of enforcing Enterprise Resource Planning ('ERP') software object permissions in a three-tiered architecture is provided. A user connects to the three-tiered architecture via an enhanced client, which connects to a database server via a middle-tier server. The database server stores code and permission information for each database object. When a user connects to the system, the user's permissions are retrieved and stored at the middle-tier server. The user may then access data by instantiating objects at the middle-tier server by compiling and executing code retrieved from the database server. The middle-tier server performs permission checking for accessing database objects and provides environments for executing both managed and unmanaged code. The middle-tier server can perform permission checking for users and objects without accessing the database server.

Enforcement of object permissions in enterprise resource planning software

Growing community of inventors

Copenhagen, Denmark

Stuart Glasson