Found 243 results for "api repository node"

The search executed in 0.001 seconds

API Keys

API Keys For information on API Keys, please visit the Cloud CMS - API Keys Developer Page.

Score: 33.54238

API

API The Cloud CMS API consists of an HTTP/HTTPS endpoint that uses OAuth 2.0 authentication. It supports both REST concepts and asynchronous data operations. You can access this API using any of our drivers as well as curl or any HTTP client library. Our API provides functionality that covers all aspects of content production, publishing and presentation. 100% of the functionality of Cloud CMS is accessible from the API, including: Content Models, Creation and Editing Workflow, Scheduled Publish

Score: 30.650894

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

Application Server

Application Server The Cloud CMS Application Server offers an easy way for customers to assemble powerful, front-end custom APIs and web sites for Cloud CMS. It is completely free and runs on top of the popular Node.js technology stack. With Cloud CMS, customers have a choice of using any front-end presentation technology they wish. In many cases, customers already have a technology investment (such as C#, PHP, Java or Ruby) and thus a preference for continuing to build on that technology stack.

Score: 18.474003

Docker / 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: 16.14397

API / Data Types / Repository

Repository Configuration As with all data stores, this data store maintain a configuration document that contains system and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the behavior and characteristics of the directory. The following table presents y

Score: 15.858789

Workflow

Workflow 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: 13.576512

API / 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: 13.524298

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.3099375

API / Data Types / Node

Node Type node Datastore Type repository Supports authorities, permissions, transfer Configuration The node configuration contains system and custom properties. You can write your own properties as you see fit. However, system properties should be left alone as they are read-only. The following table presents you the system properties. Node Properties Property Type Default Read-Only Description _features object Read-Only This object contains all of the configuration for features which have been

Score: 13.093632

Actions

Actions Cloud CMS provides an Action framework that lets you kick off Actions that perform content operations 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 triggers when a piece of content is updated or when a workflow task transitions. The Action might do something like Send an Email or Fire off a Web Hook. The Cloud CMS Action framework aspires to provide complete units of work

Score: 12.926038

Forms / Fields / 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 selection

Score: 11.989668

Docker / Configuration / API Server

API Server The Cloud CMS API Server is a Java application that launches inside of a Java Servlet Container. The Java application surfaces a REST API as well as backend services and DAOs to support connectivity to Mongo DB, Elastic Search and a slew of Amazon services including S3, SNS, SQS, Route 53, Cloud Front and more. Properties File Cloud CMS is primarily configured via a properties file that is auto-detected and loaded when the underlying Spring Framework starts up. This properties file is

Score: 11.691578

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

Actions / Sync Node

Sync Node ID: syncNode Syncs a node to a target location. If the node does not exist in the target location, it is created. If it is already created, it is updated. If the node was deleted or we are explicitly told to sync a delete operation, the node will be deleted at the target location. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the source node. branchId text true The ID of the branch of the source node. nodeId text true The ID

Score: 11.277367

Actions / Unzip Node

Unzip Node ID: unzipNode Unzips an attachment from a node into a target folder. { "title": "Unzip Node", "properties": { "repositoryId": { "title": "Repository ID of node with ZIP attachment", "type": "string" }, "branchId": { "title": "Branch ID of node with ZIP attachment", "type": "string" }, "nodeId": { "title": "ID of node with ZIP attachment", "type": "string" },

Score: 11.212402

Workflow / Workflow Handlers / Copy Node

Copy Node Type: copyNode This handler copies nodes that are part of a workflow's payload to a target folder. The target folder can be identified either by a node ID or a node path. The config for this handler is as follows: { "targetNodeId": "", "targetOffsetPath": "" } If targetOffsetPath is specified, then targetNodeId is the root node to calculate the offset against. If targetNodeId is not provided, the default repository root is used. Here is an example w

Score: 11.091398

Actions / Copy Node

Copy Node ID: copyNode Makes a copy of a node and any of its owned children to a new location in the content graph. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the source node. branchId text true The ID of the branch of the source node. nodeId text true The ID of the source node. targetRepositoryId text true The ID of the repository of the target parent node. targetBranchId text true The ID of the branch of the target parent node. t

Score: 11.073355

Actions / Lock Node

Lock Node ID: lockNode Locks a node as the current user. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the node. branchId text true The ID of the branch of the node. nodeId text true The ID of the node.

Score: 10.990673

Actions / Unlock Node

Unlock Node ID: unlockNode Unlocks a node as the current user. The current user must have the lock or the current user must have authorities to remove the lock. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the node. branchId text true The ID of the branch of the node. nodeId text true The ID of the node.

Score: 10.910586

Workflow / Workflow Handlers / Move Node

Move Node Type: moveNode This handler moves nodes that are part of a workflow's payload to a target container. The target container can be identified either by a node ID or a node path. The config for this handler is as follows: { "targetNodeId": "", "targetOffsetPath": "" } If targetOffsetPath is specified, then targetNodeId is the root node to calculate the offset against. If targetNodeId is not provided, the default repository root is used. Here is an exam

Score: 10.641196

Workflow / 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 t

Score: 10.129514

Policies / Node Policies

Node Policies Node policies provide places where you can hook in behaviors that trigger when nodes are created, updated or deleted within the graph. Nodes may either be entities or associations. This provides an ideal way to plug in your custom behaviors for any definition or content instance within your content graph. The following policies are available: Policy QName Description p:beforeCreateNode Raised before a piece of content is created p:afterCreateNode Raised after a piece of content has

Score: 7.968857

Conditions / Node Has Attachment

Node Has Attachment The nodeHasAttachment condition tests whether a node has an attachment with a given attachmentId and optional contentType. It triggers if a matching attachment is found. JSON Schema { "title": "Node Has Attachment", "properties": { "attachmentId": { "type": "string", "title": "Attachment ID", "default": "default" }, "contentType": { "type": "string", "title": "Content Type" }

Score: 6.7339907

Application Server / Clustering

Clustering The Cloud CMS Application Server supports running on a single Node process as well as multiple Node processes. Node processes can run on a single server instance or can be spread across multiple server instances behind a load balancer. By default, the Application Server starts up and allocates itself to a single CPU. This is known as single mode. Even if you have a server with more than one CPU on it, the Application Server will still only bind to 1 of those CPUs. When the Application

Score: 6.4644723