Search Results


Rules Content Rules provide a way for you to wire in business logic behind the content graph. Once they're set up, rules run automatically as content is created, updated and deleted within your branch. Rules are content nodes with a JSON payload the describes the Conditions and Actions to be triggered. As with all behaviors, Rule nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavio

Score: 11.8544


Overview Conditions provide a way for Rules to evaluate their content and their environment prior to determining whether to proceed with the execution of their Actions. A Condition might be a simple check such as checking to see whether the current content item has a certain property value. But they also might be more complex logic chains consisting of and and or blocks. Cloud CMS provides a number of out-of-the-box Conditions. Scroll down to see a list of available out-of-the-box Condition

Score: 10.063317


Overview Policies can be used to run custom code or fire off actions when an event, such as creating a content item or associating a content item into the content graph, occurs. Cloud CMS provides a wide array of policies that you can hook your custom logic into. By default, Cloud CMS provides sensible and useful content policy handlers to manage the lifecycle of you content. You can wire in new policy handlers. Policy handlers include scripts and rules. The following types of policies are

Score: 9.5026045


Plugins Cloud CMS plugins let you enhance your editorial user interface with new features and capabilities that integrate to popular third-party services like YouTube, Vimeo and Google Docs. Plugins provision your editorial environment with things like: new form field types that integrate to third-party services new user interface pages for browsing and working with media from third-party services new actions or rules to enhance your repository's business logic new content types, associat

Score: 9.429775


Overview Cloud CMS lets you wire in behaviors behind your content models so that rules automatically execute when your content is touched. Content editors work with simple forms to create content that conforms to your defined content models. When that content is created, updated or deleted, it automatically triggers policies (or events) which you use to bind in custom behaviors.

Score: 9.042931

Managing a large number of PDFs or images

In Cloud CMS everything is a node. A node has JSON properties and could also have binary attachments. What you would call a "file" is a node with properties describing it's folder location and a "default" attachment holding the payload (PDF file, image, MSWord doc, etc).

Typically, for large number of PDFs, images, etc, we suggest  individual nodes with a single attachment each (which is the PDF, image, etc). We have many customers who use Cloud CMS in this way and it essentially works

Score: 7.516509


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

Score: 6.1041884

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


Config The Configuration Service loads JSON rules for the current application and composes them into a JSON configuration document that is served back. The Configuration Service considers JSON rules that are defined at application level as well as the project, platform and user level. { "config": { "remote": { "enabled": , "appKey": "" } } }

Score: 6.0169992


Overview Cloud CMS provides an action framework that lets you kick off actions that perform processes on your behalf. Actions are units of work that are typically fired off as a result of an event handler or listener. For example, you might register an action that fires when a piece of content is updated or when a workflow task transitions. The Cloud CMS action framework aspires to provide complete units of work that are configured using simple JSON. The units of work are cluster aware and

Score: 5.79603