Legal claims defining the scope of protection, as filed with the USPTO.
1. A method of using messages to extend functionality of an application programming interface in a customer relationship management (“CRM”) system comprising: selecting an operation where the operation is a CRM operation; communicating to a CRM web service a request message based on the selected operation; if the request message has a business entity type name in the request message name, then the request message is only valid for the named entity: instantiating the request message; assigning the request message fields; and executing the request message; if the request message is a common request message without a business type name in the request message name, and the request message has a target property: instantiating the request message; selecting and instantiating one of the supported target classes; assigning the target class fields; assigning the request message fields; associating target class with the request message; and, executing the request message; if the request message name does not include a business entity name nor the message has a target property: instantiating the request message; assigning the request message fields; and executing the request message.
2. The method according to claim 1 , wherein all the new messages are derived from the base request and response classes.
3. The method according to claim 1 , wherein the method is executed by communicating a request message and returning a response message.
4. The method according to claim 1 , wherein the request messages are instantiated and built by a client of a CRM web service.
5. The method according to claim 1 , wherein the message is transmitted to the CRM web service via a transport protocol.
6. The method according to claim 1 , wherein business operations are assigned to business entities.
7. The method according to claim 1 , wherein target base classes are created by separating the business entities into categories based on the business operations supported by the category.
8. The method according to claim 1 , wherein the target class hierarchy is used to determine what business entities support which operations.
9. A computing apparatus, comprising: a display unit that is capable of generating video images; an input device; a processing apparatus operatively coupled to said display unit and said input device, said processing apparatus comprising a processor and a memory operatively coupled to said processor, a network interface connected to a network and to the processing apparatus; said processing apparatus being programmed for selecting an operation where the operation is a customer relationship management (“CRM”) operation; communicating to a CRM web service via a transport protocol a request message based on the selected operation; if the request message has a business entity type name in the request message name, then the request message is only valid for the named entity: instantiating the request message; assigning the request message fields; and executing the request message; if the request message is a common request message without a business type name in the request message name, and the request message has a target property: instantiating the request message; selecting and instantiating one of the supported target classes; assigning the target class fields; assigning the request message fields; associating target class with the request message; and, executing the request message; if the request message name does not include a business entity name nor the message has a target property: instantiating the request message; assigning the request message fields; and executing the request message.
10. The computing apparatus of claim 9 , wherein the request messages are instantiated and built by a client of a CRM web service.
11. The computing apparatus of claim 9 , wherein target base classes are created by separating the business entities into categories based on the business operations supported by the category and wherein the target class hierarchy can be reviewed to determine what business entities support which operations.
12. A computer readable storage medium adapted to store computer executable code to use messages to extend functionality of an application programming interface in a customer relationship management (“CRM”) system wherein the computer executable code comprises computer code for: selecting an operation where the operation is a CRM operation; communicating to a CRM web service a request message based on the selected operation wherein the request messages are instantiated and built by a client of a CRM web service; if the request message has a business entity type name in the request message name, then the request message is only valid for the named entity: instantiating the request message; assigning the request message fields; and executing the request message; if the request message is a common request message without a business type name in the request message name, and the request message has a target property: instantiating the request message; selecting and instantiating one of the supported target classes; assigning the target class fields; assigning the request message fields; associating target class with the request message; and, executing the request message; if the request message name does not include a business entity name nor the message has a target property: instantiating the request message; assigning the request message fields; and executing the request message.
13. The computer readable storage medium of claim 12 , wherein the request messages are instantiated and built by a client of a CRM web service.
14. The computer readable storage medium of claim 12 , wherein target base classes are created by separating the business entities into categories based on the business operations supported by the category and wherein the target class hierarchy can be reviewed to determine what business entities support which operations.
15. The computer readable storage medium of claim 12 , wherein all the new messages are derived from the base request and response classes.
Unknown
February 23, 2010
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.