Providing attachment-based data input and output
First Claim
1. An article comprising a non-transitory machine-readable storage medium storing instructions for interactive, attachment-based data management, the instructions operable to cause one or more computers to:
- receive a request from a logically remote client via a network interface, the request indicating a data file and a business object associated with a business application, the business object comprising at least one object attribute, the business object separate and distinct from the data file;
update the business object with a message in a format associated with the business application based on the data file, the message referencing a logical location of the data file;
map at least a portion of the data file to at least one keyword associated with the business object;
identify, based on the mapped portion of the data file, a handler object communicably coupled to an integration middleware logically situated between the business application and a remote repository;
store the data file in the remote repository; and
update a dependent object associated with the business object with a logical location of the data file in the remote repository.
2 Assignments
0 Petitions
Accused Products
Abstract
Various embodiments of systems, methods, and software provide attachment-based mass data input and output for a distributed application system. Software for interactive, attachment-based data management may comprise computer readable instructions operable when executed to receive a request from a logically remote client via a network interface, where the request indicates a data file and a business object associated with a business application. The business object is then updated with a message in a format associated with the business application based on the data file. The data file is then stored in a repository and a dependent object (included in, or referenced by, or otherwise associated with the business object) is then updated with a logical location of the data file in the repository.
67 Citations
23 Claims
-
1. An article comprising a non-transitory machine-readable storage medium storing instructions for interactive, attachment-based data management, the instructions operable to cause one or more computers to:
-
receive a request from a logically remote client via a network interface, the request indicating a data file and a business object associated with a business application, the business object comprising at least one object attribute, the business object separate and distinct from the data file; update the business object with a message in a format associated with the business application based on the data file, the message referencing a logical location of the data file; map at least a portion of the data file to at least one keyword associated with the business object; identify, based on the mapped portion of the data file, a handler object communicably coupled to an integration middleware logically situated between the business application and a remote repository; store the data file in the remote repository; and update a dependent object associated with the business object with a logical location of the data file in the remote repository. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. An article comprising a non-transitory machine-readable storage medium storing instructions for interactive, attachment-based data management, the instructions operable to cause one or more computers to:
-
automatically identify a business object in a business application based on a received request, the business object comprising at least one object attribute; instantiate a dependent object using the business object, the dependent object storing a logical location for a data file associated with the business object, the data file being separate and distinct from the business object and dependent object; map at least a portion of the identified business object; identify a handler object based on the mapped portion of the identified business object; convert, via the handler object, a business object message in a format associated with the business application to a second format, the business object message referencing the data file; and store the converted message at the logical location as the data file in the second format. - View Dependent Claims (13, 14)
-
-
15. A file server for interactive, attachment-based data management comprising:
-
memory storing a plurality of instantiated business objects according to a business application; and one or more processors; receiving a request from a logically remote client via a network interface, the request indicating a data file and one of the business objects associated with the business application, each business object comprising at least one object attribute, the business object separate and distinct from the data file; updating the business object with a message in a format associated with the business application based on the data file, the message referencing a logical location of the data file; mapping at least a portion of the data file to at least one keyword associated with the business object; identifying, based on the mapped portion of the data file, a handler object communicably coupled to an integration middleware logically situated between the business application and a remote repository; storing the data file in a logically remote repository from the business objects; and updating a dependent object associated with the business object with a logical location of the data file in the remote repository. - View Dependent Claims (16, 17, 18, 19, 20, 21, 22, 23)
-
Specification