Invented by Timothy J. Barker, Jonathan Levine, James Johnson, Salesforce Inc

The market for System and method for sharing documents among on-demand services is rapidly growing as businesses and individuals increasingly rely on cloud-based platforms and on-demand services for their document management needs. This innovative solution allows for seamless collaboration and sharing of documents across various on-demand services, providing a more efficient and streamlined workflow. The rise of on-demand services has transformed the way businesses operate, enabling them to access a wide range of services and resources without the need for extensive infrastructure or long-term commitments. However, one challenge that arises with the use of multiple on-demand services is the difficulty of sharing and collaborating on documents across these platforms. This is where the System and method for sharing documents among on-demand services comes into play. This system provides a unified platform that integrates with various on-demand services, allowing users to easily share, access, and collaborate on documents across these platforms. Whether it’s sharing a document from a cloud storage service to a project management tool or collaborating on a document within a customer relationship management (CRM) system, this solution ensures seamless document sharing and collaboration. One of the key advantages of this system is its ability to eliminate the need for manual document transfers and duplicate copies. With this solution, users can directly access and edit documents from within their preferred on-demand service, without the hassle of downloading, uploading, or transferring files. This not only saves time but also reduces the risk of version control issues and data loss. Furthermore, this system offers enhanced security features to protect sensitive documents. It allows users to set access permissions, ensuring that only authorized individuals can view or edit specific documents. Additionally, it provides audit trails and activity logs, enabling businesses to track document activities and ensure compliance with data protection regulations. The market for System and method for sharing documents among on-demand services is witnessing significant growth due to the increasing adoption of cloud-based platforms and on-demand services across various industries. Businesses of all sizes, from startups to large enterprises, are recognizing the value of this solution in streamlining their document management processes and improving collaboration among teams. Moreover, the COVID-19 pandemic has accelerated the demand for remote work solutions, making the need for efficient document sharing and collaboration even more crucial. With employees working from different locations and relying on various on-demand services, a unified system for sharing documents becomes essential for maintaining productivity and ensuring seamless collaboration. In conclusion, the market for System and method for sharing documents among on-demand services is experiencing rapid growth as businesses and individuals seek efficient and secure ways to collaborate on documents across multiple platforms. This innovative solution not only streamlines document management processes but also enhances productivity and data security. As the reliance on on-demand services continues to increase, the demand for this system is expected to grow, making it a promising market for businesses operating in the document management space.

The Salesforce Inc invention works as follows

A method of sharing documents between on demand services is described. In one embodiment, the user of a 1st on-demand services may be able view a list that includes both content from the 1st on-demand and content from a 2nd on-demand. Content from the second on demand service can be associated with content information, which allows the content to shared by multiple users of the 1st on-demand services. The user who wants to view the content selects or clicks on an indicator that identifies the content. A connection is made to the second service and images are sent to the first service from the second service.

Background for System and method for sharing documents among on-demand services

The background section does not imply that the subject matter is prior art just because it was mentioned in the section. A problem that is mentioned in the background or related to the subject matter in the background should not be presumed to be prior art. The background section is merely a collection of different approaches that can be considered inventions in themselves.

In conventional on-demand services, users can access documents that are stored in a logical storage area associated with the service provider. The user retrieves and stores documents using their own system. A user system could remotely access one or more server systems, which in turn might access the on demand service of the service provider. The user system could issue a query to the on-demand system’s document management system in order to retrieve documents from the system. The on-demand system may receive a request in the form a query, and send information to the user’s system about the documents that are stored at the service and/or the relevant document to the demand.

It is not practical for the average user to share documents on different document management systems.

It is therefore desirable to offer techniques that allow users to share documents between one or more services on demand to enhance the ease of using the system.

According to embodiments, mechanisms and methods are provided for sharing documents among on-demand services. The mechanisms and methods of sharing documents between on demand services allow embodiments to give users access to information and documents stored on different on-demand service. “The ability of embodiments that allow for the sharing of documents among on-demand service can provide improved and more efficient accessibility to documents and other types of information stored on separate services.

Each embodiment described herein can be combined or used in any way with the other embodiments. “Any element from any embodiment can be used in another embodiment.

Any of the above examples may be used individually or in combination with each other. This specification can also contain embodiments which are only mentioned in part or referred to in the summary or abstract, or not at all. The embodiments may not address all of the deficiencies in the prior art that may be mentioned or alluded in the specification. Other words, different embodiments may address different deficiencies discussed in the specification. Some embodiments might only address a single deficiency or partially address a few deficiencies that are discussed in the specifications. Other embodiments might not address any of them.

