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: 42.81926

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: 27.425283

API / Controls / Related Content

Related Content ID: related-content The related-content field type renders a n upload field that is pre-configured to upload assets and store them as standalone document nodes within the content graph. This is useful, say, if you wanted to let end users upload images and store them in an /Images folder. Sample configuration: { "type": "related-content", "uploadPath": "/Images" } The related content control should be modeled on top of either an object or an array field. This is very simi

Score: 27.16973

API / Controls / File Picker

File Picker ID: file-picker The file-picker field type renders a modal picker for a file. This uses the File Folder service within Cloud CMS to let you browse through folder-based navigation. A breadcrumb is rendered at the top to help users step through the folder hierarchy. Sample configuration: { "type": "file-picker" } As with the node picker, the file picker should be modeled on top of either an object or an array field. The former is used for selection of a single node whereas the lat

Score: 27.095936

API / Controls / Node Picker

Node Picker ID: node-picker The node-picker field type renders a modal picker for a node. The modal picker allows you to filter nodes as well as paginate, sort and inspect nodes. The picker supports single node and multi-node selection depending on how the field is configured. Sample configuration: { "type": "node-picker" } The node picker should be modeled on top of either an object or an array field. The former is used for selection of a single node whereas the latter is used for selectio

Score: 26.562399

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: 18.496044

API / Actions / Overview

Overview Cloud CMS provides an action framework that lets you kick off actions that perform processes on your behalf. Actions are units of work that are typically fired off as a result of an event handler or listener. For example, you might register an action that fires when a piece of content is updated or when a workflow task transitions. The Cloud CMS action framework aspires to provide complete units of work that are configured using simple JSON. The units of work are cluster aware and will

Score: 18.483786

API / Conditions / Overview

Overview Conditions provide a way for Rules to evaluate their content and their environment prior to determining whether to proceed with the execution of their Actions. A Condition might be a simple check such as checking to see whether the current content item has a certain property value. But they also might be more complex logic chains consisting of and and or blocks. Cloud CMS provides a number of out-of-the-box Conditions. Scroll down to see a list of available out-of-the-box Conditions and

Score: 17.248144

Application Server / URL Addressability / Node URLs

Node URLs The Application Server supports retrieval of nodes and node attachments via URLs and takes responsibility for setting headers and cache state for optimal performance. This method is the preferred method for dealing with binary payloads as it ensures compatibility with CDN edge caching. In addition, binary and JSON files that are retrieved from the Cloud CMS API are cached on the Application Server itself so that subsequent requests benefit from having a local copy. A notifications laye

Score: 13.951968

Docker Guide / Maintenance / Repository Compression

Repository Compression Cloud CMS content is stored within a Repository. A Repository differs from other types of data stores in that it provides Copy-On-Write mechanics using Changeset-driven versioning. Every time you create, update or delete content within a repository, those adjustments are written onto a new Changeset. Changesets are layered automatically and provide a stack of differences that, over time, allow you to scroll back to any moment in time to see a perfect capture of every modif

Score: 12.892718