Search Results

Mitigating the OWASP Top 10

An explanation of how Cloud CMS addresses each of the Top 10 OWASP topics: Mitigating-the-OWASP-Top-10.pdf

Score: 8.883635


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


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

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


Search Cloud CMS provides full-text and structured search for all of your content. The platform uses Elastic Search under the hood to automatically create and manage search indexes for your content so that you can find anything at any time. The platform also offers "composite" search operations which let you layer searches on top of structured queries and traversals around node objects. Cloud CMS automatically indexes all of your content, including both it's JSON structure and any binary att

Score: 5.763798


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 (Elasti

Score: 5.734413


Search Content is automatically indexed when it is created, modified, or uploaded in Cloud CMS. The index is across the Content properties and the also any attached file eg Word, PDF,.. Platform At Platform level you can search for Content across all projects subject to your access permissions. Project Search at Project le

Score: 5.7236333

Configure Search

Configure Search You can configure the project search page to show different filter controls on the left hand side by adding some properties to your project JSON descriptor. These controls ultimately feed into a Cloud CMS node API find call that has the following structure: { "query": ... query block into MongoDB, "search": ... search block into Elastic Search } The following customization block can be added to your project's JSON descriptor: { ..., "search": {

Score: 5.710135


Indexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update

Score: 5.5515985


@search Searches for nodes and makes those nodes available to the template. Parameters parameter required description text required the text to search for sort the field to sort on sortDirection the direction to sort in (either 1 for ascending or -1 for descending) limit the number of records to return skip a position to skip ahead to in the record set scope if "page", then only relatives related to the current page will be returned as specifies the name of the resultsvariable

Score: 5.3871465