Microsoft Technology Licensing, LLC

Mahesh Hariharan

Elliot Stephenson Lewis

Andriy Smertin

Noor Mohammed Merchant

Abhishek Agarwal

Nirav Yogesh Shah

Shashi Ranjan

Ashish Kothari

Prateek Rajvanshi

Sutirtha Saha

Adithya Nittor Vishwanath

Ashwinderjit Kaur

Rajarshi Ray

Anirban Saha

Shaleen Sharma

Eric Fernandes

Kritika Kishore Prasad

Gaurav Agrawal

Ramprasadh Kothandaraman

A qualifying system receives a channel activity record from one of a plurality of different external systems, over one of a plurality of different communication channels. It accesses qualification rules to determine whether the channel activity record is to be transformed into one or more target entities in a computing system. If so, a conversion engine accesses user-configurable mappings and conversion rules to identify conversion actions that are to be taken in order to transform the channel activity record into one or more target entities. The conversion engine performs a data transformation on the channel activity record to transform it into the identified one or more target entities.

Transforming data to share across applications

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 customer relationship management (CRM) eventing framework may be extended to a cloud computing environment. A listening channel may be opened between a service and a service bus in a cloud computing environment. The cloud computing environment may also include an authenticating service. Service information for the service may be registered with a CRM. The CRM may receive a request made by a requester. The request may trigger a request processing pipeline in an eventing framework. The CRM may post event data responsive to the request to the service bus. The service may receive the event data, process it and may send back a confirmation or response. The CRM may finally send a response to the requester.

Extending a customer relationship management eventing framework to a cloud computing environment in a secure manner

Growing community of inventors

Redmond, WA, United States of America

Mahesh Hariharan