Microsoft Technology Licensing, LLC

Elliot Stephenson Lewis

Andriy Smertin

David Robert Shutt

Mahesh Hariharan

Noor Mohammed Merchant

Israel Hilerio

Michael James Ott

Prabhat Kumar Pandey

Jasjit Singh Grewal

Jigar Thakkar

Jeremy M Kolpak

Ajith Kumar Gande

Jagan Peri

Nick Thomson

Koushik Bhattacharjee

Maya Widyasari

Jay Grewal

Andrei Smertin

Oleksiy Vlasenko

Mahesh Vijayaraghavan

Xiaodond La

Sergey Sorokin

Karin Zimprich

Manisha Powar

Nick Patrick

Access to customer relationship management (CRM) secured field instances is enabled based on field settings. A requester's identity determines action paths to be executed in order to enable access to fields. A client application's user privileges are inherited to enable access to secured fields. Such access through a granted privilege is provided through an API intermediating inheritance of user's privileges from client application.

Programmatically enabling user access to CRM secured field instances based on secured field instance settings

A post is generated that identifies different types of activity in a computer system, such as changes to the data in the computer system. The post is generated in a language-neutral way. An activity feed generator generates a language-specific post and distributes it, in an activity feed, to a set of users, based on user preferences. The activity feed generator can also access a security model so that only users with sufficient privileges receive the post in their activity feed.

Automatic language sensitive, event based activity feeds

Techniques for an inherited entity storage model are described that can be employed to implement inherited entity management for a CRM system. In at least some embodiments, input can be obtained to create a custom entity that is based at least in part upon a parent entity. The custom entity is created to inherit the parent entity according to an inheritance relationship established between the entities. To do so, the custom entity is created from the parent entity in a common table with the parent entity using some common fields and defining custom fields as appropriate. Data for the entities is then stored via the common table. This approach can reduce storage requirements, enable unified searching, and speed up data operations. Further, back-end business logic associated with parent entity in the CRM system can be automatically applied to the custom entity based upon the inheritance relationship established between the entities.

Inherited entity storage model

Technologies are described herein for providing a hosted multi-tenant application that utilizes per-tenant unshared private databases. A shared middle-tier is utilized in conjunction with private, unshared databases for each of the tenants. The private, unshared databases are utilized to store application data for an associated tenant, along with any customizations to the application implemented by the tenant. A shared configuration database is also utilized that stores application data that is shared among the tenants. When a request is received from a tenant to access the hosted application, the shared configuration database is utilized to locate the private, unshared database associated with the tenant making the request. The contents of the private, unshared database associated with the tenant making the request are then utilized to response to the request.

Hosted multi-tenant application with per-tenant unshared private databases

In a multi-tenant data sharing environment with shared, customizable data attributes are assigned to requested data and stored in a cache store along with the requested data. For non-customized data designated as system data, one copy is stored in the cache store for use by multiple tenants allowing optimization of memory and performance for each data request/retrieval operation. A 'delete sentinel' attribute may be assigned to non-existing data in the cache store enabling notification of requesting tenant(s) without a need to access the tenant data store each time a request for the non-existing data is received.

In-memory caching of shared customizable multi-tenant data

A method for organizing task data used in customer relationship management systems in which task data is decomposed into a set of business activity classes including a set of business task classes, where the business task classes are combined through association or multiple inheritance to create the business activity class. Each task class can be further decomposed into a base task class and a set of task characteristic classes where task definitions may be modified by associating additional task characteristic classes to the base task class.

Decomposition of tasks into extensible and customizable business activities

Growing community of inventors

Seattle, WA, United States of America

Elliot Stephenson Lewis