Enterprise computing platform with support for editing documents via logical views

• US 9,513,874 B2
• Filed: 11/29/2011
• Issued: 12/06/2016
• Est. Priority Date: 08/18/2011
• Status: Active Grant

• Current Assignee: Infosys Limited
• Original Assignee: Infosys Limited
• Inventors: Joshi, Dinesh Govind, Shivaram, Mahesh Huyilalu, Kaushik, Ganesan, Baskaran, Subramanian, Aradhya, Vinoop
• Primary Examiner(s): Kang, Insun
• Application Number:
  US13/306,903
• Publication Number:
  US 20130047135A1
• Time in Patent Office: 1,834 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 8/30 Creation or generation of source code

Abstract

Various technologies related to an enterprise computing platform are presented. Documents in a framework can be edited via logical views as described. An enterprise computing platform having a variety of frameworks can be configured to operate in a variety of business domains. Features such as parallel computing, distributed computing, logical documents, document transformation, space visualization, data security, and others can be accomplished via configuration rather than coding.

Claims

1. One or more non-transitory computer-readable devices comprising computer-executable instructions for performing a method comprising:

in an extensible view architecture framework providing a document-centric platform, receiving a request to interact with a logical document, wherein the request to interact comprises a request to perform an edit operation on the logical document;

responsive to receiving the request, processing the request according to configuration information associated with the logical document and stored for the extensible view architecture framework, wherein the processing comprises directing method calls to a programming object of a domain-specific object class derived from a domain-independent base object class specified in the configuration information;

collecting content of one or more logical document elements from one or more locations within a data source, wherein the content is collected from an original source document in the data source, content of the original source document is filtered, and the content of the one or more logical document elements does not have all the content of the original source document;

constructing a logical view of the logical document based on the one or more logical document elements, wherein the one or more logical document elements are arranged hierarchically in a spatial context; and

providing access to the logical view for consumption by a view provider;

wherein the logical view is of a format for consumption by a plurality of different view provider types, wherein the method further comprises;

receiving a request to display the logical document according to the logical view;

displaying the logical document according to the logical view, wherein the displaying comprises depicting the one or more logical document elements as spatially within the logical document;

receiving edits to the logical view of the logical document; and

saving the logical view, wherein saving the logical view comprises leaving the content of the original source document in the data source as unchanged, and saving changes from the edits as a separate list of changes to a base document;

wherein at least one logical document element of the one or more logical document elements itself contains further sub-elements that are depicted as spatially within the at least one logical document element.

2. The one or more non-transitory computer-readable devices of claim 1 wherein:

the logical view is encapsulated in the programming object of the domain-specific object class.

3. The one or more non-transitory computer-readable devices of claim 1 wherein:

the class derived from the domain-independent base object class contains domain-specific callable methods for processing domain-specific aspects of the logical document.

4. The one or more non-transitory computer-readable devices of claim 1 wherein:

the extensible view architecture framework supports location independence.

5. The one or more non-transitory computer-readable devices of claim 1 further comprising:

representing the logical document internally as a logical document comprising one or more logical document elements, wherein the content of the one or more logical document elements are stored as source documents in one or more locations within a data source.

6. The one or more non-transitory computer-readable devices of claim 5 further comprising:

storing hierarchical relationships within the logical document; and

outputting the hierarchical relationships to a view provider for presentation by the view provider.

7. The one or more non-transitory computer-readable devices of claim 1 further comprising:

instantiating a view manager as a view manager programming object; and

managing the logical view with the view manager.

8. The one or more non-transitory computer-readable devices of claim 7 wherein:

the view manager programming object is of an object class derived from the domain-independent base object class.

9. The one or more non-transitory computer-readable devices of claim 1 further comprising:

instantiating the logical view as a logical view programming object;

wherein the logical view programming object is of an object class derived from the domain-independent base object class.

10. The one or more non-transitory computer-readable devices of claim 9 wherein:

the domain-independent object class comprises;

a callable method drawing the logical view; and

a callable method capturing the logical view.

11. The one or more non-transitory computer-readable devices of claim 1 wherein:

the logical view is of a view-provider-independent form.

12. The one or more non-transitory computer-readable devices of claim 11 wherein providing access comprises:

providing a reference to the logical view to a view provider for translation from the logical view to a rendered view.

13. The one or more non-transitory computer-readable devices of claim 12 further comprising:

presenting the rendered view, wherein the presenting visually presents a presentation of the logical document.

14. The one or more non-transitory computer-readable devices of claim 1 wherein:

collecting the content comprises accessing a serialized version of content of the logical document in a database;

drawing content of one or more logical view elements from the serialized version of the content of the logical document; and

constructing the logical view comprises representing the content of the one or more logical view elements in memory as the logical view.

15. The one or more non-transitory computer-readable devices of claim 1 further comprising:

storing rules for document transformation for a plurality of entities; and

in an enterprise automation framework, applying the rules for respective of the entities, the applying generating a plurality of transformed documents comprising the logical document;

wherein the original source document comprises an optimized source document; and

transforming a given document comprises repeatedly transforming the optimized source document.

16. The one or more non-transitory computer-readable devices of claim 15 further comprising:

storing availability and capacity information for a plurality of servers; and

based on the availability and capacity information for the plurality of servers, in an enterprise computing framework, sending a job to a server;

wherein the job performs the generating of the logical document;

based on the availability and capacity information for the plurality of servers, in an enterprise computing framework, sending a different job to a different server; and

wherein the different job performs generating of a different document.

17. The one or more non-transitory computer-readable devices of claim 16 further comprising:

in an enterprise resource and services management framework, storing configuration information for a plurality of other frameworks.

18. The one or more non-transitory computer-readable devices of claim 1 wherein the method further comprises:

