Search Results

Knowledge Recipient

Knowledge Recipient QName: f:knowledge-recipient Used internally to identify that a node has received one or more knowledge properties from a source Knowledge Space. These properties exist on the JSON but may have their values overwritten at any time. The indicated properties are not "mastered" on this node but rather receive their values from elsewhere. Any node that is marked as a f:knowledge-recipient will have at least one a:shares-knowledge association binding it back to the source of t

Score: 15.070771

Knowledge Sharing

Knowledge Sharing QName: f:knowledge-sharing Used to tag an association as to indicate that it "shares knowledge" between a source node and a target node. The source node is a node is a "knowledge space" and the target node is a "knowledge recipient". An association marked with f:sharing-knowledge will be considered to be an association that knowledge properties may propagate down when changes are made to a knowledge space node. By default, the a:child association which is used to mark relat

Score: 14.372862

Knowledge Space

Knowledge Space QName: f:knowledge-space Used to indicate that a node should behave as a Knowledge Space. A Knowledge Space has zero or more knowledge properties. A knowledge property is a regular old property on your JSON object that is special in that its value may propagate to other nodes automatically. A Knowledge Space is holds the "master value" for those knowledge properties. When those properties change, their new values are pushed to any other nodes that are sharing the knowledge

Score: 14.2030945

How does Cloud CMS compare to DIY (do-it-yourself)?

Not sure whether to build or buy? 

Review these points to help guide your selection.

Why DIY:

  • exact fit with your technology stack
  • use existing in-house skills and resources
    • build only the features you need
    • able to add new features as required
    • use existing developers for support
  • cost / budget - internal
    • no need for external services to deliver and support product
  • Score: 9.596062

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

Overview

Overview Welcome to the Cloud CMS Documentation center. Cloud CMS is an API-first content management system that provides everything you need on the back end to power web sites and mobile applications. Cloud CMS makes it easy for your business users to create, manage and publish amazing content to your users! You are reading the Getting Started guide. To learn more about Cloud CMS and what it does, select the option in the left-hand menu. We offer several additional guides to help you work

Score: 6.833373

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

Send Email

Send Email ID: sendEmail Sends an email to a recipient. To send an email using this action, it is required that you identify: the email provider to be used to send the email (applicationId and emailProviderId the recipient of the email (using to or toPrincipalId) who the email is from (either using from or the default from value of your email provider) the body of the email (by either specifying body directly, via a node reference or via an Email Template reference) the subject of the e

Score: 6.325012

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