Abstract: Content maintained in a first repository of a first installation (which can optionally be an on-premise installation) of a content management system, as well as metadata associated with the content, can be shared via an approach in which content items maintained in the first repository are synchronized with a copy of the content items maintained in a second repository of a second installation (which can optionally be a cloud-based installation). The first installation can be optionally firewall protected. The copy of the content items can be accessed by collaborative users both within and external to a firewall. Related systems, methods, products, etc. are described.

Abstract: The content management system can receive log-on requests from a plurality of users and a request from the plurality of users to access content stored in a repository of the content management system. The requested content can be copied to a transient content store. The transient content store can facilitate presentation of the copy of the content on a shared interface to the plurality of users. The transient content store can facilitate editing of the copy of the content by the plurality of users simultaneously by an editor external to the content management system. The edited copy of the content can be transmitted back to the content management system and can be stored in the repository of the content management system.

Abstract: Event information associated with an occurrence of an event in an electronic content management system can be routed to an event information broker of an analytics engine that is configured to maintain data routing continuity by storing the event information in a system memory. The analytics engine can be logically and/or physically separate from the electronic content management system. The broker can separate event information into event topic bins. Messenger listeners can be used to obtain event information and store it in a staging area database for analysis and reporting without interfering with the operations of the electronic content management system.

Abstract: A user interface for applying restriction parameters to content items and users in a grouped manner is provided. A selection of one or more restriction groups can be received through a graphical user interface on a display device associated with a content management system. One or more restriction marks associated with the one or more restriction groups can be displayed on the graphical user interface. A selection of the displayed one or more restriction marks can be received through the graphical user interface for being assigned to a content item stored in the content management system. The content item can have associated metadata stored in the content management system. Metadata associated with the content item can be updated. The updated metadata can indicate that the selection of the one or more restriction marks is assigned to the content item.

Abstract: A synchronization queuing service associated with a content management system repository can record file events occurring to content items maintained at the content management system repository. The synchronization queuing service can receive a file synchronization request for information identifying a content item to which a client machine is subscribed. The synchronization queuing service can determine consistency or inconsistency of a client machine state of the content item relative to the content item at the content management system repository and can respond to client machine with a file event summary comprising information usable by the client machine to identify actions necessary to synchronize the client machine state of the content item the content item.

Abstract: Configurable and self-optimizing business process applications can be used in conjunction with features of a content management system, for example including generating and providing guidance relating to a decision or action point within a workflow instance, allowing a user to invoke an exception that includes a deviation from a set of actions defined by the business process application, saving a modified version of the business process application in the content management repository, and monitoring performance metrics of the business process application and the modified business process application when used by additional users in additional workflow instances. Methods, systems, and articles of manufacture are described.

Abstract: User permissions for a search on content managed by a content management system (CMS) can be evaluated in a search engine based on a user identity of a user providing a query input for the query rather than after return of an initial results set to the CMS or some other front-end application. The search engine can constrain possible results returned from a search for the query input using a content index of a plurality of content items maintained in a repository of the content management system. The constraining can include limiting the search engine from adding a content item of the plurality of content items to a permissions-filtered results set unless the evaluating of the user permissions and the search for the query input against the content index do not exclude the content item. Other aspects can support index updating by selective use of a metadata index.

Abstract: In-place records management can include in-place declaration of records in which a document within a document library or other first file structure associated with a content management system or application can be declared as a record such that records management controls are set for the document. The setting of the records management controls can include placing a record marker in the first file structure while the content object containing content and metadata of the document now designated as a record is relocated to a second file structure associated with a record management system or application. The record marker allows users of the content management system or application who had access to the document prior to its designation as a record to be able to access the corresponding record from within the content management system or application. Additional features can include dynamic record declaration and dynamic record handling.

Abstract: Using a first unique identifier of a local file on a client machine associated with a second unique identifier of a content item maintained at a content management system repository, synchronization of the local file and the content item can be restored after a synchronization break.

Abstract: Content transformations can include transformation of content items in a CMS repository from a source format to a target format. Such transformations can be performed using a transformation node cluster having multiple nodes, each of which is configured for a specific content transformation type. Router nodes can receive requests for content items and route content items to transformation nodes having a proper content transformation type to either transform a requested content item to the target format or perform an intermediate transformation as part of a transformation chain. A transformation node cluster can be dynamically configurable based on estimates of expected loads for the various types of transformations. Systems, methods, and articles of manufacture are also described.

Abstract: The content management system can receive log-on requests from a plurality of users and a request from the plurality of users to access content stored in a repository of the content management system. The requested content can be copied to a transient content store. The transient content store can facilitate presentation of the copy of the content on a shared interface to the plurality of users. The transient content store can facilitate editing of the copy of the content by the plurality of users simultaneously by an editor external to the content management system. The edited copy of the content can be transmitted back to the content management system and can be stored in the repository of the content management system.

