Search Results

API / Content Services / Tree

Tree Content that is organized into folders can be retrieved using the Tree API. The Tree API lets you pull back an entire path-based folder and file structure of content within a single API call. The API call lets you specify a root node, a maximum depth to traverse down the path structure, paths that should be automatically expanded and query terms for filtering of root nodes. The Tree API is deal to support a variety of cases including: retrieval of multiple deeply-nested paths within a singl

Score: 37.906075

API / Security / Security

Security Cloud CMS provides two ways to describe access rights to things: Object-level / role-based authorities Team / role-based authorities With object-level / role-based authorities, you assign a principal (either a user or a group) a role against something. For example, you might give Joe the CONSUMER role against a content node. When Joe then interacts with the content node in the future, he will do so with the CONSUMER role which will allow him to "read" the node. With team / role-based au

Score: 14.962773

API / Workflow Handlers / Sync Node

Sync Node Type: syncNode This handler "syncs" nodes that are part of a workflow's payload to a target branch. This handler can be used to have workflow payload nodes automatically copied to or deleted from a target branch. The full config for this handler is as follows: { "targetProjectId": "", "targetRepositoryId": "", "targetBranchId": "", "includeAllAssociations": , "delete": } Examples Sync nodes to another branch in

Score: 11.154837

API / Workflow / Overview

Overview In explaining workflow, let's first take a look at the following things: Workflow Models Workflow Instances Workflow Tasks Workflow Payload Resources Workflow Comments Workflow History Item Workflow Events Workflow Event Handlers A workflow model is a definition of a workflow consisting of a full set of instructions on how content should be routed between participants or activities on its way toward completion. A workflow model is kind of like a blueprint describing the sequence of step

Score: 10.976941

API / Content Services / Traversal

Traversal Content in Cloud CMS is stored in a graph-like structure that consists of nodes and associations. Nodes are entities in the graph and associations are the relationships (the lines between points in the graph). As such, when working with content in Cloud CMS, you'll often find it useful to employ these structures in terms of your content model. Your content can be spread out between nodes and associations equally so that both the entities and the relationships hold JSON properties that

Score: 10.907011

API / Actions / Move Node

Move Node ID: moveNode Moves a source association into a new location in the content graph. The association is unlinked from its source node and linked to the target parent node. The association type and properties are preserved. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the source association. branchId text true The ID of the branch of the source association. nodeId text true The ID of the source association. targetRepositoryId t

Score: 9.69227

API / Data Types / Association

Association Type association Datastore Type repository Supports authorities, permissions, transfer Associations, on the other hand, do not bear permissions. They are considered structural elements that provide several meanings for the content in a branch: The "linked" relationships between nodes. These relationships can be broken by either party without validating the integrity of either object. An example is a "related items" relationship in a web site. Suppose Product A points to Product B via

Score: 9.570974

UI Guide / Projects / Deleted Items

Deleted Items Cloud CMS provides a "copy on write" mechanism for any creates, updates or deletes to the content in a branch. This means that whenever you delete something, you're actually masking it as deleted. The content itself is never destroyed or removed permanently. As such, it is always possible walk backwards in time and discover content that was deleted - all the way back to the moment when your branch or repository was created. To make things easier, Cloud CMS provides a "deletions" in

Score: 9.32454

Tree Hierarchies

In Cloud CMS, there are no hard and fast rules regarding association types between nodes. And so, when dealing with things like tree structures, you usually have to first make some assumptions about the kinds of relationships between nodes that you want to traverse. For arbitrary relationships and traversals around nodes, Cloud CMS provides traversal methods which are a bit more intensive to use. However, if you're using typical a:child relationships between nodes (which is what Cloud CMS uses f

Score: 9.18098

API / Content Services / Find

Find Cloud CMS offers three primary facilities for retrieving content based on DSL: Query (Mongo DB) Search (Elastic Search) Traversal (Graph Traversal) "Find" provides a way for you to execute a single API lookup that runs one or more of the above and composes them into a single result set. Using "Find", you can do things like: Find any nodes where price is greater than 10.00 and less than 15.00 (using Mongo DB) and also has the word awesome somewhere in it's binary attachment (Elastic Search).

Score: 8.869765