Search Results

API / Workflow / Overview

Overview 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: 34.87243

API / Content Models / 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, inclu

Score: 31.714745

API / Data Types / Association

Association Type association Datastore Type repository Supports authorities, permissions, transfer Associations, on the other hand, do not bear permissions. They are considered structural elements that provide several meanings for the content in a branch: The "linked" relationships between nodes. These relationships can be broken by either party without validating the integrity of either object. An example is a "related items" relationship in a web site. Suppose Product A points to Product B via

Score: 9.410886

API / Features / Propagates Authorities

Propagates Authorities QName: f:propagates-authorities Flags an association as one that propagates inherited authorities from the source to the target. If a parent has authorities assigned to it, those authorities are propagated to the children as masked a:hasRole associations. These associations have inherited set to true and inheritsAssociation set to the association ID being masked. Cloud CMS uses this feature to model propagation of authorities in a containment model within the graph. When y

Score: 8.498475

API / Features / Rates

Rates QName: f:rates Applied to an association to indicate that the target node contains a property with a rating value that should be used to aggregate (increment or decrement) rating statistics on the source. This feature automatically computes rating statistics on the source node for the property indicated on the target node. The following statistics are aggregated on the source node: { "_statistics": { "ratingTotalCount": , "ratingTotalValue": , "r

Score: 8.436059

UI Guide / Content / Tags

Tags Cloud CMS lets you manage your tag hierarchy and assign those tags to your content. Content that is tagged is automatically marked with the tag information (within the tags property) and will also maintain an a:has_tag association in the content graph that points back to the tag instance. Tags are first class citizens within Cloud CMS. They are content like everything else. Once content is tagged, you will see it reflected in the user interface as such. You will be able to navigate your con

Score: 8.430483

API / Features / 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 relations

Score: 8.353419

API / Content Models / 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 elemen

Score: 8.322203

UI Developer Guide / Actions / Actions

Actions account change-password addon install-addon uninstall-addon applications delete_applications new_application archives delete-archives download-archive publish-archives unpublish-archives associations add-association delete-associations attachments add-attachment delete-attachments authorities grant-authority revoke-authority comments add-comment delete-comments conflict evaluate-conflict keep-conflicting-version keep-local-version view-conflict-in-api conflicts delete-conflicts evaluate-

Score: 7.729113

API / Content Services / 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 similar t

Score: 7.5962853