Abstract: A synchronization queuing service associated with a content management system repository can record file events occurring to content items maintained at the content management system repository. The synchronization queuing service can receive a file synchronization request for information identifying a content item to which a client machine is subscribed. The synchronization queuing service can determine consistency or inconsistency of a client machine state of the content item relative to the content item at the content management system repository and can respond to client machine with a file event summary comprising information usable by the client machine to identify actions necessary to synchronize the client machine state of the content item the content item.

Abstract: Hybrid, configurable business process applications can be used in conjunction with features of a content management system. For example, a first content management system installation executes a workflow instance based on a business process application whose definition is maintained in by the first content management system installation and synchronizes a workflow state of the workflow instance to a second content management system installation using a mirrored workflow state in which both content of the workflow state and metadata characterizing parameters of the workflow state are mirrored from the first content management system repository to the second content management system repository such that a content item retained in the second content management system repository is accessed for use in the workflow instance via the mirrored workflow state at the second content management system repository. Methods, systems, and articles of manufacture are described.

Abstract: Content maintained in a first repository of a first installation (which can optionally be an on-premise installation) of a content management system, as well as metadata associated with the content, can be shared via an approach in which content items maintained in the first repository are synchronized with a copy of the content items maintained in a second repository of a second installation (which can optionally be a cloud-based installation). The first installation can be optionally firewall protected. The copy of the content items can be accessed by collaborative users both within and external to a firewall. Related systems, methods, products, etc. are described.

Abstract: A synchronization queuing service associated with a content management system repository can record file events occurring to content items maintained at the content management system repository. The synchronization queuing service can receive a file synchronization request for information identifying a content item to which a client machine is subscribed. The synchronization queuing service can determine consistency or inconsistency of a client machine state of the content item relative to the content item at the content management system repository and can respond to client machine with a file event summary comprising information usable by the client machine to identify actions necessary to synchronize the client machine state of the content item the content item.

Abstract: Content transformations can include transformation of content items in a CMS repository from a source format to a target format. Such transformations can be performed using a transformation node cluster having multiple nodes, each of which is configured for a specific content transformation type. Router nodes can receive requests for content items and route content items to transformation nodes having a proper content transformation type to either transform a requested content item to the target format or perform an intermediate transformation as part of a transformation chain. A transformation node cluster can be dynamically configurable based on estimates of expected loads for the various types of transformations. Systems, methods, and articles of manufacture are also described.

Abstract: A workflow executed by an on-premise installation of the content management system can include a cloud workflow and an on-premise workflow relating to on-premise content retained in an on-premise repository managed by the on-premise installation of the content management system. A synchronization can be initiated between the on-premise content and a cloud copy of the on-premise content to reflect a change to either of the on-premise content or the cloud copy in the other of the on-premise content and the cloud copy. The cloud copy can exist at a location managed by a cloud-based installation of the content management system. Upon detection that the cloud workflow has been completed by the location using the cloud copy, a resumption of the on-premise workflow can be triggered using the synchronization between the on-premise content and the cloud copy of the on-premise content. Related systems, methods, products, etc. are described.

Abstract: Content maintained in a first repository of a first installation (which can optionally be an on-premise installation) of a content management system, as well as metadata associated with the content, can be shared via an approach in which content items maintained in the first repository are synchronized with a copy of the content items maintained in a second repository of a second installation (which can optionally be a cloud-based installation). The first installation can be optionally firewall protected. The copy of the content items can be accessed by collaborative users both within and external to a firewall. Related systems, methods, products, etc. are described.

Abstract: A workflow executed by an on-premise installation of the content management system can include a cloud workflow and an on-premise workflow relating to on-premise content retained in an on-premise repository managed by the on-premise installation of the content management system. A synchronization can be initiated between the on-premise content and a cloud copy of the on-premise content to reflect a change to either of the on-premise content or the cloud copy in the other of the on-premise content and the cloud copy. The cloud copy can exist at a location managed by a cloud-based installation of the content management system. Upon detection that the cloud workflow has been completed by the location using the cloud copy, a resumption of the on-premise workflow can be triggered using the synchronization between the on-premise content and the cloud copy of the on-premise content. Related systems, methods, products, etc. are described.

Abstract: Content maintained in a first repository of a first installation (which can optionally be an on-premise installation) of a content management system, as well as metadata associated with the content, can be shared via an approach in which content items maintained in the first repository are synchronized with a copy of the content items maintained in a second repository of a second installation (which can optionally be a cloud-based installation). The first installation can be optionally firewall protected. The copy of the content items can be accessed by collaborative users both within and external to a firewall. Related systems, methods, products, etc. are described.