receiving an attempted edit to the logical view of the logical document via a user drag operation;

detecting that the user drag operation drags an item to an impermissible location or attempts to delete an essential item; and

responsive to detecting that the user drag operation drags an item to an impermissible location or attempts to delete an essential item, obtaining approval of another party before implementing the user drag operation.

19. The one or more non-transitory computer-readable devices of claim 1 wherein the original source document comprises an optimized source document and the method further comprises:

transforming the optimized source document repeatedly, wherein the transforming generates a plurality of transformed documents.

20. A method implemented at least in part by one or more computing devices, the method comprising:

in an extensible view architecture framework providing a document-centric platform, receiving a request for a view of a logical document comprising one or more logical document elements of the logical document;

responsive to the request, accessing the logical document according to configuration information stored for the extensible view architecture framework, wherein accessing the logical document comprises calling at least one method on at least one programming object of a domain-specific object class derived from a domain-independent base class specified in the configuration information, the programming object representing the logical document, wherein the at least one programming object is configured to provide content of the logical document, and is based on a plurality of original source documents in a data source, wherein the plurality of original source documents for the logical document are scattered among different sources at scattered locations in the data source, wherein the original source documents comprise different source types, wherein content of the original source documents is filtered, and content of the one or more logical document elements does not have all the content of the original source documents, wherein the one or more logical document elements are arranged hierarchically in a spatial context;

further responsive to the request, providing the content of the one or more logical document elements as represented by the at least one programming object representing the logical document;

representing one logical view of the logical document out of a plurality of logical views with a programming object representing the logical view;

providing access to the programming object representing the logical view;

receiving a method call on the programming object representing the logical view to provide the logical view for display as a rendered view;

responsive to the method call, providing content in a view-provider-independent format for display as the rendered view;

displaying the logical document according to the logical view, wherein the logical view incorporates the filtered content of the original source documents that are scattered among different sources at scattered locations in the data source, wherein the original source documents comprise different source types, wherein displaying the logical document comprises depicting the one or more logical document elements as spatially within the logical document;

receiving a request to perform an edit operation on the logical document;

receiving edits to the logical view of the logical document; and

saving the logical view, wherein saving the logical view comprises leaving the content of the original source documents in the data source as unchanged, and saving changes from the edits as a separate list of changes to one or more base documents;

wherein at least one logical document element of the one or more logical document elements itself contains further sub-elements that are depicted as spatially within the at least one logical document element.

21. The method of claim 20 wherein:

the logical document is represented by a domain-independent entity object class representing an entity.

22. The method of claim 21 wherein:

the domain-independent entity object class comprises the following attributes;

identifier;

meta type;

one or more serialization attributes; and

one or more security attributes.

23. The method of claim 22 wherein:

the meta type specifies whether that the entity is a document.

24. The method of claim 22 wherein:

the meta type supports specifying that the entity is a document, a view, a business object, and a use case.

25. The method of claim 20 wherein:

the logical document is represented by an object class having domain-specific features; and

the object class having domain-specific features is derived from a domain-independent entity object class.

26. The method of claim 20 wherein:

the logical document is represented by a more domain-specific object class having more domain-specific features, and the more domain-specific object class is derived from a lesser domain-specific object class having lesser domain-specific features; and

the lesser domain-specific object class is derived from a domain-independent entity object class.

27. The method of claim 20 wherein:

the logical document is a document type out of a plurality of document types; and

features are provided for the logical document by a configurable framework according to configuration information stored as associated with the document type.

28. The method of claim 27 wherein the features are specified to indicate:

whether the logical document is a compound document.

29. The method of claim 27 wherein the features comprise:

encryption.

30. A computer-implemented method of processing a plurality of documents of a plurality of different source document types, the method comprising:

in a computer system comprising a processor, representing a logical view of the documents for consumption by a view provider out of a plurality of view providers, wherein the logical view of the documents is represented via an entity object or a class derived from the entity object;

representing a logical document, wherein the logical document comprises one or more logical document elements drawing filtered content from the plurality of documents of the plurality of different source document types that are at scattered locations in a data source, and the logical document filters data from the plurality of documents of the plurality of different source document types that are at the scattered locations in the data source so that the logical document does not have all content of the documents of the plurality of different source document types, wherein the logical document is represented via the entity object or the class derived from the entity object, and the source document types comprise a spreadsheet and a database table;

storing configuration information for the different source document types, wherein the configuration information comprises a meta type indicating that the documents are documents, and the documents are original source documents in the data source;

receiving a request to view the documents;

responsive to the request, calling a method on an object class for providing content of the logical document, wherein the object class is derived from a domain-independent object class for providing content of an entity and the content is collected from the original source documents in the data source;

sending the content to the view provider for rendering as a physical view of the logical document;

representing one logical view of the logical document out of a plurality of logical views with a programming object representing the logical view, wherein the logical view incorporates the original source documents that are at the scattered locations in the data source and the one or more logical document elements are arranged hierarchically in a spatial context;

providing access to the programming object representing the logical view;

receiving a method call on the programming object representing the logical view to provide the logical view for display as a rendered view;

responsive to the method call, providing content in a view-provider-independent format for display as the rendered view, wherein the view-provider-independent format designates the one or more logical document elements as spatially within the logical document;

receiving a request to perform an edit operation on the logical document;

receiving edits to the logical view of the logical document; and

saving the logical view, wherein saving the logical view comprises leaving the content of the original source documents in the data source as unchanged, and saving changes from the edits as a separate list of changes to one or more base documents;

wherein at least one given logical document element itself contains further sub-elements that are designated as spatially within the given logical document element of the one or more logical document elements; and

wherein the documents provide a visual view of hierarchical spatial data representing store fixtures, and the one or more logical document elements comprise planograms representing a plurality of shelves onto which products are designated as placed.