Search Results

Start Workflow

Start Workflow ID: startWorkflow Starts a workflow with the given node placed into the payload. Configuration Property Type Required Default Description model text true The ID of the workflow model to be used. swimlanes object false Identifies principals to be assigned into workflow swimlanes. The structure is: { "swimlane1": ["domainId1/principalId1"], "swimlane2": ["domainId2/principalId2"] } runtime object fal

Score: 12.385107

Locking

Locking Cloud CMS locking is a "data lock" approach which is a transactional lock is taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and fails entirely with rollback if any of the documents fail individually. We have transactional writes for multiple documents. We have a changeset-driven versioning model where each transaction writes onto it's own changeset. N number of documents may

Score: 9.864906

Overview

Overview Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team

Score: 6.0131683

Overview

Overview Releases, also referred to as branches, allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls

Score: 6.0131683

Query

Query Cloud CMS provides SQL-like, structured query for all of your content. The platform uses MongoDB under the hood to store the JSON for your content. MongoDB offers a powerful, unmatched query engine so that you can execute complex lookups of your content to support both your editorial and runtime application needs. The platform also offers "composite" quyery operations which let you layer MongoDB queries on top of Elastic Search DSL searches and traversals around node objects. Cloud C

Score: 5.633023

Documents - List Selected Actions

Documents - List Selected Actions The documents-list-selected-actions key defines actions that are available for selected items within the documents browsing page. These actions appear under the Selected... dropdown and apply to items that are selected (using checkboxes or radio buttons) on the page. The base configuration looks like this: { "config": { "documents-list-selected-actions": [] } } Default Configuration The base configuration looks like this: { "config":

Score: 5.155663

Document Actions

Document Actions The document-actions key defines actions that are available on a per-document basis. When working on an individual document, this key defines the actions that will appear as operations that can be performed. The base configuration looks like this: { "config": { "document-actions": [] } } Example - Add an Action { "config": { "document-actions": [{ "key": "do-something-awesome", "title": "Do Something Awesome",

Score: 5.1064343

Actions

Actions Cloud CMS provides a large number of actions that can be bound to links sections within configuration blocks. This allows you to customize dropdowns, button toolbars and action links at various places within the user interface. It also provides a way for you to override action implementation classes for your own users. For a list of these actions, see Actions on the lower left-hand menu.

Score: 5.026732

Documents - List Buttons

Documents - List Buttons The documents-list-buttons key defines actions that are available at buttons at the top of the documents browsing page. These actions are defined relative to the currently viewed document or folder. The base configuration looks like this: { "config": { "documents-list-buttons": [] } } Default Configuration The base configuration looks like this: { "config": { "documents-list-buttons": [{ "key": "new", "title":

Score: 4.9428377

Actions

Actions You can optionally configure Actions that execute when a release goes live. Some actions support variables. The following variables are always available: release - a JSON object of the release along with all metadata about the release releaseId - the ID of the release object branchId - the ID of the release branch snapshot - the ID of the snapshot that was generated after merge The following Actions are supported: Send Email Fire Web Hook For each action, you need to provi

Score: 4.924704