Search Results

Features

Features Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS,

Score: 12.335544

Content Model - Association example

Question. Suppose that I have the following collection types:

  • Customers 
  • Orders
and I want to store the Customer ID and the Customer Name on each Order…
If the customer then updates his Name, how is it possible (if at all) to update the customer’s name on all of his orders - in a single atomic transaction?
 
Answer.  For this situation, you would have two content types - Customer and Order. One good way to address this is

Score: 10.170803

Property Mapping

Property Mapping QName: f:property-mapping Automates the assignment or mapping of property values from one end of an association to the other. This feature is added to an association (or an association definition) to set up an automatically maintained mapping of values from a "from" node to a "to" node. The feature allows for multiple mappings to be defined. When the defined "from" node is updated, it's property value is automatically copied or mapped into the "to" node's recipient property

Score: 9.881601

Relator Properties

Relator Properties Cloud CMS provides support for properties that auto-manage their relationships between multiple nodes in the content graph. Whenever you intend to connect two nodes together, it is often convenient to model a property on one or both of the nodes involved in the relationship such that the properties maintain information locally on the endpoints about the relationship. Such properties are known as relator properties. Consider a Store that sells Books. Books are written by A

Score: 9.137728

Auto Client Mapping

Auto Client Mapping Type autoClientMapping Datastore Type webhost Supports authorities, permissions, transfer

Score: 7.6243834

Overview

Overview A content model consists of definitions which describe your project's content types, properties, graph associations, and the aspect-oriented features that Cloud CMS uses to ensure data consistency, integrity and validity when content is created, updated or deleted. In Cloud CMS, all content modeling is done using JSON and more specifically, JSON Schema. JSON Schema provides an elegant and well-adopted model for describing the types for content objects, properties and other nested ele

Score: 7.259362

Statistics

Statistics Cloud CMS automatically collects and aggregates node statistics for you as you connect nodes together in the content graph. Nodes are entities and associations are used to connect them together through a series of relationships. As nodes are connected together, both the source and target node will have their statistics computed and updated so that you can quickly find out how many relationships a given node has to its neighbors. The basic mechanics behind node statistics are simila

Score: 6.8378625

Related

Related QName: f:related This feature is applied internally to nodes that are on the other end of a relator association to indicate that the target node is related to the source node. This feature acts as a marker to tell Cloud CMS to consider the related nodes and the relator association at persistence time so the properties can be managed more efficiently in terms of mapping values from one end of the relationship to the other. There is no need to apply or work with this feature manually.

Score: 6.578054

Remove Features

Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: { "features": [{ "qname": "" }] } Each of the features identified by qname will be removed from the documents attached to the workflow payload. Here is an example configuration which assum

Score: 6.284486

Add Features

Add Features Type: addFeatures This handler adds features to a node that is part of the workflow's payload. This can be used to apply one or more features to your content instances as they flow through your workflow. The config for this handler is as follows: { "features": [{ "qname": "", "config": { ... optional configuration for the feature } }] } The config is an optional parameter. You can use this handler to add one or more fe

Score: 6.2500587