The systems and methods for sharing documents among on-demand services are described. The systems and methods for sharing documents among on-demand service can allow embodiments to give users access to documents and other information stored in separate on-demand service.

The next section will describe mechanisms and methods to provide and share documents and content among on-demand services with examples.

System Overview

FIGS. “FIGS. 1A and 1B are examples of a multi-tenant on-demand database. This is an example on an on demand service where information can be shared. FIGS. The user interfaces of FIGS. “4-14 can be used.

FIG. 1A shows a block diagram for an environment 10 that could be used to provide a database on demand service. The environment 10 can include tenant data storage 22, storage system 24, program code 26 and process space 28. Other embodiments of environment 10 may not include all the components listed, and/or have other elements in place of or added to those listed above.

In FIG. 1An environment 10 is a place where an on-demand service for databases exists. A user system 12 can be any device or system used by the user to access a databases user system. User systems 12 may be, for example, a handheld computer, mobile phone, laptop computer, workstation, or network of computing devices. As shown in FIG. As shown in FIG. 1B), user systems 12 could interact with a database service 16 via a network 14.

An on demand database service such as system 16 is a pre-established system of databases that are made available to users who do not have to worry about building or maintaining the system. Instead, the system is available when users require it (e.g. on their own request). On-demand database systems may store data from multiple tenants in tables of the same database image, forming a multi-tenant system (MTS). In this way, “on-demand database 16” is defined. The terms?on-demand database service 16? Here, the terms?system 16? and?system 16? will be interchangeable. A database object may be included in a database image. A relational database system (RDMS), or an equivalent, may be used to store and retrieve information from the database object. The application platform 18 can be a framework for running the system 16 applications, including the operating system, hardware, and/or other software. On-demand Database Service 16 may include application platform 18, which allows creation, management and execution of one or more applications. The application platform can be developed by the service provider, or users who access the service through user systems 12. Or third-party application developers.

The user systems 12 can have different capacities. The capacity of any particular system 12 could be determined entirely by the permissions (permission level) of the current user. If a salesperson uses a user system 12 to communicate with a system 16, the user system will have the capacity assigned to that salesperson. While an administrator uses that user system to interact with system 16, the user system will have the capacities allocated to that administrator. Users with one permission level can access applications, data and database information that is accessible to a user of a lower level, but they may not be able to access certain applications, database data and data that are accessible to a user of a higher level. Users will therefore have different abilities to modify and access application information and database data, depending on their security level.

Network 14″ is any combination of networks that are able to communicate. Network 14 could be a combination of any or all of the following: LAN (local network), WAN, telephone network (wide area), wireless network (point-to-point), star network (token ring), hub network (hub network), or any other configuration. The most common computer network is the TCP/IP network (Transfer Control Protocol/Internet Protocol), such as the global network of networks commonly referred to by the name?Internet.? With a capital “I”,? This network will be used for many examples. It should be understood, however, that the invention may use a variety of networks, even though TCP/IP has been widely implemented.

Continuing with FIG. Users systems 12 could communicate with system 16 via TCP/IP, and at a network level they might use HTTP, FTP AFS, WAP etc. In an HTTP example, the user system 12 may include a HTTP client (also known as a “browser”). Sending and receiving HTTP messages from and to an HTTP server in system 16. This HTTP server could be the only network interface between network 14 and system 16, but other techniques may be used. In some implementations the interface between network 14 and system 16 includes load-sharing functionality, such round-robin HTTP Request Distributors to distribute incoming HTTP Requests evenly across a plurality servers. Each of the servers can access the MTS data, at least for users who are accessing the server. However, alternative configurations could be used.

In one embodiment, the system 16 shown in FIG. 1A implements a web based Customer Relationship Management (CRM). In one embodiment, the system 16 is configured with application servers that can implement and execute CRM applications, as well as to provide data, code and forms to user systems 12, and to retrieve data from a database. In a multi-tenant database, data from multiple tenants can be stored within the same object. However, tenant data is typically arranged in logically distinct groups so that no tenant has access to data belonging to another tenant unless it is explicitly shared. In some embodiments, the system 16 implements other applications than or in addition CRM application. System 16 can, for example, provide tenants with access to multiple hosted applications (standard and customized), including CRM. The application platform 18 may support user (or third-party developer) applications that may or may include CRM. It manages the creation, storage, and execution of these applications on a virtual machine within the process space 16 of the system 16.

FIG. 1A shows a possible arrangement of elements in system 16. In conjunction with FIG. 1B includes a network data storage 22, tenant data storage 23, system data data storage 24, and program code 26 to implement various functions of the system 16. Other processes that can run on the system 16 include database-indexing processes.

Click here to view the patent on Google Patents.