Recursive navigation in mobile CRM

• US 9,741,060 B2
• Filed: 09/19/2011
• Issued: 08/22/2017
• Est. Priority Date: 09/17/2010
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Carter, Wayne, Tadepalli, Sridhar, Yaseen, Rahim
• Primary Examiner(s): Survillo, Oleg
• Application Number:
  US13/236,476
• Publication Number:
  US 20120124163A1
• Time in Patent Office: 2,164 Days
• Field of Search: 709217
• CPC Class Codes: G06F 16/245 Query processing
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

A method and apparatus for recursive navigation. In one embodiment of the method, a first reply is generated in response to receiving a first request from a mobile device. The first reply is generated as a function of a page definition, and the first reply comprises data selected from a first object of a logical data model, but not a second object of the logical data model. The first and second objects are distinct from each other. A second reply is generated in response to receiving a second request from the mobile device. The second reply is generated as a function of the page definition, and the second reply comprises data selected from the second object but not the first object.

Claims

1. A method comprising:

receiving a first request for a first page associated with a customer relationship management (CRM) system from a mobile device;

reading a first item from a CRM page navigation stack in response to receiving the first request;

determining whether the first request is for forward page navigation or backward page navigation;

in response to determining that the first request is for forward page navigation, generating a first reply by merging a page definition for the first page with data selected from one or more of;

a first object of a logical data model or a root object of the logical data model, wherein the page definition for the first page is selected from a memory of the CRM system, and wherein the first object of the logical data model is identified in the first item;

receiving a second request for a second page associated with the CRM system from the mobile device;

reading a second item from the CRM page navigation stack in response to receiving the second request;

determining whether the second request is for forward page navigation or backward page navigation; and

in response to determining that the second request is for backward page navigation;

removing the second item from the CRM page navigation stack; and

generating a second reply by merging a page definition for the second page with data selected from the second object but not the first object, wherein the page definition for the second page and the second object are identified in the second item.

2. The method of claim 1, wherein the selection of the data from the first object is based on metadata of the page definition for the first page, and wherein the selection of the data from the second object is based on the metadata of the page definition for the second page.

3. The method of claim 1, further comprising:

reading another item from the CRM page navigation stack in response to receiving another request from the mobile device;

generating another reply in response to reading the other item from the CRM page navigation stack, wherein the other reply comprises data from another object of the logical data model, wherein the other reply is generated as a function of another page definition, wherein the page definition for the first page and the other page definition are distinct from each other; and

pushing a third item onto the CRM page navigation stack, wherein the third item comprises an identity of the other object and an identity of the other page definition or a copy thereof.

4. The method of claim 3, further comprising:

generating an identity of the second object using information of the second item read from the CRM page navigation stack and information in the page definition; and

retrieving data from the second object in response to the generation of the identity of the second object;

wherein the second reply is generated using the data retrieved from the second object.

5. The method of claim 1, further comprising serializing the first reply for subsequent transmission to the mobile device.

6. A method comprising:

transmitting instructions to a computer system for storage in memory thereof;

wherein the instructions when executed implement a process, the process comprising;

receiving a first request for a first page associated with a customer relationship management (CRM) system from a mobile device;

reading a first item from a CRM page navigation stack in response to receiving the first request;

determining whether the first request is for forward page navigation or backward page navigation;

in response to determining that the first request is for forward page navigation, generating a first reply by merging a page definition for the first page with data selected from one or more of;

a first object of a logical data model or a root object of the logical data model, wherein the page definition is selected from a memory of the CRM system, wherein the page definition for the first page is selected from a memory of the CRM system, and wherein the first object of the logical data model is identified in the first item;

receiving a second request for a second page associated with the CRM system from the mobile device;

reading a second item from the CRM page navigation stack in response to receiving the second request;

determining whether the second request is for forward page navigation or backward page navigation; and

in response to determining that the second request is for backward page navigation;

removing the second item from the CRM page navigation stack; and

generating a second reply by merging a page definition for the second page with data selected from the second object but not the first object, wherein the page definition for the second page and the second object are identified in the second item.

7. The method of claim 6, wherein the selection of the data from the first object is based on metadata of the page definition for the first page, and wherein the selection of the data from the second object is based on the metadata of the page definition for the second page.

8. The method of claim 6, wherein the process further comprises:

reading another item from the CRM page navigation stack in response to receiving another request from the mobile device;

generating another reply in response to reading the other item from the CRM page navigation stack, wherein the other reply comprises data from another object of the logical data model, wherein the other reply is generated as a function of another page definition, wherein the page definition for the first page and the other page definition are distinct from each other; and

pushing a third item onto the CRM page navigation stack, wherein the third item comprises an identity of the other object and an identity of the other page definition or a copy thereof.

9. The method of claim 8, wherein the process further comprises:

generating an identity of the second object using information of the second item read from the CRM page navigation stack and information in the page definition; and

retrieving data from the second object in response to the generation of the identity of the second object;

wherein the second reply is generated using the data retrieved from the second object.

10. The method of claim 6, wherein the process further comprises serializing the first reply for subsequent transmission to the mobile device.

11. A non-transitory computer readable memory comprising instructions, wherein a method is implemented in response to executing the instructions, the method comprising:

receiving a first request for a first page associated with a customer relationship management (CRM) system from a mobile device;

reading a first item from a CRM page navigation stack in response to receiving the first request;

determining whether the first request is for forward page navigation or backward page navigation;

in response to determining that the first request is for forward page navigation, generating a first reply by merging a page definition for the first page with data selected from one or more of;

a first object of a logical data model or a root object of the logical data model, wherein the page definition for the first page is selected from a memory of the CRM system, and wherein the first object of the logical data model is identified in the first item;

receiving a second request for a second page associated with the CRM system from the mobile device;

reading a second item from the CRM page navigation stack in response to receiving the second request;

determining whether the second request is for forward page navigation or backward page navigation; and

in response to determining that the second request is for backward page navigation;

removing the second item from the CRM page navigation stack; and

generating a second reply by merging a page definition for the second page with data selected from the second object but not the first object, wherein the page definition for the second page and the second object are identified in the second item.

12. The non-transitory computer readable memory of claim 11, wherein the selection of the data from the first entry is based on metadata of the page definition for the first page, and wherein the selection of the data from the second entry is based on the metadata of the page definition for the second page.

13. The non-transitory computer readable memory of claim 11, wherein the method further comprises:

reading another item from the CRM page navigation stack in response to receiving another request from the mobile device;

generating another reply in response to reading the other item from the CRM page navigation stack, wherein the other reply comprises data from another object of the logical data model, wherein the other reply is generated as a function of another page definition, wherein the page definition and the other page definition are distinct from each other; and

pushing a third item onto the CRM page navigation stack, wherein the third item comprises an identity of the other object and an identity of the other page definition or a copy thereof.

14. The non-transitory computer readable memory of claim 13, wherein the method further comprises:

generating an identity of the second object using information of the second item read from the CRM page navigation stack and information in the page definition; and

retrieving data from the second object in response to the generation of the identity of the second object;

wherein the second reply is generated using the data retrieved from the second object.

15. The non-transitory computer readable medium of claim 11, wherein the method further comprises serializing the first reply for subsequent transmission to the mobile device.