Abstract: Disclosed are mechanisms for sharing content through content consumption systems. A sharing module publishes content in a share and metadata associated therewith to a content consumption system external to a managed repository. The share represents a folder or directory in the managed repository. The publication can be made through application programming interface (API) calls handled by a first sharing module API, a repository API, a second sharing module API, and a content consumption system API. These APIs together provide a one-to-one mapping of communications protocols used by the managed repository and the external system. The share in the managed repository and the share published to the content consumption system are synced and any conflict between the two is detected and resolved. The shared content can be repatriated back to the managed repository and the shared version deleted from the content consumption system.

Abstract: Disclosed are mechanisms for sharing content through content consumption systems. A sharing module publishes content in a share and metadata associated therewith to a content consumption system external to a managed repository. The share represents a folder or directory in the managed repository. The publication can be made through application programming interface (API) calls handled by a first sharing module API, a repository API, a second sharing module API, and a content consumption system API. These APIs together provide a one-to-one mapping of communications protocols used by the managed repository and the external system. The share in the managed repository and the share published to the content consumption system are synced and any conflict between the two is detected and resolved. The shared content can be repatriated back to the managed repository and the shared version deleted from the content consumption system.

Abstract: Disclosed are mechanisms for sharing content through content consumption systems. A sharing module publishes content in a share and metadata associated therewith to a content consumption system external to a managed repository. The share represents a folder or directory in the managed repository. The publication can be made through application programming interface (API) calls handled by a first sharing module API, a repository API, a second sharing module API, and a content consumption system API. These APIs together provide a one-to-one mapping of communications protocols used by the managed repository and the external system. The share in the managed repository and the share published to the content consumption system are synced and any conflict between the two is detected and resolved. The shared content can be repatriated back to the managed repository and the shared version deleted from the content consumption system.

Abstract: A cloud-based, integrated business application suite includes an add-in that enables access from a client device to a first server, but not a second server. A user accesses the first server through an interface of the integrated suite to request a webpage which launches a first local instance of a service application. The first local instance of the service application sets up a local storage location and provides this location to a URL that is used to launch a webpage that is a client of the second server. A second local instance of the service application which is aware of the storage location is launched and this instance stores data requested from the second server in the identified local storage location. The stored information is read from the storage location by the first instance of the service application and is provided to the integrated application suite.

Abstract: Disclosed are mechanisms for sharing managed content through external systems. A sharing module publishes content in a share and metadata associated therewith to an external system. The share represents a folder or directory in a repository managed by an information system such as an enterprise content management system. The publication is made possible through application programming interface (API) calls handled by a first sharing module API, a repository API, a second sharing module API, and an external system API. These APIs together provide a one-to-one mapping of communications protocols used by the managed repository and the external system. The share in the managed repository and the share published to the external system are synced and any conflict between the two is detected and resolved. The shared content can be repatriated back to the managed repository and the shared version deleted from the external system.

Abstract: A cloud-based, integrated business application suite includes an add-in that enables access from a client device to a first server, but not a second server. A user accesses the first server through an interface of the integrated suite to request a webpage which launches a first local instance of a service application. The first local instance of the service application sets up a local storage location and provides this location to a URL that is used to launch a webpage that is a client of the second server. A second local instance of the service application which is aware of the storage location is launched and this instance stores data requested from the second server in the identified local storage location. The stored information is read from the storage location by the first instance of the service application and is provided to the integrated application suite.

Abstract: A cloud-based, integrated business application suite includes an add-in that enables access from a client device to a first server, but not a second server. A user accesses the first server through an interface of the integrated suite to request a webpage which launches a first local instance of a service application. The first local instance of the service application sets up a local storage location and provides this location to a URL that is used to launch a webpage that is a client of the second server. A second local instance of the service application which is aware of the storage location is launched and this instance stores data requested from the second server in the identified local storage location. The stored information is read from the storage location by the first instance of the service application and is provided to the integrated application suite.

Abstract: Disclosed are mechanisms for sharing managed content through external systems. A sharing module publishes content in a share and metadata associated therewith to an external system. The share represents a folder or directory in a repository managed by an information system such as an enterprise content management system. The publication is made possible through application programming interface (API) calls handled by a first sharing module API, a repository API, a second sharing module API, and an external system API. These APIs together provide a one-to-one mapping of communications protocols used by the managed repository and the external system. The share in the managed repository and the share published to the external system are synced and any conflict between the two is detected and resolved. The shared content can be repatriated back to the managed repository and the shared version deleted from the external system.

Abstract: Disclosed are mechanisms for sharing managed content through external systems. A sharing module publishes content in a share and metadata associated therewith to an external system. The share represents a folder or directory in a repository managed by an information system such as an enterprise content management system. The publication is made possible through application programming interface (API) calls handled by a first sharing module API, a repository API, a second sharing module API, and an external system API. These APIs together provide a one-to-one mapping of communications protocols used by the managed repository and the external system. The share in the managed repository and the share published to the external system are synced and any conflict between the two is detected and resolved. The shared content can be repatriated back to the managed repository and the shared version deleted from the external system.

Abstract: Disclosed are mechanisms for sharing managed content through external systems. A sharing module publishes content in a share and metadata associated therewith to an external system. The share represents a folder or directory in a repository managed by an information system such as an enterprise content management system. The publication is made possible through application programming interface (API) calls handled by a first sharing module API, a repository API, a second sharing module API, and an external system API. These APIs together provide a one-to-one mapping of communications protocols used by the managed repository and the external system. The share in the managed repository and the share published to the external system are synced and any conflict between the two is detected and resolved. The shared content can be repatriated back to the managed repository and the shared version deleted from the external system.